October 3, 2005 at 11:15 pm
Hi,
I am working on SQL Server 2005 June CTP on Windows 2003 Server SP 1. I restarted my computer but now I am not able to start the MSSQLServer service. When I try to start the service I get this message The SQL Server (MSSQLSERVER) service on Local Computer started and then stopped. Some services stop automatically if they have no work to do, for example, the Performance Logs and Alerts service.
Other services Analysis services, Browser, Integration Services, Reporting services, VSS writer, all are running.
I have checked the Event Viewer, 4 error meesages are seen all related to MSSQLServer, they are:
1&2. Event ID 17182: TDSSNIClient initialization failed with error 0x7e, status code 0x3a.
3. Event ID 17826: 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.
4. Event ID 17120: SQL Server could not spawn FRunCM thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.
Please help me!
Thanks a ton in advance,
Swapnil
October 5, 2005 at 11:54 am
It seems that all bets are off as far as the June CTP goes. Get the current product and do a fresh install. My experience has been that a new OS install is in order, too. I understand that MS has released, as of last Tuesday or so, yet another new cleanup tool that cleans up after all versions of the CTPs. It hasn't been tried here, and by now we're smart enough to have Ghosted versions of clean and patched OS installations.
It just does not make sense to try to support an old Beta.
October 17, 2006 at 9:43 pm
Happened to me, on testing environment using SQL Server 2005 Enterprise. Anybody knows how to solve this problem other than re-install?
October 18, 2006 at 7:14 am
Can you please post recent ErrorLog? If SQL is not coming up, error log is the first place to start.
December 29, 2007 at 5:38 am
OPEN THE SQL SERVER CONFIGRATION MANAGER
CLICK THE SQL SERVER 2005 NETWORK CONFIGRATION
DISABLED VIA.
October 8, 2008 at 5:54 am
This also happen to me just recently, looking for solutions, the work around I found was to disable the TCP setting and go with name pipe. Not the best solution but works. I would like to go back to TCP/IP but when ever I enable the setting and restart SQL I get the following errors:
* Event Time: 10/6/2008 10:05:10 AM
* MSSQLSERVER Error Event
* Event ID: 17182
* TDSSNIClient initialization failed with error 0x2740, status code 0xa.
* Event Time: 10/6/2008 10:05:10 AM
* MSSQLSERVER Error Event
* Event ID: 17182
* TDSSNIClient initialization failed with error 0x2740, status code 0x1.
* Event Time: 10/6/2008 10:05:10 AM
* MSSQLSERVER Error Event
* Event ID: 17826
* Could not start the network library becasue of an internal error in the network library.
To determine the cause, review the errors immediately proceding this one in the error log.
* Event Time: 10/6/2008 10:05:10 AM
* MSSQLSERVER Error Event
* Event ID: 17120
* SQL Server could not spawn FRunCM thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.
Need help other then reinstalling SQL....
Thanks,
Aaron
October 8, 2008 at 7:42 am
Even I had faced the same problem. I disabled VIA Protocol (Server) through configuration manager and reboot the server. Agree with benimposta.
October 8, 2008 at 4:59 pm
Seems like you might have something listening on TCP port configured for this instance or might be its blocked somehow.
Do you have more than one SQL Server instance on your machine? Did you install the instance you are having trouble with as a default instance?
MJ
May 13, 2009 at 11:04 pm
Hi
This problem usually arise when there are 2 instances of SQL Server and both are listening to same port.
Just change the port number for one of the instances and things would work fine!
HTH
March 20, 2010 at 12:52 am
Dear All,
1. Export "Regedit - HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.1\MSSQLServer\SuperSocketNetLib\Tcp\IP1" registry
2. Open the exported file in Notepad
3. Change the IP1 as IP2
4. Change the IP address of the current machine IP address in "IpAddress" REG_SZ value - Save and close the file
5. Start the SQL service
IMPORTANT NOTE:If the current IP address is available in IP1, Please add as 127.0.0.1 in IP2
---
All is well
ElanGovan Panchatcharam
June 4, 2010 at 1:43 am
Refer the MS artilce on
"
January 29, 2012 at 10:24 pm
Thanks 🙂
June 7, 2012 at 6:12 am
I had exactly this problem (with Errors on EventIDs 17120, 17182, 17826 & 17190), and could never find a solution, other than tediously re-installing SQL Server. I'd tried disabling VIA, using different Port numbers and just about all the other suggestions I found online, none of which helped at all.
It happened again today and I just couldn't face the re-install for some reason, but as I had to have it fixed I did one last trawl through google and finally found a solution. It was roughly as described in the following blog post:
http://www.sqlserverblogforum.com/tag/could-not-spawn-fruncm-thread/
Although at the final stage he has entered LOCAL SERVICE as the log on, that wouldn't work for me, but selecting Local System account and ticking "Allow service to interact with desktop" did. Whatever the reason, it seems accessing the Services through Control Panel gives slightly different behaviour than accessing it through the SQL Server Configuration Manager. No idea why, but it worked for me so thought I'd share in case it helped anyone else avoid a re-install
September 19, 2012 at 4:37 am
If you have tried to disable Name Pipe, Via or TCP/IP then by just enabling it i solved my problem
March 12, 2014 at 12:11 pm
niall1981 (6/7/2012)
I had exactly this problem (with Errors on EventIDs 17120, 17182, 17826 & 17190), and could never find a solution, other than tediously re-installing SQL Server. I'd tried disabling VIA, using different Port numbers and just about all the other suggestions I found online, none of which helped at all.It happened again today and I just couldn't face the re-install for some reason, but as I had to have it fixed I did one last trawl through google and finally found a solution. It was roughly as described in the following blog post:
http://www.sqlserverblogforum.com/tag/could-not-spawn-fruncm-thread/
Although at the final stage he has entered LOCAL SERVICE as the log on, that wouldn't work for me, but selecting Local System account and ticking "Allow service to interact with desktop" did. Whatever the reason, it seems accessing the Services through Control Panel gives slightly different behaviour than accessing it through the SQL Server Configuration Manager. No idea why, but it worked for me so thought I'd share in case it helped anyone else avoid a re-install
I just wanted to add that this solution just worked for me. I'm not sure why it happened in the first place. I rebooted the server after the most recent round of MS Patches and encountered this error.
Thanks!
Viewing 15 posts - 1 through 15 (of 20 total)
You must be logged in to reply to this topic. Login to reply