October 23, 2006 at 10:28 am
I am unable to connect to my default instance of SQL Server 2005, except locally.
When l looked at the SQLServer Log I found the following entry which MIGHT fix the problem:
The SQL Network Interface library could not deregister the Service Principal Name (SPN) for the SQL Server service. Error: 0x45b. Administrator should deregister this SPN manually to avoid client authentication errors.
Problem is I can't find how to accomplish this task.
Anyone have an idea on this?
Thanks
Bill
October 23, 2006 at 8:56 pm
You can use setspn command line utility to list, create or delete spn's:
October 24, 2006 at 5:00 am
If the SPN is set up with the correct service account and SQL port, there is no need to de-register it. SQL will try to create its SPN on startup, and remove it on closedown. If it does not have the rights to do this, the existance of the SPN will depend on if it has been created manually.
As far as I can see, the only 'problem' about leaving a SPN around permanently is that clients that rely on AD to find the SQL instance and your instance is down will have an unexpected logon error instead of getting told by AD that the SQL instance is not available.
However, if you have changed service account and a SPN exists for the previous service account then you may get other authentication problems. See the SQL2005 BOL entry on the AD Helper Service for a bit more information.
Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.
When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara
October 24, 2006 at 5:02 am
Thanks for the good info.
Turns out the problem was a DNS issue.
I'm glad to have a better understanding of the SPNs now though.
April 24, 2008 at 8:01 am
I am also geting the same error 'Administrator should deregister this SPN manually to avoid client authentication errors' in the error log when i am trying to install SQL Server 2005. SQL Server installation terminates with a unhadleabe exception. My OS is Windows Server 2003 SP 2. previously it was having SQL Server 2000. which I have uninstalled.
Can you tell me please what you did get rid of the previous mention error. Or any other suggestions.
April 24, 2008 at 8:08 am
The problem I had was resolved by fixing the DNS on the network. It happened in the process of merging multiple domains.
Sorry I can't help beyond that.
Bill Mell
January 5, 2009 at 6:42 am
I have a server that gets rebooted every Sunday at 4AM that is hanging up somewhere in the process. If we go into the server room, point the KVM to that server, and wiggle the mouse, it magically finishes shutting down and restarts.
The only thing that remotely resembles an error message is that "The SQL Network library could not deregister the Service Prinicipal Name (SPN) for the SQL Server service. Error: 0x45b....." error.
Could this be preventing a shutdown from completing, or is it just a coincidence that we are seeing this message becasue the shutdown process stops the SQL services? (And as far as I can tell, the SQL services are cleanly stopping).
The Redneck DBA
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply