Ms Sql Server Supersocket Info Spnregister Error 1355
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 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 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 a known non-issue. It should be an informational message. http://support.microsoft.com/default.aspx?scid=kb;en-us;303411Haven't seen an 8344 error before.K. Brian Kelleyhttp://www.truthsolutions.com/Author: Start to Finish Guide to SQL Server Performance Monitoring http://www.netimpress.com/shop/product.asp?ProductID=NI-SQL1 K. Brian Kelley, CISA, MCSE, Security+, MVP - SQL ServerRegular Columnist (Secu
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 http://www.sqlservercentral.com/Forums/Topic9596-48-1.aspx 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 https://support.symantec.com/en_US/article.tech108471.html 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 the Active Directory. You may see the following warning in the Microsoft Windows NT Event Log: Warning SuperSocket Info: (SPNRegister) : Error 1355
Server 2016 SQL Server 2014 SQL Server 2012 SQL Server 2008 AdministrationBackup and Recovery Cloud High Availability Performance Tuning PowerShell Security Storage Virtualization DevelopmentASP.NET Entity Framework T-SQL Visual Studio Business IntelligencePower BI SQL Server Analysis Services SQL Server Integration Services SQL http://sqlmag.com/sql-server/answers-microsoft-20-jun-2001 Server Reporting Services InfoCenters Advertisement Home > SQL Server > Answers from Microsoft - 20 Jun 2001 Answers from Microsoft - 20 Jun 2001 Jun 19, 2001 Richard Waymire | SQL Server Pro EMAIL Tweet Comments 2 Advertisement Editor's Note: Send your SQL Server questions to Richard Waymire, Microsoft's group program manager for SQL Server management tools, at questions@sqlmag.com. I need to set up a SQL Server 2000 active/active cluster, but the information I found on ms sql the Internet is about SQL Server 2000 active/passive clustering. Where can I find information about active/active clustering? Active/active SQL Server 2000 clustering simply requires two or more installations of active/passive clustering. So, you can install SQL Server 2000 on the second node the same way you do on the first node. I'm experiencing a SQL Server 7.0 performance problem. I have a table with a nonclustered index on OWNER_PER_ID and APPT_REPT_FLG columns and a clustered ms sql server index on ROW_STATUS and OWNER_PER_ID columns. Before I execute a SELECT statement to retrieve data from this table, I declare variables @P1 through @P5 and set the values Y, Y, N, I-K56, and Y (respectively) to them. When I execute the statement using the parameters, Query Analyzer uses the nonclustered index and performance is poor. However, when I run the same statement and hard-code Y instead of using the variable @P2, Query Analyzer uses the clustered index and performance is excellent. What's the difference between using the variable @P2 and hard-coding Y in the SELECT statement's WHERE clause? And how should I configure SQL Server to use the correct index when I can't hard-code the value in the SELECT statement? The plan that SQL Server chooses depends on the statistics on the APPT_REPT_FLG index. SQL Server assumes a standard number of matching rows when SQL Server sees a variable in the WHERE clause. However, when the query optimizer knows the actual value, such as the Y above, you can check the statistics on the index to determine approximately how many rows the restriction will actually apply to. For example, on your SQL Server 7.0 system, if SQL Server sees a variable to match against with equality, the query optimizer assumes that 10 percent of the rows will be returned. Clearly you'll get better results wh