Sunday, October 18, 2015

BACKUP DATABASE is terminating abnormally - Process 4424 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process

One of my clients recently encountered this error (they are using SQL Server 2014). Their database backup job would fail with the following error:

Command: BACKUP DATABASE [Databas_Name] TO DISK = N'E:\Backup\Database_Name\FULL\DB_Name_FULL_20151013_210000.bak' WITH CHECKSUM, COMPRESSIONMsg 3013, Level 16, State 1, Server SERVER-NAME, Line 1  BACKUP DATABASE is terminating abnormally.

Also, the error log, referenced a dump file

Stack Dump being sent to E:\Databases\MSSQL10.MSSQLSERVER\MSSQL\LOG\SQLDump0169.txt     

I opened up the dump file and saw the below message. As you can guess, there is nothing useful on what the error message is about and how to resolve it.

This file is generated by Microsoft SQL Server  version 12.0.2000.8  upon detection of fatal unexpected error. Please return this file, the query or program that produced the bugcheck, the database and the error log, and any other pertinent information with a Service Request. 

SqlDumpExceptionHandler: Process 4424 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.

Exception Address = 000007FEF0A68D40 Module(sqlmin+0000000002C88D40)                                        
Exception Code    = c0000005 EXCEPTION_ACCESS_VIOLATION                                                      
Access Violation occurred reading address FFFFFFFFFFFFFFFF                                                      

As you can guess, there is nothing useful on what the error message is about and how to resolve it. I found a KB article that talks about this error and it suggested installing a Cumulative Update.  

Resolution: Since SQL Server 2014 SP1 was available, I was more comfortable installing SP1 instead of a Cumulative Update. We installed SP1 and the issue got resolved. 

Hope this helps. If you encountered this error and used to a different method to fix the issue, please let me know (via comments)



No comments:

Post a Comment