February 2, 2018 at 10:30 am
Hi,
Frequently observing below errors in sql log. Not sure about the login name.
Any suggestion to fix this error.
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. The logon attempt failed.
Thank you!1
February 2, 2018 at 10:54 am
adisql - Friday, February 2, 2018 10:30 AMHi,
Frequently observing below errors in sql log. Not sure about the login name.
Any suggestion to fix this error.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. The logon attempt failed.
Thank you!1
Usually you have some more information logged about the error. You can check the security event log on that server when it happens - search the event log based on the time the error is recorded in the SQL Server log.
The error can happen for many different reasons - problems with spns is often a factor. So you may want to check that the spns exist and are configured correctly. This tool makes it pretty easy to check:
Microsoft Kerberos Configuration Manager for SQL Server
Sue
February 2, 2018 at 11:32 am
Sue_H - Friday, February 2, 2018 10:54 AMadisql - Friday, February 2, 2018 10:30 AMHi,
Frequently observing below errors in sql log. Not sure about the login name.
Any suggestion to fix this error.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. The logon attempt failed.
Thank you!1
Usually you have some more information logged about the error. You can check the security event log on that server when it happens - search the event log based on the time the error is recorded in the SQL Server log.
The error can happen for many different reasons - problems with spns is often a factor. So you may want to check that the spns exist and are configured correctly. This tool makes it pretty easy to check:
Microsoft Kerberos Configuration Manager for SQL ServerSue
Thank you !!
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply