How do you use cloud databases? Take the survey.

Monitor fails to Login

On one of the servers that we monitor we get login failures every day at the same time for around 5 mins and the monitoring stops. The monitor service is a windows account. Other monitored servers have no issues. The messages we receive are:

Login failed. The login is from an untrusted domain and cannot be used with Windows authentication.
Error: 17806, Severity: 20, State: 14.
SSPI handshake failed with error code 0x80090311, state 14 while establishing a connection with integrated security; the connection has been closed. Reason: AcceptSecurityContext failed. The Windows error code indicates the cause of failure. No authority could be contacted for authentication.
Error: 18452, Severity: 14, State: 1

After the 5 mins everything starts working again. Any ideas what is happening?


  • Russell DRussell D Posts: 1,324 Diamond 5
    edited September 21, 2017 1:11PM
    Hard to say really, but this could be for a number of reasons.

    It can be related to SQL trying to contact AD for a kerberos ticket and failing, for which case I'd investigate your DC and see if you're getting any errors there. Also, on that server, run nltest / and see if you get any errors, or a successful return (eg Trusted DC Name/Connection).

    Its potential cause could be a DNS issue, can you connect to SQL via windows authentication on this machine? If not look into refreshing the DNS settings.

    It looks like you've not sent through the full error, are you also seeing Cannot generate SSPI context? This might help if so.
    Have you visited our Help Centre?
Sign In or Register to comment.