Posted by: Colin Smith
Login Errors, SQL Server, Troubleshooting, Windows Authentication
So this morning I was asked to help out with an issue that a user was seeing. The user has an application that uses a local account on the server to run the application and that application uses that account using windows auth to connect to a sql server on another host. So when I got the call I logged into SQL Server and I looked at the SQL Server error log and I found the following.
2010-11-03 15:13:55.27 Logon Error: 17806, Severity: 20, State: 2.
2010-11-03 15:13:55.27 Logon SSPI handshake failed with error code 0x8009030c while establishing a connection with integrated security; the connection has been closed. [CLIENT: xxx.xx.xx.xx]
2010-11-03 15:13:55.27 Logon Error: 18452, Severity: 14, State: 1.
2010-11-03 15:13:55.27 Logon Login failed for user ”. The user is not associated with a trusted SQL Server connection. [CLIENT: xxx.xx.xx.xx]
I found that the application attempts to connect via ODBC connection and I attempted to configure an ODBC connection and I found that I recieved the same error. I searched online for this error and all I found was that this would happen if you were using windows authentication only on the SQL Server and attempting to connect with a SQL Server account. That is not the case for me since I am using windows authentication to connect to the SQL Server. I checked to make sure that the account had been created on both hosts and it was, and it was also a login and user in SQL and the database that it needed.
So I attempted to log into the SQL Server host with this local account and I found that Windows wanted that account to change its password. The password had expired. This was the problem. I went in and modified the user so that the password was not expired and viola…. All is well again.
Hope that will help someone out since I did not find any real help for my particular issue on-line and the error is not so great.