"A communications failure has occurred with a SQL Server resource." occurs when attempting to backup an SQL Database

Article:TECH124776  |  Created: 2010-01-08  |  Updated: 2012-07-09  |  Article URL http://www.symantec.com/docs/TECH124776
Article Type
Technical Solution


Issue



"A communications failure has occurred with a SQL Server resource." occurs when attempting to backup an SQL Database.


Error



0xe000ff19 - A communications failure has occurred with a SQL Server resource. V-79-57344-65305 - The database server is not responding. Backup set canceled.

The errors below may also show in the event logs.
Event Type: Error
Event Source: SQLVDI
Event Category: None
Event ID: 1
Date: 3/8/2010
Time: 10:01:44 AM
User: N/A
Computer: SERVER
Description:
SQLVDI: Loc=TriggerAbort. Desc=invoked. ErrorCode=(0). Process=1616. Thread=4376. Server. Instance=MSSQLSERVER. VD=Global\NovaStorBackup_00__0dfb0e38_b466_47af_9c51_7d13107e9b12__SQLVDIMemoryName_0.


Event Type: Error
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 18210
Date: 3/8/2010
Time: 10:01:45 AM
User: administrator
Computer: SERVER
Description:
BackupVirtualDeviceFile::RequestDurableMedia: Flush failure on backup device '_00__0dfb0e38_b466_47af_9c51_7d13107e9b12_'. Operating system error 995 (The I/O operation has been aborted because of either a thread exit or an application request.).


Event Type: Error
Event Source: MSSQLSERVER
Event Category: (6)
Event ID: 3041
Date: 3/8/2010
Time: 10:01:45 AM
User: administrator
Computer: SERVER
Description:
BACKUP failed to complete the command BACKUP DATABASE. Check the backup application log for details
.


Solution




   1. Make sure that Service pack 4 is installed on SQL 2005 instance.
 
   2. Make sure that Service pack 1 is installed on SQL 2008 instance.

   3. If the error continues, re-register both the "SQLVDI.dll" files which are located in the following SQL Directory locations

   X:\Program Files\Microsoft SQL Server\80\COM
   X:\Program Files\Microsoft SQL Server\80\Tools\Binn

   Register both the files with the "Regsvr32" command and run the backup job again.
 

Supplemental Materials

SourceUMI
ValueV-79-57344-65305
Description

A communications failure has occurred with a SQL Server resource. The database server is not responding.


SourceEvent ID
Value3041
Description

BACKUP failed to complete the command BACKUP DATABASE. Check the backup application log for details
 


SourceEvent ID
Value18210
Description

BackupVirtualDeviceFile::RequestDurableMedia: Flush failure on backup device '_00__0dfb0e38_b466_47af_9c51_7d13107e9b12_'. Operating system error 995 (The I/O operation has been aborted because of either a thread exit or an application request.).
 


SourceEvent ID
Value1
Description

SQLVDI: Loc=TriggerAbort. Desc=invoked. ErrorCode=(0). Process=1616. Thread=4376. Server. Instance=MSSQLSERVER. VD=Global\NovaStorBackup_00__0dfb0e38_b466_47af_9c51_7d13107e9b12__SQLVDIMemoryName_0.
 


SourceError Code
Value0xe000ff19
Description

A communications failure has occurred with a SQL Server resource



Legacy ID



346991


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


Terms of use for this information are found in Legal Notices