Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase 12»»

Not able to restart the MSSQL Server Services Expand / Collapse
Author
Message
Posted Monday, October 3, 2005 11:15 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Friday, February 8, 2008 2:09 AM
Points: 2, Visits: 2

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


Post #225702
Posted Wednesday, October 5, 2005 11:54 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Wednesday, March 22, 2006 2:23 PM
Points: 254, Visits: 1

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.




Cheers,

david russell

Post #226332
Posted Tuesday, October 17, 2006 9:43 PM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Sunday, July 3, 2011 2:20 AM
Points: 113, Visits: 77
Happened to me, on testing environment using SQL Server 2005 Enterprise. Anybody knows how to solve this problem other than re-install? 
Post #316113
Posted Wednesday, October 18, 2006 7:14 AM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Wednesday, September 17, 2014 6:29 PM
Points: 344, Visits: 290

Can you please post recent ErrorLog? If SQL is not coming up, error log is the first place to start.

 

 

Post #316214
Posted Saturday, December 29, 2007 5:38 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Saturday, December 29, 2007 5:25 AM
Points: 1, Visits: 0
OPEN THE SQL SERVER CONFIGRATION MANAGER
CLICK THE SQL SERVER 2005 NETWORK CONFIGRATION

DISABLED VIA.
Post #437321
Posted Wednesday, October 8, 2008 5:54 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Wednesday, October 8, 2008 5:48 AM
Points: 1, Visits: 0
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
Post #582476
Posted Wednesday, October 8, 2008 7:42 AM
SSC Journeyman

SSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC Journeyman

Group: General Forum Members
Last Login: Sunday, November 24, 2013 7:15 PM
Points: 88, Visits: 93
Even I had faced the same problem. I disabled VIA Protocol (Server) through configuration manager and reboot the server. Agree with benimposta.
Post #582549
Posted Wednesday, October 8, 2008 4:59 PM
SSCommitted

SSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommitted

Group: General Forum Members
Last Login: Thursday, May 22, 2014 7:04 AM
Points: 1,688, Visits: 8,766
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
Post #582987
Posted Wednesday, May 13, 2009 11:04 PM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: 2 days ago @ 11:27 PM
Points: 273, Visits: 725
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
Post #716645
Posted Saturday, March 20, 2010 12:52 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Tuesday, February 22, 2011 8:26 PM
Points: 1, Visits: 11
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
http://gofrugal.com
Post #886862
« Prev Topic | Next Topic »

Add to briefcase 12»»

Permissions Expand / Collapse