Help on not able to Start SQLSERVER service anymore
Question
Monday, July 11, 2011 8:14 AM
Dear all,
I am running SQL server 2008 standard under Windows server 2008 R2.
Was working well until 2 days ago where SQLSERVER service cannot start anymore.
Here is below what the log says, but do not know how to solve it :
2011-07-11 09:59:54.83 Server Error: 26023, Severity: 16, State: 1.
2011-07-11 09:59:54.83 Server Server TCP provider failed to listen on [ 'any' <ipv6> 1433]. Tcp port is already in use.
2011-07-11 09:59:54.83 Server Error: 17182, Severity: 16, State: 1.
2011-07-11 09:59:54.83 Server TDSSNIClient initialization failed with error 0x2740, status code 0xa. Reason: Unable to initialize the TCP/IP listener. Only one usage of each socket address (protocol/network address/port) is normally permitted.
2011-07-11 09:59:54.83 Server Error: 17182, Severity: 16, State: 1.
2011-07-11 09:59:54.83 Server TDSSNIClient initialization failed with error 0x2740, status code 0x1. Reason: Initialization failed with an infrastructure error. Check for previous errors. Only one usage of each socket address (protocol/network address/port) is normally permitted.
2011-07-11 09:59:54.83 Server Error: 17826, Severity: 18, State: 3.
2011-07-11 09:59:54.83 Server Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log.
2011-07-11 09:59:54.83 Server Error: 17120, Severity: 16, State: 1.
2011-07-11 09:59:54.83 Server SQL Server could not spawn FRunCM thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.
Thnaks for help
regards
serge
Your knowledge is enhanced by that of others.
All replies (7)
Monday, July 11, 2011 8:27 AM ✅Answered
Hi Serge,
As mentioned in the log, some other application is using TCP port 1433. Try changing the port of disable the application which is currently using port 1433
- Vishal
Monday, July 11, 2011 9:43 AM ✅Answered
Here is an article explaining how to do what Vishal stated:
http://support.microsoft.com/kb/823938
Jeff Wharton
MSysDev (C.Sturt), MDbDsgnMgt (C.Sturt), MCT, MCPD, MCITP, MCDBA
Blog: Mr. Wharty's Ramblings
MC ID: Microsoft Transcript
Please mark solved if I've answered your question, vote for it as helpful to help other user's find a solution quicker
Monday, July 11, 2011 11:41 AM
Hi Serge,
Please confirm if VIA network protocol is DISABLED.
You can check by going to SQL Server Configuration Manager -> SQL Server Network Configuration.
Expand SQL Server Network Configuration and check on Protocols for MSSQLSERVER. Disable the VIA if it is enabled.
Thanks,
Vishal Srivastava.
Regards, Vishal Srivastava
Monday, July 11, 2011 3:12 PM
it isYour knowledge is enhanced by that of others.
Monday, July 11, 2011 4:08 PM
Hi,
It seems you have not enabled protocols.Please enable shared memory or named pipes becauseyou have problem with TCP/IP port.
find out which application is using 1433
or change your SQL tcp/ip port ,but make sure to get confirmation from application team (they might have using port number in connection string)
Configuration manager>>Instance Protocols>>TCP/IP properties>>change your port as your requirement>>restart sql service
Sure it will resolve your problem
Sivaprasad.L Together We can Achieve
Monday, July 11, 2011 6:27 PM
Hi,
Please read this thread, they have given solution for this same issue
Arunraj Chandrasekaran, MCTS, Author: SQLXpertise.com
If you found this post useful, Please "Mark as Answer" or "Vote as Helpful"
Sunday, September 29, 2013 12:14 PM
Thanks Friend my problem is solved.