The other day I was working in SSMS and connected to an instance. Pretty normal there. I later opened some window (I don’t recall exactly–perhaps a report or some db option) and was met with this error message. I could then do nothing in the database.
SSPI handshake failed with error code 0x8009030c, state 14 while establishing a connection with integrated security; the connection has been closed. Reason: AcceptSecurityContext failed. The Windows error code indicates the cause of failure. [CLIENT: 10.1.1.1].
This same error was found in the SQL Server log with the accompanying error message.
Error: 17806, Severity: 20, State: 14.
It turns out my Windows password had expired from the time I opened the instance to the time I was looking at something in the database. Once I reset my password, I was good to go.
Mirroring is dead. Long live mirroring. While it will no longer be included in future versions of SQL Server, I still come across instances I have to support and thus am making some notes. Occasionally, when setting up mirroring, you may get the following error.
The server network address “TCP://SQLServer:5022” can not be reached or does not exist. Check the network address name and that the ports for the local and remote endpoints are operational. (Microsoft SQL Server, Error: 1418)
I have found some common scenarios include:
- Insufficient permission on both nodes. Make sure the service account for each SQL Server instance has rights to the partner instance. Seems simple enough, but this was an issue for me just last month.
- The log backup has not been applied to the partner/mirrored instance. While sometimes it might let you set up without taking a transaction log backup and applying it on the partner database, more often than not it requires it.
Check out Robert Davis’s post for more helpful information if you are stuck.