Ms Sql Supersocket Info Spnregister Error 1355
PKI Service Identity Access Manager Shop Online Cyber Security Services Managed Security Services DeepSight Intelligence Incident Response Security Simulation Website Security SSL Certificates Complete Website Security Code Signing Certificates Norton Shopping Guarantee Buy SSL Products A-Z Services Services Home Business Critical Services Consulting Services Customer Success Services Cyber Security Services Education Services Solutions Solutions Home Topics Encryption Everywhere Internet of Things Next Generation Endpoint Office 365 Industries Automotive Cyber Insurance Education Financial Services Global Service Providers Industrial Control Systems Healthcare Retail Government Federal Government State & Local Support Center Technical Support Symantec Connect Buying Programs Upgrades Maintenance & Renewals Training Security Center Security Center Home Blogs ISTR Threats Virus Definitions and Security Updates Removal Tools Partner Find a Partner Become a Partner Login Required Login into Partner Portal Partner Licensing Partner Renewals Partner Training Margin Builder Opportunity Registration Financial Benefits English 中文(简体) 中文(繁體) Česká English Français Deutsch Magyar Italiano 日本語 한국어 Polski Português Pусский Español Site: Symantec Enterprise Small Business Norton United States Search Support Home Support Home MySymantec Licensing Products A-Z SYM16-015 Security Advisory Login Profile Subscriptions Logout Login Forgot Password? Don't have a SymAccount? Create a SymAccount now!' "Super SocketInfo: (SPNRegister) Error 1355" when starting SQL Server TECH108471 January 24th, 2007 http://www.symantec.com/docs/TECH108471 Support / "Super SocketInfo: (SPNRegister) Error 1355" when starting SQL Server Did this article resolve your issue? Thank you for your feedback! Provide feedback on this article Request Assistance Print Article Subscribe to this Article Manage your Subscriptions Search Again Situation When SQL Server starts on a computer that is running Microsoft SQL Server 2000, the SQL Server program always attempts to register the virtual server in
up Recent PostsRecent Posts Popular TopicsPopular Topics Home Search Members Calendar Who's On Home » SQL Server 7,2000 » Service Packs » Error and warning in Event log -- SuperSocket... 12 posts,Page 1 of 212»» Error and warning in Event log -- SuperSocket info Rate Topic Display Mode Topic Options Author Message Mark FlemingMark Fleming Posted Wednesday, January 29, 2003 8:43 AM Grasshopper Group: General Forum Members Last Login: Wednesday, April 18, 2012 12:42 PM Points: 21, Visits: 43 Hey https://support.symantec.com/en_US/article.tech108471.html folks,I wasn't sure where to post this but here goes...We have 3 database servers running Win 2K Advanced with SP3 with SQL Server 2K SP3(All recent installs -- within the last month)2 of the database servers use a domain account at startup as the service account.When the SP3 was applied I was logged in using my account (domain admin) instead of the service account.We http://www.sqlservercentral.com/Forums/Topic9596-48-1.aspx are getting an error message:"SuperSocket info: Failed to get Exclusive port use(MSAFD Tcpip [TCP/IP]) : Error 10013."and a warning message:"SuperSocket info: (SpnRegister) : Error 8344."I found a solution to the error message -- reapply SP3 while logged in as service account.However I'm still getting the warning message.I can't find any information anywhere about it.I've searched here, Microsoft, Google, Technetand can find absolutely nothing on it.Does anyone have any ideas as to the cause/possible resolutions?ThanksMark-- Edit --I just went back and checked the event log again -- the error was occurring before the SP3 install.So does anyone have any suggestions still-- End Edit --Edited by - mark.fleming on 01/29/2003 08:52:32 AM Post #9596 K. Brian KelleyK. Brian Kelley Posted Wednesday, January 29, 2003 9:25 AM Keeper of the Duck Group: Moderators Last Login: Friday, September 16, 2016 11:44 AM Points: 6,639, Visits: 1,905 The error message is because something else has grabbed the port. 1433 is in the dynamic port range, unfortunately. Usually identifying the offending network application and stopping it frees up the port. Failing that, a reboot usually does.http://support.microsoft.com/default.aspx?scid=kb;en-us;293107As for the warning, if it's error 1355, it's
the event log shows the following message: > > SuperSocket info: (SpnRegister) : Error ms sql 1355. Source: MSSQLServer, Event > ID: 19011 > > What does it mean and how can I fix this? Have a look at the following http://techrepublic.com.com/5208-6287-0.html?forumID=47&threadID=169054&start=0&tag=search PRB: SQL ms sql supersocket Server 1355 Warning Errors are Informational http://support.microsoft.com/?id=303411 If thats does not throw any light on the problem then just put id: 19011 into google and read the other 569 replys Tim . References: SQL causes Event Error 1355 From: Don Castiglioni Prev by Date: SQL Server 7 Next by Date: Re: SQL Server 7 Previous by thread: SQL causes Event Error 1355 Next by thread: SQL Server 7 Index(es): Date Thread Flag as inappropriate (AWS) Windows Science Usenet ArchiveAboutPrivacyImprint www.tech-archive.net >Archive >SQL-Server >microsoft.public.sqlserver.setup >2005-05
register the virtual server in the Active Directory. You may see the following warning in the Microsoft Windows NT Event Log: Warning SuperSocket Info: (SPNRegister) : Error 1355 Event Category 8 Event ID 19011 This message is not an error message. This text is only a warning that SQL Server was not able to register a Service Principal Name (SPN), which indicates that the security mechanism that will be used is Microsoft Windows NT Challenge\Response (NTLM) authentication instead of Kerberos. CAUSE : The message usually appears because the SQL Server service account is running as a domain user who does not have requisite permissions to register SPNs. With Microsoft Windows 2000 Service Pack 3 (SP3), you can enable Kerberos authentication on server clusters. Reference Links SQL Server 1355 Warning Errors are Informational SQL Server 2000 Kerberos Support Including SQL Server Virtual Servers on Server Clusters Did this information help you to resolve the problem? Yes: My problem was resolved. No: The information was not helpful / Partially helpful. Comments: Captcha Refresh