SQL Server Service Shutting down unexpectedly

Question

SQL Server Service Shutting down unexpectedly

kelseyv

Ten Centuries

Points: 1074
More actions
July 26, 2004 at 4:39 pm

#85930

Hi All,
Strange thing happened this AM, my SQL server service shut down.
The agent restarted it but due to active connections I had many users with errors.
Then it happened again about 45 minutes ago.
It seems like it happens when doing a TLog backup. It does 2 dbs successfully then dies. I'm not sure if it's on completion of the second or start of the 3rd. But if I run the job again it completes with no errors.
SQL 2000 SP3 Windows Server 2003 SQL LiteSpeed for both db and TLog backups Raid 1+0
I have not changed anything in months on this box. We did have a power surge last week and had to resseed a drive but there are no hardware errors being reported. There is more than half the disk free.
The exception log has 07/26/04 15:45:46 spid 0 Exception 0xc0000005 EXCEPTION_ACCESS_VIOLATION at 0x0056B969
We haven't done any application upgrades recently either.
I'm really at a loss as what to check. Any help is appreciated.
THanks
K

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply

Steve Jones - SSC Editor SSC Guru Points: 736162 More actions · Answer 1

The error log has that error? That usually is a corrupt file of some sort. Hve you run checkdb? Might need to contact MS PSS if it continues.

Also, can you manually run a log backup of the last db that is tried before it shuts down?

Allen Cui-55137 SSC Guru Points: 51650 More actions · Answer 2

Also check machine application and system logs for any information may related. You may also have SQL Server dump file created in SQL Server log folder. In order to analyze them, you have to send it to Microsoft.

kelseyv Ten Centuries Points: 1074 More actions · Answer 3

Other than the exception log I couldn't find any dump files. I looked at all files modified yesterday.

I'm getting a battery needs reconditioning on a controller but that was the only unusual thing on the box.

Did a backup last night that includes a CheckDb and reindexing on all user dbs including the one that seemed to be causing the error and everything was fine. It found no errors. It ran in the same amount of time as it normally does.

I rebooted the machine as well after the back up.

It's been 16 hours since the last unexpected termination.

THanks for your help.

K