Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

arcserve sql db backup agent vdi.log error

Status
Not open for further replies.

cscw88

MIS
Nov 6, 2003
20
SG
using arcserve 2000 to backup database receive error in
VDI.log:

----------------------------------------------
2006/10/05 02:03:24 pid(1948) tid(500)
Error on DBASQL70TID500VD0
Error at TriggerAbort: invoked

----------------------------------------------
2006/10/05 02:03:43 pid(1312) tid(1892)
Error on DBASQL70TID500VD0
Error at SVDS::Open: Dup(stateEvent) Status Code: 6, x6
Explanation: The handle is invalid.

----------------------------------------------
2006/10/05 02:03:45 pid(1948) tid(500)
Error on DBASQL70TID500VD0
Error at TriggerAbort: invoked

----------------------------------------------
2006/10/05 02:03:46 pid(1948) tid(500)
Error on DBASQL70TID500VD0
Error at TriggerAbort: StateEvent Status Code: 6, x6
Explanation: The handle is invalid.

----------------------------------------------
2006/10/05 02:03:46 pid(1948) tid(500)
Error on DBASQL70TID500VD0
Error at TriggerAbort: CompletionSem Status Code: 6, x6
Explanation: The handle is invalid.

----------------------------------------------
2006/10/05 02:03:46 pid(1948) tid(500)
Error on DBASQL70TID500VD0
Error at CVDS::Cleanup: Close(State) Status Code: 6, x6
Explanation: The handle is invalid.

----------------------------------------------
2006/10/05 02:03:47 pid(1948) tid(500)
Error on DBASQL70TID500VD0
Error at CVDS::Cleanup: Close(CompleteSem) Status Code: 6, x6
Explanation: The handle is invalid.

MS SQL Server version is 2000.

Pls help. Thanks

 
Patch up arcserve and give more information from the dbasql.log - the vdi.log isn't that useful without it.
 

can't find anything from the dbasql.log file.

I notice that we can turn on the debug mode for the backup agent log file(from registry setting), dbasql.trc or dbasql60.trc to trace the problem, do you think it is advisable to do that?

The backup agent release notes mention that it can be only be turn on only when ca support engineer ask us to do so. why is that so? any impact when we turn on the dbasql.trc log ourselves?
 
I'm tempted to turn on the debug registry key for the sql backup agent to generate the dbasql.trc or dbasql60.trc file for me to trace and resolve the issue.

Can anyone here advise me will there be any impact on the server/system if I turn on this debug mode to generate the trace file?

Thks for help
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top