st8floorsup


I keep getting these alerts but the client's IP listed in the message doesn't seem to be having a problem. I'm not sure if it is retrying and succeeds the second or third try. I commonly get 2 of these messages each time it happens. I thought is may be when the user connects to the server in Management Studio but when I got the message today the user wasn't trying to connect to this server. The server the use was connected to in SSMS is linked to this server but if the link was causing the error it looks like it would return the IP of the server instead of the users IP. The link is done using a SQL login account. Anyway, this is not a big problem since know body except me even knows it is happening but I'd like to figure it out.

SQL Server Alert System: 'Fatal Error in Current Process' occurred on

DESCRIPTION: SSPI handshake failed with error code 0x8009030c while establishing a connection with integrated security; the connection has been closed.




Re: SSPI handshake failed with error

Nan Tu


This error is posted by server that is being connected from a client. The authitication scheme is windows authentication. 0x8009030c is SEC_E_LOGON_DENIED error, i.e. "The logon attempt failed". It means that the client login credential is not recognizable by the server. There could be many reasons result in this error, including typically (1) client server are in different domain, (2) Client or Server or both is not in domain and there password used by the client is not sync-up with server, a typical scenario in workgroup. To solve (1).setup domain trust (2) create the same user account on both machine.






Re: SSPI handshake failed with error

st8floorsup

This server is not in the DMZ so the user should not (could not) be connecting to it using Window Authenication. It seems that something is trying to connect to it using windows authenication from her machine but I don't know what it is.




Re: SSPI handshake failed with error

Nan Tu

Since you know the client IP address, one pragmatic way is to run "netstat -anob <interval>" on the machine and redirect the output into a text file, let interval=1. You can search which process made connection to your sqlservr by matching the server IP address and port number. Let me know if you find it.