MSSQLService won''t run
-
Hi all-
I'm new this forum, and I have a big problem.
MSSQLService won't start automatically on system start (that's how the service is set up). It won't start in Enterprise manager either. It's MSSQL 7.0 SP4 (fully patched) running on Windows 2000 SP4 (fully patched).
I get this error: Connection could not be established for <servername> - General network error. Check your network documentation. ConnectionOpen (connect())..
I've made sure the logins for the SQL Server Service and Agent Match, and I've tried both NT and sa accounts. I've also installed a new NIC. The server pings by name and address and can surf the web just fine.
Here's the end of the SQL log file:
2005-07-19 04:06:12.71 kernel SQL Server terminating because of system shutdown.
2005-07-19 04:06:12.81 kernel LogEvent: Failed to report the current event. Operating system error = 31(A device attached to the system is not functioning.).
2005-07-19 04:06:19.92 spid1 Closing file d:\MSSQL7\data\hoau_Data.MDF.
2005-07-19 04:06:20.00 spid1 Closing file d:\MSSQL7\data\hoau_Log.LDF.
2005-07-19 04:06:20.10 spid1 Closing file d:\MSSQL7\data\stau_Data.MDF.
2005-07-19 04:06:20.14 spid1 Closing file d:\MSSQL7\data\stau_Log.LDF.
2005-07-19 04:06:20.21 spid1 Closing file d:\MSSQL7\data\HEAT_Nuera.mdf.
2005-07-19 04:06:20.25 spid1 Closing file d:\MSSQL7\data\HEAT_Nuera_log.ldf.
2005-07-19 04:06:20.32 spid1 Closing file D:\MSSQL7\data\stageDB.mdf.
2005-07-19 04:06:20.37 spid1 Closing file D:\MSSQL7\data\stageDB_log.ldf.
2005-07-19 04:06:20.48 spid1 Closing file d:\MSSQL7\DATA\northwnd.mdf.
2005-07-19 04:06:20.50 spid1 Closing file d:\MSSQL7\DATA\northwnd.ldf.
2005-07-19 04:06:20.62 spid1 Closing file d:\MSSQL7\DATA\pubs.mdf.
2005-07-19 04:06:20.65 spid1 Closing file d:\MSSQL7\DATA\pubs_log.ldf.
2005-07-19 04:06:20.89 spid1 Closing file d:\MSSQL7\DATA\msdbdata.mdf.
2005-07-19 04:06:20.93 spid1 Closing file d:\MSSQL7\DATA\msdblog.ldf.
2005-07-19 04:06:21.03 spid1 Closing file d:\MSSQL7\DATA\model.mdf.
2005-07-19 04:06:21.06 spid1 Closing file d:\MSSQL7\DATA\modellog.ldf.
2005-07-19 04:06:21.07 kernel SQL Server is terminating due to 'stop' request from Service Control Manager.
The system shutdown occurred as the result of the automatic Windows Update Agent, which executes around 4:00 am.
Three minutes after the shutdown, this error appeared in the event log:
The SQLServerAgent service depends on the MSSQLServer service which failed to start because of the following error: %%0
Now it won't come back up no matter what I do. Anyone seen this? I suspect either the Update Agent or one of the updates has hosed the MSSQLServer service. We're down all day. I'm desperate. All ideas welcome.
Thanks!
Eric
-
OK, so i tried checking to make sure port 1433 wasn't seized by some other app. I set a telnet server on the machine and defaulted it to port 1433, tested it, then switched it back to 23, then turned telnet server off.
About an hour later I simply started sql server from the command line. I closed the command prompt and about a minute or so after that i was able to start MSSQLService and SQL Agent from Services.
Go figure...
The last nine hours:
....
...
-
I have this same issue. MSSQL 2000 running on MS Windows 2000 SP4.
"The SQLSERVERAGENT service depends on the MSSQLSERVER service which failed to start because of the following error: %%0."
The services attempt to start but never will. I cannot stop or re-start them from any GUI. I can stop them from the command line and start them. However when the server is rebooted the services won't start. Not finding anything significant to help with troubleshooting in any of the logs.
-
In the System event log (OS), what's the error given for why the MSSQLSERVER service failed to start? Could it be the service account password changed (or expired)? You would see this error in the Security event log (OS) if you have the right auditing turned on for the server.
K. Brian Kelley
@kbriankelley
Viewing 4 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply