Error 1355 Mssql Server
360 games PC games Windows games Windows phone games Entertainment All Entertainment Movies & TV Music Business & Education Business Students & educators Developers Sale Sale Find a store Gift cards Products Software & services Windows Office Free downloads & security Internet Explorer Microsoft Edge Skype OneNote OneDrive Microsoft Health MSN Bing Microsoft Groove Microsoft Movies & TV Devices & Xbox All Microsoft devices Microsoft Surface All Windows PCs & tablets PC accessories Xbox & games Microsoft Lumia All Windows phones Microsoft HoloLens For business Cloud Platform Microsoft Azure Microsoft Dynamics Windows for business Office for business Skype for business Surface for business Enterprise solutions Small business solutions Find a solutions provider Volume Licensing For developers & IT pros Develop Windows apps Microsoft Azure MSDN TechNet Visual Studio For students & educators Office for students OneNote in classroom Shop PCs & tablets perfect for students Microsoft in Education Support Sign in Cart Cart Javascript is disabled Please enable javascript and refresh the page Cookies are disabled Please enable cookies and refresh the page CV: {{ getCv() }} English (United States) Terms of use Privacy & cookies Trademarks © 2016 Microsoft
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 https://support.microsoft.com/en-us/kb/303411 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 http://www.sqlservercentral.com/Forums/Topic9596-48-1.aspx 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 applica
Need help? Post your question and get tips & solutions from a community of 418,504 IT Pros & Developers. It's quick & easy. SuperSocket info: (SpnRegister) : Error 1355. P: n/a goyal.mayank https://bytes.com/topic/sql-server/answers/530172-supersocket-info-spnregister-error-1355-a Hi All, For hardware upgratdation we have to move our database server(MSSQL 2000) from a P3(Window 2003) machine to a p4(Windows 2003) machine. We have replicated the data from P3 machine to P4 machine. the replication was success full. After this we have changed the name of the p4 machine to tha of p3 machine. now when we try to connect to the new p4 machine using the windows authentication we are error 1355 not getting errror "Cannot generate SSPI Context." for solving it we have tried to change the name of the sqlserver. REF: http://groups.google.co.in/group/mic...b0966be28f835e while replication the database we have made the mssql service run under a network account. this could be a possible reason for not able to register with the ADS. Later we have changed it to run under the local user account. Any help will be highly appreciated. Mayank Aug error 1355 mssql 31 '06 #1 Post Reply Share this Question 1 Reply P: n/a Erland Sommarskog (go**********@gmail.com) writes: For hardware upgratdation we have to move our database server(MSSQL 2000) from a P3(Window 2003) machine to a p4(Windows 2003) machine. We have replicated the data from P3 machine to P4 machine. the replication was success full. After this we have changed the name of the p4 machine to tha of p3 machine. now when we try to connect to the new p4 machine using the windows authentication we are not getting errror "Cannot generate SSPI Context." You are not getting error? Or should that "not" not be there? for solving it we have tried to change the name of the sqlserver. Your posting is a bit unclear, but to comlete an operation as the one you described, you need to do EXEC sp_dropserver P4 EXEC sp_addserver P3, 'local' and then restart SQL Server. Once you are done, verify that @@servername has the correct value. -- Erland Sommarskog, SQL Server MVP, es****@sommarskog.se Books Online for SQL Server 2005 at http://www.microsoft.com/technet/pro...ads/books.mspx Books Online for SQL Server 2000 at http://www.microsoft.com/sql/prodinf...ons/books.mspx Aug 31 '06 #2 This discussion thread is closed Start new discussion Replies have been disabled for this discussion. Similar topics apache error when interfacing html with perl g