On the weekend I responded to an emergency callout regarding a custom Microsoft Access front end application not being able to talk to the backend SQL database. The error which was being received was as follows.
Connection failed:
SQL State:'S1000'
SQL Server Error 0
[Microsoft][ODBC SQL Server Driver]Cannot generate SSPI context
After investigation this was caused by an incorrect time set on the SQL server. The Kerberos time tolerance by default is set 5 minutes however the SQL server clock had drifted 8 minutes out. The customer did not have their Active Directory time hierarchy configured correctly.
Connection failed:
SQL State:'S1000'
SQL Server Error 0
[Microsoft][ODBC SQL Server Driver]Cannot generate SSPI context
After investigation this was caused by an incorrect time set on the SQL server. The Kerberos time tolerance by default is set 5 minutes however the SQL server clock had drifted 8 minutes out. The customer did not have their Active Directory time hierarchy configured correctly.
No comments:
Post a Comment