SQL trans baclups failing with status 6, 0x80770004

HI,

Since we upgraded to 7.6.0.3 we happen to have Status 6 errors in our env. for SQL trans backups, and diff backups.

All backup log are returning the same error:

2014-11-19 11:04:19 - Info dbclient(pid=4548) INF - BACKUP STARTED USING        
2014-11-19 11:04:19 - Info dbclient(pid=4548) Microsoft SQL Server 2005 - 9.00.5069.00 (Intel X86)     
2014-11-19 11:04:19 - Info dbclient(pid=4548) Aug 22 2012 16:01:52         
2014-11-19 11:04:19 - Info dbclient(pid=4548) Copyright (c) 1988-2005 Microsoft Corporation        
2014-11-19 11:04:19 - Info dbclient(pid=4548) Standard Edition on Windows NT 5.2 (Build 3790: Service Pack 2)  
2014-11-19 11:04:19 - Info dbclient(pid=4548) Batch = C:\Program Files\VERITAS\NetBackup\DbExt\MsSql\Trans.bch, Op# = 4      
2014-11-19 11:04:19 - Info dbclient(pid=4548) INF - Using backup image SESOLSQL01DAT.MSSQL7.SESOLSQL01DAT.trx.Flexdb.~.7.001of001.20141119110425..C       
2014-11-19 11:04:19 - Info dbclient(pid=4548) INF - backup log "Flexdb" to VIRTUAL_DEVICE='VNBU0-4548-3440-1416391467' with  stats = 10, blocksize = 65536, maxtransfersize = 4194304, buffercount = 2
2014-11-19 11:04:19 - Info dbclient(pid=4548) INF - Number of stripes: 1, Number of buffers per stripe 2.
2014-11-19 11:04:20 - Info dbclient(pid=4548) INF - Created VDI object for SQL Server instance <SESOLSQL01DAT>. Connection timeout is <300> seconds.
2014-11-19 12:32:18 - Info dbclient(pid=4548) ERR - Error in VxBSACreateObject: 3.       
2014-11-19 12:32:18 - Info dbclient(pid=4548)     CONTINUATION: - System detected error, operation aborted.  
2014-11-19 12:32:18 - Info dbclient(pid=4548) ERR - Error in GetCommand: 0x80770004.       
2014-11-19 12:32:18 - Info dbclient(pid=4548)     CONTINUATION: - An abort request is preventing anything except termination actions.
2014-11-19 12:32:21 - Info dbclient(pid=4548) ERR - Error in VDS->Close: 0x80770004.       
2014-11-19 12:32:21 - Info dbclient(pid=4548)     CONTINUATION: - An abort request is preventing anything except termination actions.

I searched the forum, and I want to exclude possible causes:

• clustered sql servers(they are not)
• db named with "-" hyphen
• and lack of Default-Application-Backup schedules.
• no .bch file has the policy name in it.

Could it be:

http://www.symantec.com/business/support/index?pag...

What information can I provide in order to continue with troubleshooting.

Thank you.

//George