We started seeing CheckDB_alive alert in SQLSERVER due to domain logon failed while making connection.
We are using Windows Authentication and when testing the profile we are getting the error:
Log:
Oct 16 14:09:20:245 [5888] sqlserver: Profile: test connection profile/test connection checkpoint, domain logon using user <Domain>\<user>
Oct 16 14:09:20:291 [5888] sqlserver: Error from domain_logon/LogonUser: 1326
Oct 16 14:09:20:291 [5888] sqlserver: Profile: test connection profile/test connection checkpoint - domain logon failed
or:
Oct 16 14:09:20:245 [5888] sqlserver: Profile: test connection profile/test connection checkpoint, domain logon using user <Domain>\<user>
Oct 16 14:09:20:291 [5888] sqlserver: Error from domain_logon/LogonUser: 1909
Oct 16 14:09:20:291 [5888] sqlserver: Profile: test connection profile/test connection checkpoint - domain logon failed
Release : UIM 20.4, sqlserver probe
Error 1326: Windows error: the username or password are wrong
Causes of 1326 can be multiple, wrong password, password updated and not synced, wrong domain, wrong username or connection profile corruption caused by a probe crash.
Error 1909: Windows error: This account has been locked out or cannot be referenced
Causes of 1909 can be that during investigation and testing the server policy might lock the user after several failed login attempts.
Error 1326:
• Check if the password is correct, check if any recent password change is synced, review the username and domain are correct.
• Verify if the same Windows user can create an ODBC connection to the DB from the same server where the SQLserver probe is deployed.
• If the credentials are correct, recreate a new connection with the same user name and credentials and test. Alternatively, create a new Windows authentication user that has appropriate permissions on the DB and create a new connection in the sqlserver and test.
Error 1909:
• As the user is locked, a windows admin should unlock the user