The error "Database Query Failure. See the job log for details" (e0008492 HEX or a0008492 HEX) is reported while Backing up Microsoft SQL 2000/2005 Databases

Article:TECH67379  |  Created: 2009-01-18  |  Updated: 2013-07-05  |  Article URL http://www.symantec.com/docs/TECH67379
Article Type
Technical Solution


Issue



The error "Database Query Failure. See the job log for details" (e0008492 HEX or a0008492 HEX) is reported while Backing up Microsoft SQL 2000/2005 Databases


Error



V-79-57344-33938 - Write on '_00__37125b2a_1056_4c82_8efd_8c441246c270_' failed, status = 995. See the SQL Server error log for more details.
The item \ in use - skipped.

The SQL 2005 Log error Message shows the error below in the path: C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files

For SQL 2000 the path would be: C:\Program Files\Microsoft SQL Server\80\Setup Bootstrap\LOG.

2009-01-20 01:51:36.91 spid51    BackupMedium::ReportIoError: write failure on backup device <database name >_00__235c44db_22b5_44e9_bc6d_1a789514dfbb_'. Operating system error 995(The I/O operation has been aborted because of either a thread exit or an application request.).

009-01-20 01:51:36.95 spid51    BackupVirtualDeviceFile::RequestDurableMedia: Flush failure on backup device <database name >_00__235c44db_22b5_44e9_bc6d_1a789514dfbb_'. Operating system error 995(The I/O operation has been aborted because of either a thread exit or an application request.).
 
 
Beremote log might show the following:
 
[1684] 07/04/09 00:14:40 SQL Error GUID: 5f8fe30
[1684] 07/04/09 00:14:40 SQL Error Source: Microsoft OLE DB Provider for SQL Server
[1684] 07/04/09 00:14:40 SQL Error Description: [DBNETLIB][ConnectionRead (recv()).]General network error. Check your network documentation.
[1684] 07/04/09 00:14:40 SQL Error State: 08S01
[1684] 07/04/09 00:14:40 SQL Error Number: 11
[1684] 07/04/09 00:14:40 Operation thread exiting.
 
[2488] 07/04/09 00:14:44 LP_ENV::MsgError: error 0xe0008492 processing object \ABC
 
 
Events are logged in as shown below:
 
Event Type: Error
Event Source: SQLVDI
Event Category: None
Event ID: 1
Date: 1/29/2009
Time: 1:13:25 PM
User: N/A
Computer: SERVER1
Description:      SQLVDI: Loc=TriggerAbort. Desc=invoked. ErrorCode=(0). Process=984. Thread=5752. Client. Instance=NEXTECH. VD=Global\RESTORE_restore__MemoryName_0.

Solution



This issue is pertaining to SQLVDI (Virtual Device Interface) and is resolved by applying the Microsoft Hot fix as mentioned in the following article:
 
FIX: Error messages and an event may be logged when you use the Virtual Device Interface in SQL Server 2005 or in SQL Server 2000
 

 

Supplemental Materials

SourceUMI
ValueV-79-57344-33938
Description

Write on '_00__37125b2a_1056_4c82_8efd_8c441246c270_' failed, status = 995. See the SQL Server error log for more details.
The item \ in use - skipped.


SourceEvent ID
Value1
Description

SQLVDI: Loc=TriggerAbort. Desc=invoked. ErrorCode=(0). Process=984. Thread=5752. Client. Instance=NEXTECH. VD=Global\RESTORE_restore__MemoryName_0.


SourceError Code
Value0xe0008492
Description

Database Query Failure.



Legacy ID



318417


Article URL http://www.symantec.com/docs/TECH67379


Terms of use for this information are found in Legal Notices