View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000454 | bareos-core | General | public | 2015-04-09 18:32 | 2016-01-14 13:53 |
| Reporter | akempiak | Assigned To | |||
| Priority | high | Severity | crash | Reproducibility | random |
| Status | closed | Resolution | suspended | ||
| Platform | Microsoft | OS | Windows Server | OS Version | 2012 R2 |
| Product Version | 14.2.2 | ||||
| Summary | 0000454: SQL Server Backup : ACCESS VIOLATION | ||||
| Description | We have a SQL Server which hosts a lot of databases. Randomly (or maybe not, maybe there's an explaination, I don't know), all the backup processes are failing one after the other, until SQL Server crashs itself (don't know why too). In SQL Server, here is the most significant error (and it's always the same for all failed backups): ***Stack Dump being sent to E:\MSSQL12.MSSQLSERVER\MSSQL\LOG\SQLDump0222.txt SqlDumpExceptionHandler: Process 17448 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process. * ******************************************************************************* * * BEGIN STACK DUMP: * 04/09/15 14:11:49 spid 17448 * Private server build. * * * Exception Address = 00007FF8F9908D40 Module(sqlmin+0000000002C88D40) * Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION * Access Violation occurred reading address FFFFFFFFFFFFFFFF * Input Buffer 356 bytes - * BACKUP DATABASE [DB_060_company] TO VIRTUAL_DEVICE='{303714 * E4-DE8E-481A-9F92-71CD5339E054}' WITH DIFFERENTIAL, BLOCKSIZE=65536, BUF * FERCOUNT=10, MAXTRANSFERSIZE=65536 My understanding of the error is that SQL Server fails to access to the "Virtual Device", which must be created by the Bareos client for the backup to be done (I think so). So, the error might come from a wrong virtual device communicated from the bareos client to SQL Server, or a virtual device "not really existing, or deleted for some reason before being used". That's why I'm opening a issue here. | ||||
| Steps To Reproduce | Running a lot of backups seem to increase probability to happen. | ||||
| Additional Information | I could send you the SQLDump file. We are trying to open and read it. | ||||
| Tags | No tags attached. | ||||
 |
According to our analysis, it could come from a SQL Server known issue. We have to update our SQL Server asap to see if it's linked. |
|
|
Hello, we haven't seen this problem at other sites. Could also be a problem of the MSSQL server itself. Have you applied all available patches? |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2015-04-09 18:32 | akempiak | New Issue | |
| 2015-04-10 12:18 | akempiak | Note Added: 0001681 | |
| 2015-11-06 17:20 | maik | Note Added: 0001937 | |
| 2015-11-06 17:20 | maik | Status | new => feedback |
| 2016-01-14 13:53 | mvwieringen | Status | feedback => closed |
| 2016-01-14 13:53 | mvwieringen | Resolution | open => suspended |
