June 20, 2011 at 1:14 am
Hi,
Last night my SQLServer 2008 R2 stopped working; both SQL Server and SQL Server Agent had stopped. By starting them all came back online without a problem.
The error message I got is:
SQL Server is terminating because of fatal exception c0000005. This error may be caused by an unhandled Win32 or C++ exception, or by an access violation encountered during exception handling. Check the SQL error log for any related stack dumps or messages. This exception forces SQL Server to shutdown. To recover from this error, restart the server (unless SQLAgent is configured to auto restart).
After further investigation we found that it happened during full-backupping. Several databases had been backupped successfully until it occurred. The database that was to be back-upped works, and with error checking no errors were found.
One cause might be: Windows Update. Yesterday afternoon I installed all available Windows Updates. That went without a problem.
What is this problem? Can't find anything on Google, except that it might be a bug in SQL....
LATEST NEWS: it just happened again! No backups were running, nothing special was going on. In the logs there is nothing to be found that indicates a problem....
Thanks,
Raymond
June 20, 2011 at 6:50 am
I have experienced similar symptoms if the server engineers use WSUS (or similar) to automatically apply SQL Security fixes. If the kb's cant be installed successfully, I think the default behaviour is to stop the SQL Server services...
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply