question

Waqar_lionheart avatar image
Waqar_lionheart asked

The SQL Server Network Interface library could not deregister the Service Principal Name (SPN) for the SQL Server service. Error: 0x6d3, state: 4. Administrator should deregister this SPN manually to avoid client authentication errors

Hi All, Sorry to bother but I am seeing this error after server shutdown. Just a bit concerned here as it did not happen before. Kind of new to all this to any help on what to do will be greatly appreciated. My sql server service runs under local system. This server only has one instance installed on it. I am a bit stumped. Correct me if I am wrong but running under local system, it should have all the necessary rights and permissions to register or deregister a SPN successfully? does it mean kerberos is not working anymore. how do i check? I have not had any complaints of any connections being refused. Thanks in advance, Waqar
permissionsnetworkspn
10 |1200 characters needed characters left characters exceeded

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

1 Answer

· Write an Answer
Adedba avatar image
Adedba answered
Might be worth downloading kerberos Config manager from Microsoft, this will run through an spn check for you its very simple to use :) [Kerberos Configuration Manager for SQL Server][1] [1]: https://www.microsoft.com/en-us/download/details.aspx?id=39046&WT.mc_id=soc-n-[TR]-loc-[Services]-[farukc]
10 |1200 characters needed characters left characters exceeded

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Write an Answer

Hint: Notify or tag a user in this post by typing @username.

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.