c0000005 EXCEPTION_ACCESS_VIOLATION after stopping/starting servi

On a nightly basis, SQL services are stopped to perform backups.
Afterwards the services are started.
This has been working for years.
Middle of last week, SQL has been failing to start.
SqlDumpExceptionHandler: Process 4844 generated fatal exception c0000005
EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
It requires a REBOOT to bring SQL back up.
No maintenace has been applied, Windows or SQL Server.
Win2K Server Standard Edition SP4
SQL Server SP4First question:
Have you seen this page yet? http://support.microsoft.com/?kbid=814572
Second question:
Why do you stop/start SQL to run backups? You can run "hot" backups
using the BACKUP command or a maintenance plan, then backup those
backup files.|||Tracey
Thanks for the prompt reply.
As for #2:
We have the oppurtunity to do so.
It's a cleaner backup.
I feel better with it.
If our nightly window gets tight, then we will switch to HOT backup only.
Yes, we do have a maintenance plan in place to do backups, reorg and index
maintenance.
This is not causing the prioblem.
We've been doing it this way for some time.
I'm the only SQL DBA this company has had.
Something changed last week.
It was not WIN maintenance.
It was not SQL Server maintenance.
As to #1:
Yes, I've seen that posting.
This is at SP4, or so I've been told, and has been for the past 6 months.
I used Microsoft Update and it indicates no fixes availible for Sql Server
2005.
Regards
Mark
"Tracy McKibben" wrote:
> First question:
> Have you seen this page yet? http://support.microsoft.com/?kbid=814572
> Second question:
> Why do you stop/start SQL to run backups? You can run "hot" backups
> using the BACKUP command or a maintenance plan, then backup those
> backup files.
>|||Found the problem.
It's the anti-virus software McAfee.
It upgraded itself the other week.
I've gotten around the problem by shutting down the McAfee services before
restarting the MS SQL services.
Right or wrong, it works.
"Mark Kuntz" wrote:
> On a nightly basis, SQL services are stopped to perform backups.
> Afterwards the services are started.
> This has been working for years.
> Middle of last week, SQL has been failing to start.
> SqlDumpExceptionHandler: Process 4844 generated fatal exception c0000005
> EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
> It requires a REBOOT to bring SQL back up.
> No maintenace has been applied, Windows or SQL Server.
> Win2K Server Standard Edition SP4
> SQL Server SP4