The SQL Network Interface library could not register the Service Principal Name (SPN) for the SQL Server service. Error: 0x54b, state: 3. Failure to register an SPN may cause integrated authentication to fall back to NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies.
There was another problem that I faced today for a different client. The solution to this one was similar to the SSPI context error.
We installed a SQL Server instance and when I tried to start it, it wouldn't start. Saw the above mentioned error in the event viewer and SQL Server error logs.
The solution was
1) Change the SQL Server Service to run under 'LOCALSYSTEM' account and restart SQL Server.
2) Once this was complete I was able to connect to the instance.
3) Next change the service to run under whatever Active directory account you want to run it under.
4) Restart SQL Server
There was another problem that I faced today for a different client. The solution to this one was similar to the SSPI context error.
We installed a SQL Server instance and when I tried to start it, it wouldn't start. Saw the above mentioned error in the event viewer and SQL Server error logs.
The solution was
1) Change the SQL Server Service to run under 'LOCALSYSTEM' account and restart SQL Server.
2) Once this was complete I was able to connect to the instance.
3) Next change the service to run under whatever Active directory account you want to run it under.
4) Restart SQL Server
No comments:
Post a Comment