Error 0x54b Sql Server
Contents |
(Русский)ישראל (עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeLibraryLearnDownloadsTroubleshootingCommunityForums Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered by: The SQL Network Interface library was unable to register SPN. Error: 0x54b SQL Server > SQL Server Database Engine Question 0 register spn for sql server Sign in to vote I am running SQLExpress 2005, on Win 2003. Occasionally in the sql server network interface library could not register the service principal name (spn) the event viewer I see the message: The SQL Network Interface library was unable to register SPN. Error: 0x54b When I click list spn for sql server on the link on the event viewer for more info, there is no further details. Can someone clarify what this message means and should I be concerned Thanks Wednesday, August 17, 2005 8:59 AM Reply |
Check Spn Registration
Quote Answers 1 Sign in to vote Hi,Is your machine part of a domain or just workgroup?This probably isn't an error that you need to be concerned about. Every time an instance is started, SQL Server will attempt to automatically register a Service Principal Name (SPN) to be used for Kerberos authentication in case it's available(the BOL has more information about the format of the SPN). Kerberos authentication requires that the client list spn for server and server machines belong to the same domain or else, trusted domains. In your case, the error indicates a Windows error of 1355 (=0x54B) which translates to "The specified domain either does not exist or could not be contacted." If I had to guess, I would say that your machine is not part of a domain. There's no problem with this except that Kerberos authentication will not be available.One other thing. The registration of the SPN will only succeed if the account starting the service has the privilege to do so --normally the Local System Account or a Domain Admin account. But if SPN registration failed because of lack of privilege, the error would be different.I hope this helps.Il-Sung.--Il-Sung LeeProgram Manager, SQL Server ProtocolsMicrosoft Corp. This posting is provided "AS IS" with no warranties, and confers no rights. Monday, August 22, 2005 1:01 PM Reply | Quote All replies 1 Sign in to vote Hi,Is your machine part of a domain or just workgroup?This probably isn't an error that you need to be concerned about. Every time an instance is started, SQL Server will attempt to automatically register a Service Principal Name (SPN) to be used for Kerberos authentication in case it's available(the BOL has more information about the format of the SPN). Ke
365 for Enterprise Skype for business Microsoft Dynamics Microsoft Dynamics Sales Service Marketing Social Enterprise Resource Planning Small and Midsize Business Windows Windows 10 for business Windows 10 for Internet of Things what is service principal name Windows devices Data and analytics Data management and analytics Microsoft SQL Server
Read Serviceprincipalname
Microsoft Power BI Microsoft Cortana Intelligence Suite Operations management Operations Management Suite System Center Sign in Search Microsoft Search
Finddomainforaccount: Call To Dsgetdcnamewithaccountw Failed With Return Value 0x00000525
Dynamics Community Participate Ask a Question Get Started Badges Earn Badges View Badges Leaderboards Compete on Leaderboards View Leaderboards Become an Expert Recommend a Blog Introduce Yourself Provide Feedback Communities Microsoft https://social.msdn.microsoft.com/Forums/sqlserver/en-US/567d77bf-4f23-4ea7-8eae-7a6f295f7701/the-sql-network-interface-library-was-unable-to-register-spn-error-0x54b?forum=sqldatabaseengine Dynamics AX Microsoft Dynamics CRM Microsoft Dynamics GP Microsoft Dynamics NAV Other Products Partner Community Dynamics Community Microsoft Dynamics RMS Forum Blogs Videos Support Dynamics Community Participate Ask a Question Get Started Badges Earn Badges View Badges Leaderboards Compete on Leaderboards View Leaderboards Become an Expert Recommend a Blog Introduce Yourself Provide Feedback Communities Microsoft Dynamics AX Microsoft Dynamics CRM Microsoft Dynamics https://community.dynamics.com/rms/f/106/t/159604 GP Microsoft Dynamics NAV Other Products Partner Community Microsoft Dynamics RMS Forum Blogs Videos Support The SQL Network Interface library could not register the Service Principal Name (SPN) for the SQL Server service Sign In Share Twitter LinkedIn Facebook Email Print RSS Pappu My Badges Question Status Suggested Answer Pappu asked a question on 4 May 2015 12:07 PM I got the following message logged into Error log [Server Machine running SQL Server 2012] and both standalone POS running on the Back office server freezes up. Is there a solution to this problem? Any help would be appreciated. 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. Thanks, Pappu Tags: SQL SPN Network Interface library Reply All Responses (1) Only Answers DYNAMICS101 My Badges Suggested Answer DYNAMICS101 responded on 4 May 2015 3:50 PM blogs.technet.com/
up Recent PostsRecent Posts Popular TopicsPopular Topics Home Search Members Calendar Who's On Home » SQL Server 2008 » SQL Server 2008 - General » User can http://www.sqlservercentral.com/Forums/Topic947701-391-1.aspx connect to default instance, but... 11 posts,Page 1 of 212»» User can connect to default instance, but can't to named one Rate Topic Display Mode Topic Options Author Message Shcherbunov NeilShcherbunov Neil Posted Monday, July 5, 2010 11:24 PM Valued Member Group: General Forum Members Last Login: Wednesday, July 2, 2014 8:31 AM Points: 57, Visits: 278 Good day to ALL! My situation: there is stand-alone computer (no network cable) with name COMP. sql server On COMP was installed WinServer 2008 and then SQL Server 2008R2 in two instances: default and with name MSSQLSERVER2. Configure of both instance the absolutely same. And on COMP there is Window's user XXXuser, the member of group Users. On both instances there is login COMP\XXXuser for this user with, again, identical configure.Now, I am enter on COMP(in operating system) as COMP's administrator and open console (runas) as XXXuser. In this console I spn for sql type:sqlcmd -S COMPNot a problem - connect! Back to the command line and type:sqlcmd -S COMP\MSSQLSERVER2But this time the console respond:Msg 18456, Level 14, State 1, Server COMP\MSSQLSERVER2, Line 1Login failed for user COMP\XXXuser.If we now go (as admin) to Management Studio and look to Errors Log for MSSQLSERVER2 for the massages concerning failed login attempts we can see:Message Login failed for user 'COMP\XXXuser'. Reason: Token-based server access validation failed with an infrastructure error. Check for previous errors. [CLIENT: