August 24, 2023 at 3:21 am
We have had SSPI errors across a dozen servers in an hour span.
Per the above link :
Stuck at the very first point...
Cause of SQL error 17806
1.SQL Server engine account running with a Domain service account, and that account locked at the time a Kerberos connection attempt. The connection would work, but it would kick down to NTLM.
What does it mean that an account is locked at the time a Kerberos connection attempt ? Thanks
FYI: We have seen 17806 in the error log quite frequently across several servers.
August 25, 2023 at 4:10 am
Thanks for posting your issue and hopefully someone will answer soon.
This is an automated bump to increase visibility of your question.
August 30, 2023 at 5:14 pm
Can somebody help me here. Thanks
September 11, 2023 at 2:16 pm
You probably lack the SPN's for SQL server. You can check them with the Microsoft tool: https://www.microsoft.com/en-US/download/details.aspx?id=39046
The tool can even generate the commands to add the missing ones.
September 12, 2023 at 8:31 am
Hi,
we got this kind of error as well. We had a lot of domaincontroller. If one of them is in maintenance, or will just reboot, the sql server needs some seconds to recognize, that he had to use another domain controller.
We don't care about the error, we got no impact on our application or databases.
Kind regards,
Andreas
September 26, 2023 at 3:53 am
This was removed by the editor as SPAM
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply