Just fixed a problem that had been (unbeknownst to me) plaguing this place for who knows how long.<\/p>\n
After rebooting a domain controller, the SQL servers would start throwing logon errors until it came back up.\u00c2\u00a0 Most of the errors were from IIS that use windows auth, a few errors even came from the app servers.\u00c2\u00a0 What made it especially tricky was that it really looked like a kerberos problem.\u00c2\u00a0 Depending on what machine you were looking at, you’d get an error like<\/p>\n
Login failed for user ”. The user is not associated with a trusted SQL Server connection.<\/em><\/p>\n or maybe<\/p>\n Logon Failure: and one<\/p>\n The Kerberos subsystem encountered a PAC verification failure<\/em><\/p>\n I saw a few<\/p>\n The failure code from authentication protocol Kerberos was The specified user does not exist<\/em><\/p>\n Long story short – I looked and poked and Googled… I couldn’t seem to find anyone that had reported this problem before (and I’m usually pretty good at putting together search terms that get me what I want) until I finally found a KB article<\/a> that fit my hunch of what was happening.\u00c2\u00a0 I don’t think I saw the “NO_SUCH_USER” code in any of the logs I looked through (maybe that’s what you get if you’re using NTLM?) but the rest of it sure sounded good.\u00c2\u00a0 I tried the work-around on the domain controllers first – stopping the netlogon service before rebooting – and didn’t get a single error.<\/p>\n I deserve a raise. \ud83d\ude00<\/p>\n","protected":false},"excerpt":{"rendered":" Just fixed a problem that had been (unbeknownst to me) plaguing this place for who knows how long. After rebooting a domain controller, the SQL servers would start throwing logon errors until it came back up.\u00c2\u00a0 Most of the errors … Continue reading
\nReason:\tAn error occurred during logon
\n… it’d go on to tell you what was wrong with Kerberos<\/em><\/p>\n