All,
I've been using SQL2000 on the same Win2003 server for five years. I have probably ten databases, only two of which are used daily. The server itself is over-spec'd for the small number of users we now have.
Every morning I check the status of the previous night's maintenence plans. This morning I found about half had failed - integrity/optimisations & backup.
I kicked all users off the system and attempted to stop and restart the SQL service before manually starting the failed jobs. It wouldn't restart. Error below:
*******************************************
Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7000
Date: 11/09/2009
Time: 10:24:11
User: N/A
Computer: S6
Description:
The MSSQLSERVER service failed to start due to the following error:
The service did not respond to the start or control request in a timely fashion.
*******************************************
Guessing that this was quite a bad sign, it happening on our busiest day of the week, and not knowing what else to do I rebooted the server hoping that 'somehow' it would sort itself out. The service didn't start with the OS as it normally does so I tried to start it using Service Manager.
Still no joy and by now I was worried. (Same error)
Way back in the days when we used NT on desktops, they would occasionally start behaving strangely and I'd just re-apply the latest SP to get them back to normal so, I tried installing SQL2000 SP4 again to see if that would do the trick. It errored and wouldn't install.
At this point all seemed lost so just for the hell of it I tried starting the service using Service Manager as before. It worked.
My problem is that I'm not getting anywhere fast searching for answers and if it's done it once it'll do it again. Thus I need to know what's causing it.
Any pointers or even 'shot in the dark' ideas would be VERYmuch appreciated!
I've been using SQL2000 on the same Win2003 server for five years. I have probably ten databases, only two of which are used daily. The server itself is over-spec'd for the small number of users we now have.
Every morning I check the status of the previous night's maintenence plans. This morning I found about half had failed - integrity/optimisations & backup.
I kicked all users off the system and attempted to stop and restart the SQL service before manually starting the failed jobs. It wouldn't restart. Error below:
*******************************************
Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7000
Date: 11/09/2009
Time: 10:24:11
User: N/A
Computer: S6
Description:
The MSSQLSERVER service failed to start due to the following error:
The service did not respond to the start or control request in a timely fashion.
*******************************************
Guessing that this was quite a bad sign, it happening on our busiest day of the week, and not knowing what else to do I rebooted the server hoping that 'somehow' it would sort itself out. The service didn't start with the OS as it normally does so I tried to start it using Service Manager.
Still no joy and by now I was worried. (Same error)
Way back in the days when we used NT on desktops, they would occasionally start behaving strangely and I'd just re-apply the latest SP to get them back to normal so, I tried installing SQL2000 SP4 again to see if that would do the trick. It errored and wouldn't install.
At this point all seemed lost so just for the hell of it I tried starting the service using Service Manager as before. It worked.
My problem is that I'm not getting anywhere fast searching for answers and if it's done it once it'll do it again. Thus I need to know what's causing it.
Any pointers or even 'shot in the dark' ideas would be VERYmuch appreciated!
