Applications Manager reached the SQL Server instance, but the server refused the credentials. Two different problems produce a login failure. Match the message you see, then follow that section.
Applications Manager shows Authentication failed: Incorrect username or password. above the message returned by the driver. The driver message is the one that tells you which problem you have, so read it first.
Login failed for user '<name>'.What it means: SQL Server received the credentials and rejected them. The connection reached the server; only the login was refused. This is the common case when a SQL login is used.
Work through these steps in order:
| State | Meaning |
|---|---|
| 2, 5 | The login does not exist on this server. |
| 6 | A Windows login was supplied as a SQL login. See the next section. |
| 7 | The login exists but is disabled, and the password is also wrong. |
| 8 | The password is wrong. |
| 11, 12 | The login is valid, but it has no permission to connect to this server. |
| 18 | The password has expired and must be changed. |
| 38, 40 | The login is valid, but its default database is unavailable. |
master, on the login's General page.Login failed. The login is from an untrusted domain and cannot be used with Windows authentication.What it means: the monitor is using Windows authentication, and the domain account could not be validated by the SQL Server host. The account itself may be correct; the problem is usually the trust, the local security policy or an NTLM restriction.
domain\username) are correct.Ensure the user account is added to the Access this computer from the network policy.
Refer to this page for more details.
If the SQL account is also used as the SQL Server service account and its password was changed recently, make sure the new password is reflected in the service configuration:
Click here for more details.
On the database server, check whether NTLM authentication is restricted. Navigate to Computer Configuration → Windows Settings → Security Settings → Local Policies → Security Options and look for the NTLM-related settings. If NTLM is restricted, remove the restriction or configure it to allow Windows authentication.
Two other messages are easy to mistake for a rejected login. Neither is one, and neither is fixed by changing the credentials.
Access denied: Your account does not have the required database permissions, The server principal '<name>' is not able to access the database 'master', or VIEW SERVER PERFORMANCE STATE permission was denied. The login succeeded; the account simply cannot read what Applications Manager needs. Refer to Troubleshooting issues while adding an MS SQL Monitor, section 9, Check that permission has been provided for the user.
Login timed out, or The TCP/IP connection to the host <hostname>, port 1433, has failed. The connection never got as far as checking the credentials. Refer to the same article, section 8, Connectivity issue.
If you have followed the steps above and still cannot log in to MS SQL, send the following to the Applications Manager support team:
Refer to our feature page to learn more about SQL Server monitoring in Applications Manager.