Troubleshooting credential validation with instance management
This topic describes the situations that may cause validation errors when you register SQL Server instances in the Applications utility.
Validation for an instance or an instance group can fail for the following reasons:
If the host name is invalid, the following message appears:
Status Code: 40 Could not validate credentials. Failed to connect to client: <client>.
If the host name is correct but you cannot connect to the host because the host is down, the following message appears:
Status code: 46 The validation operation timed out waiting for a response from the client
If the host name is correct, but user name or password is invalid, the following message appears:
Status Code: 41 Validation of operating system user/password failed for client: <client>.
If the credentials do not have the "sysadmin" role, the validation fails.
STATUS 1939: The specified user does not have SQL Server System Administrator privileges.
If the NetBackup Client Service or the NetBackup Legacy Network Service require but do not use the same user for the logon account.
Invalid configuration detected. The service user for the Netbackup Client and Netbackup Legacy Network services must be the same user. Change the service users in the Windows Service Manager and try again.
See Configuring the NetBackup services for SQL Server backups and restores.
The user account does not have the required the local security privileges and .
Status Code 41
These privileges are required if you use the credentials setting .