April 19, 2010 at 6:37 am
No user(sql or widows, remotely or locally) was able to login and jobs were failing due to login failure.
Following errors were found in the logs:
SSPI handshake failed with error code 0x80090308 while establishing a connection with integrated security; the connection has been closed. [CLIENT: <local machine>]
Login failed for user ''. The user is not associated with a trusted SQL Server connection. [CLIENT: <local machine>]
After that all the jobs started failing due to error ‘unable to determine if the owner(username) of job has server access (reason: The certificate, asymmetric key, or private key data is invalid. [SQLSTATE 42000] (Error 15297)).
Server TCP provider has stopped listening on port [ 1433 ] due to a failure. Error: 0x2739, state: 1. The server will automatically attempt to reestablish listening.
SQL services are running on domain user which is in admin group. My instance is running NTLM and SQL authentication. The user was not blocked and the password also didn’t changed. I could not find any reason why it happened to me.
Finally I recycled SQL services to resolve the issue and till now it has not occurred again. I am wondering if anyone else has faced same issue anytime and can help me to find out and trobleshoot real issue.
April 20, 2010 at 6:05 am
FYI..
My instance is SQL 2005 (ver 9.00.3042.00),SP2 and Standard Edition. Its running on Microsoft Windows Server 2003, Enterprise Edition; Version5.2.3790 Service Pack 2 Build 3790.
April 20, 2010 at 6:36 am
Do you know of any issues that occurred during the timeframe with your Domain Controller(s) that host those user accounts?
Shawn Melton
Twitter: @wsmelton
Blog: wsmelton.github.com
Github: wsmelton
April 20, 2010 at 8:27 am
I am not sure about that but it doesn't sounds like that because my other instances are also running on the same user and i didn't faced any issue there. When I logged in on the server it connected well.. I pinged from other servers it pingged fine.
Thanks
MeltonDBA (4/20/2010)
Do you know of any issues that occurred during the timeframe with your Domain Controller(s) that host those user accounts?
April 21, 2010 at 3:48 am
Please share your ideas what can be the reason for this.
April 21, 2010 at 4:15 am
I faced this situation once few years back. I deleted all Windows groups and turned the Authentication Mode to Windows Authentication in the same session. Then I closed the connection, and there you are. Cant enter the SSMS. To resolve this, I went to registery and changed the authjentication mode back to Sql Server.
I hope, this could help you.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply