cancel
Showing results for 
Search instead for 
Did you mean: 

An error occurred on a query to database msdb

Derek_Poh
Level 3

Hi,

I have this error on my backup. Please advise.

V-79-57344-33938 -
An error occurred on a query to database msdb.
V-79-57344-33938 - Database 'msdb' cannot be opened. It has been marked SUSPECT by recovery. See the SQL Server errorlog for more information.

2 REPLIES 2

horton33
Not applicable
I am receiving the same error codes:
 
Click an error below to locate it in the job log


Backup- MIBT01
AOFO: Initialization failure on: "C:". Advanced Open File Option used: Microsoft Volume Shadow Copy ...SQL Prepare for Freeze failed for snapshot.AOFO: Initialization failure on: "E:". Advanced Open File Option used: Microsoft Volume Shadow Copy ...SQL Prepare for Freeze failed for snapshot.AOFO: Initialization failure on: "G:". Advanced Open File Option used: Microsoft Volume Shadow Copy ...SQL Prepare for Freeze failed for snapshot.AOFO: Initialization failure on: "serverX". Advanced Open File Option used: Microsoft Volume Shadow ...SQL Prepare for Freeze failed for snapshot.AOFO: Initialization failure on: "Shadow?Copy?Components". Advanced Open File Option used: Microsoft...SQL Prepare for Freeze failed for snapshot.


Backup- MIBT01
V-79-57344-33938 - An error occurred on a query to database DB1.V-79-57344-33938 - The log file for database 'DB1' is full. Back up the transaction log for the database to free up ...V-79-57344-33938 - An error occurred on a query to database DB2.V-79-57344-33938 - 0x2000e208 (536928776)V-79-57344-33938 - An error occurred on a query to database distribution.V-79-57344-33938 - 0x2000e208 (536928776)V-79-57344-33938 - An error occurred on a query to database DB3.V-79-57344-33938 - 0x2000e208 (536928776)V-79-57344-33938 - An error occurred on a query to database BEDB.V-79-57344-33938 - 0x2000e208 (536928776)
This has only happened since the Easter break when I cancelled some jobs from running since I wouldn't be at work to change tapes, and no work was being done.

PaulD_Rus
Level 4
go to SQL Server Enterprise Manager>Management>SQL serverLog>Current
check all errros, find all databease with error "log is full"
then go to Databases/<your DB>/Properties>Transaction Log> increas space for logs
 
then go to Management>Current Activity>Process Info,  find all hang processes with command=backup and Application="Virtas backup exec"
kill all these procceses.
 
run BE job again.