Forum Discussion

davidn1's avatar
davidn1
Level 2
10 years ago
Solved

Backup Exec 2014 periodically crashes

BE 2014 SP2 with Hot Fix 227745 on W2K8 R2.

Hi all - I have an unpredicatable server that I reboot on a weekly basis as this tends to limit the crash, anyway, the crash is usually kicked off by the following error in the system event viewer which then triggers other errors:

EventID: 1 - Unexpected failure. Error code: 45D@01010016 (VDS Basic Provider) which then triggers:

EventID: 7034 - The Backup Exec Job Engine service terminated unexpectedly.  It has done this 1 time(s).

EventID: 57 - The system failed to flush data to the transaction log. Corruption may occur.

and in the Application event viewer and at the exact same time and EventID: 1

EventID: 33808 - An error occurred while processing a B2D command. Drive: ReadMTFData() ReadFile failed (D:\BEData\B2D018723.bkf) @16628498. Error=1117 

Have no idea which one triggers the other as the time stamps (including the seconds) are the same with EventID: 1 and EventID: 33808

Have others experienced this? - any tips would be welcome - thanks in advance - d

 

 

 

  • Update - Symantec support has advised me to carry out an OS repair so hopefully that will fix the issue...thanks guys for all your help!

  • There would be an event id 1000 logged if there is a process crash. What's the faulting module as mentioned in this event ?

  • VJware - as below:

     

    Faulting application name: bengine.exe, version: 14.1.1786.1103, time stamp: 0x54d50683
    Faulting module name: ntdll.dll, version: 6.1.7601.18798, time stamp: 0x5507b864
    Exception code: 0xc0000006
    Fault offset: 0x0000000000028fa2
    Faulting process id: 0xbd4
    Faulting application start time: 0x01d0afde2dbbf40c
    Faulting application path: D:\Symantec\Backup Exec\bengine.exe
    Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
    Report Id: 809988ef-210c-11e5-9867-a0369f0e5dca

     

    d

  • Have you noticed when does bengine.exe crash ? Is it during a specific activity such as a particular server's backup or during cataloging or verify etc ?

    Additionally, any errors/warnings logged just prior to the crash ?

    If not, I would recommend to log a formal support case as the support team can analyse the crash dump, additionally, it may be possible this issue is fixed in BE 15.

  • Yep, a normal backup is taking place + the errors logged are the one's listed above...there's heaps after the crash but I am presuming this is casued by the BE going down anyway...will log a formal support case and go from there so thanks for your help :)

  • Update - Symantec support has advised me to carry out an OS repair so hopefully that will fix the issue...thanks guys for all your help!