Backup Exec Job Engine Service crashes when more than 1 tape is cataloged.

  • Article ID:100028617
  • Modified Date:
  • Product(s):


Backup Exec Job Engine Service crashes when more than 1 tape is cataloged.

Error Message

Event Viewer reports :

Log Name:      Application
Source:        Application Error
Date:          02.12.2012 23:00:34
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Faulting application name: bengine.exe, version: 14.0.1798.109, time stamp:
Faulting module name: ntdll.dll, version: 6.1.7601.17725, time stamp: 0x4ec4aa8e
Exception code: 0xc0000374
Fault offset: 0x00000000000c40f2
Faulting process id: 0x11e8
Faulting application start time: 0x01cdd0b9ddd8ffa6
Faulting application path: C:\Program Files\Symantec\Backup Exec\bengine.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll


Workaround :

Perform slow catalog.

Deselect Use Storage-Based Catalog from Backup Exec Icon (located at top left corner of the console) -> Configuration and Settings -> Backup Exec Settings -> Catalog and run the catalog.

Veritas Corporation has acknowledged that the above-mentioned issue is present in the current version(s) of the product(s) mentioned at the end of this article. Veritas Corporation is committed to product quality and satisfied customers.
This issue is currently under investigation by Veritas Corporation. Pending the outcome of the investigation, this issue may be resolved by way of a patch or hotfix in current or future revisions of the software. However, this particular issue is not currently scheduled for any release.  If you feel this issue has a direct business impact for you and your continued use of the product, please contact your Veritas Sales representative or the Veritas Sales group to discuss these concerns.  For information on how to contact Veritas Sales, please see Please be sure to refer back to this document periodically as any changes to the status of the issue will be reflected here.

Customers experiencing this issue are encouraged to contact Veritas Technical Support as data is still being collected to assist in resolving this issue.

Was this content helpful?

Get Support