Forum Discussion
Ranjit1Have you checked the log file from the install? Does it give any clues about what actually fails?
X2As per hostcertificate logs
22:01:02.441 [9584.5896] <2> curlSendRequest: actual http response : 400 expected http result: 200
22:01:02.441 [9584.5896] <2> parse_json_error_response: Error code returned by server is :5954
22:01:02.441 [9584.5896] <2> parse_json_error_response: Developer error message return by server :The master server could not match any hostnames from alias list [Client server.corp.pri] to the IP address:x.x.x.x
22:01:02.441 [9584.5896] <16> nbcert_curl_gethostcertificate: Failed to perform getcertificate, with error code : 5954
22:01:02.441 [9584.5896] <2> NBClientCURL:~NBClientCURL: Performing curl_easy_cleanup()
22:01:02.441 [9584.5896] <2> nbclnt_curl_prefnet::reset: Returning VN_STATUS_SUCCESS
22:01:02.441 [9584.5896] <16> GetHostCertificate: nbcertcmdtool command failed to get certificate. retval = 5954
22:01:02.441 [9584.5896] <2> nbcertcmdtool: EXIT STATUS 5954: The host name could not be resolved to the requesting host's IP address.
- Ranjit16 years agoLevel 4
X2For error 14 Veritas backline recommended to add below listed files in exclusion list of antivirus, is it really work ? i am not sure because for some serevr its working fine
Antivirus Exclusions for Windows:
For a 32-bit machines:
C:\Program Files\Veritas\NetBackup\* (and all sub-directories)
C:\Program Files\Veritas\\Volmgr\* (and all sub-directories)
C:\Program Files\Veritas\NetBackupDB\*
C:\Program Files\VERITAS\VxPBX\*
C:\Program Files\Veritas\pdde\*
For a 64-bit machines:C:\Program Files\Veritas\NetBackup\* (and all sub-directories)
C:\Program Files\Veritas\\Volmgr\* (and all sub-directories)
C:\Program Files\Veritas\NetBackupDB\*
C:\Program Files (x86)\VERITAS\VxPBX\*
C:\Program Files\Veritas\pdde\* - X26 years agoModerator
The master server could not match any hostnames from alias list
5954 - hostname could not be resolved to requesting host's IP address
From the above: look at CLIENT_NAME setting for your client. The hostname that the client claims to be is not being provided the same IP address when the master server does the DNS lookup. Make sure that DNS reflects the correct IP address and the client also has the same IP address and FQDN configuration.
Related Content
- 11 years ago
- 14 years ago
- 11 years ago
- 9 years ago