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,


more ▼

asked Aug 07, 2017 at 01:14 PM in Default

avatar image

101 8

(comments are locked)
10|1200 characters needed characters left

1 answer: sort voted first

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

more ▼

answered Aug 11, 2017 at 06:29 PM

avatar image

41 2

(comments are locked)
10|1200 characters needed characters left
Your answer
toggle preview:

Up to 2 attachments (including images) can be used with a maximum of 524.3 kB each and 1.0 MB total.

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here



Answers and Comments

SQL Server Central

Need long-form SQL discussion? SQLserverCentral.com is the place.



asked: Aug 07, 2017 at 01:14 PM

Seen: 37 times

Last Updated: Aug 11, 2017 at 06:29 PM

Copyright 2018 Redgate Software. Privacy Policy