Event ID 57345 "Delete failed because the object being deleted no longer exists in database"
Article ID: 100034173
Updated On:
Description
Error Message
Log Name: Application
Source: Backup Exec
Date: 6/16/2017 4:16:53 AM
Event ID: 57345
Task Category: (65535)
Level: Information
Keywords: Classic
User: N/A
Computer:
Description:
Database Exception Context:m_QueryTimeoutInSeconds=30 sql={? = CALL DBO.DELETEINSTALLJOBINSTANCE(?)} Error:-536837662: :: -2147217900:Delete failed because the object being deleted no longer exists in database.
:: DB Error Set 0: native=0x61040001 source=Microsoft OLE DB Provider for SQL Server hr=0x80040e14 Delete failed because the object being deleted no longer exists in database.Cause
Entries related to install job instance, referenced in the message above, failed to delete from Backup Exec Database resulting in this event.
Resolution
1. Launch SGMON.exe from BE Install Path. Click on Capture -> Custom and select Beserver checkbox.
From SGMON Debug Tab -> Click Settings -> Highlight Backup Exec Server -> Select Job Log and set it to high
2. Let the informational alert pop up in the event viewer with the SGMON running (with above settings so that the error is captured)
Look for the following errors in the Debug to find the job which may be causing the following event :
3. Note the name of the Job for which this message repeats in Event viewer from the above log snippet.
4. Delete the Job if it shows in Backup Exec User Interface (BE UI). If the Job is not seen in BE UI then contact Backup Exec Technical Support to get this Job removed to stop these events in event viewer.
From SGMON Debug Tab -> Click Settings -> Highlight Backup Exec Server -> Select Job Log and set it to high
2. Let the informational alert pop up in the event viewer with the SGMON running (with above settings so that the error is captured)
Look for the following errors in the Debug to find the job which may be causing the following event :
BESERVER: [06/16/17 03:50:44] [5880] 16 JobManager: FlushCache starts
BESERVER: [06/16/17 03:50:44] [5880] 16 CJobManager::FlushCache( ): delete jobs
BESERVER: [06/16/17 03:50:44] [5880] 16 CJobManager::FlushCache( ): deleting
BESERVER: [06/16/17 03:50:44] [5880] 16 ******** JobManager: Get(CBemJobInst)
BESERVER: [06/16/17 03:50:44] [5880] 16 CJobManagerBO::Delete Fetch Lock
BESERVER: [06/16/17 03:50:44] [5880] -1 SQLLog(49139):Database Exception Context:m_QueryTimeoutInSeconds=30 sql={? = CALL DBO.DELETEINSTALLJOBINSTANCE(?)} Error:-536837662: :: -2147217900:Delete failed because the object being deleted no longer exists in database. :: DB Error Set 0: native=0x61040001 source=Microsoft OLE DB Provider for SQL Server hr=0x80040e14 Delete failed because the object being deleted no longer exists in database.
BESERVER: [06/16/17 03:50:44] [5880] 16 CJobManagerBO::Delete Release Lock lockTrackerID=1048
BESERVER: [06/16/17 03:50:44] [5880] -1 Error(16/18): 1627652097:Database Exception 0x61040001, source:Microsoft OLE DB Provider for SQL Server, result:0x80040e14, Delete failed because the object being deleted no longer exists in database.
BESERVER: [06/16/17 03:50:44] [5880] 16 CJobManager::FlushCache( ): can't delete the adhoc job instance!
BESERVER: [06/16/17 03:50:44] [5880] 16 JobManager: FlushCache ends3. Note the name of the Job for which this message repeats in Event viewer from the above log snippet.
BESERVER: [06/16/17 03:50:44] [5880] 16 CJobManager::FlushCache( ): deleting 4. Delete the Job if it shows in Backup Exec User Interface (BE UI). If the Job is not seen in BE UI then contact Backup Exec Technical Support to get this Job removed to stop these events in event viewer.
Issue/Introduction
Event ID 57345 "Delete failed because the object being deleted no longer exists in database"
Was this article helpful?
Yes
No
Powered by
