Forum Discussion

Morph27's avatar
Morph27
Level 4
17 years ago

I'm using BackupExec 11d Rev 6235 on Windows 2003 R2 SP2....

I'm using BackupExec 11d Rev 6235 on Windows 2003 R2 SP2. Backup has been running fine for 6 months. It started failing last week. I restarted the server on Friday morning. Friday evening backup failed again.
 
Searching symantec forum leads me to similar posts but there are no solution. Therefore I'm posting this error hoping that someone has a solution to this.
 
Here's what I see in W2k3 logs:
 
Event Type: Error
Event Source: Application Error
Event Category: (100)
Event ID: 1000
Date:  9/8/2007
Time:  8:08:11 AM
User:  N/A
Computer: WIN2003SRV
Description:
Faulting application bengine.exe, version 11.0.6235.0, faulting module msvcr71.dll, version 7.10.3052.4, fault address 0x00002eee.
 
---------------------------------------------
 
Event Type: Information
Event Source: DrWatson
Event Category: None
Event ID: 4097
Date:  9/8/2007
Time:  8:08:13 AM
User:  N/A
Computer: WIN2003SRV
Description:
The application, C:\Program Files\VERITAS\Backup Exec\bengine.exe, generated an application error The error occurred on 09/08/2007 @ 08:08:12.171 The exception generated was c0000005 at address 7C342EEE (MSVCR71!memcpy)
 
-------------------------------------------
 
Event Type: Error
Event Source: Backup Exec
Event Category: None
Event ID: 34113
Date:  9/8/2007
Time:  8:23:13 AM
User:  N/A
Computer: WIN2003SRV
Description:
Backup Exec Alert: Job Failed
(Server: "WIN2003SRV") (Job: "Friday") Friday -- The job failed with the following error: The Backup Exec job engine system service is not responding.
11.x and Earlier
Backup and Recovery
Backup Exec

10 Replies

Sort By
  • J_Peralta's avatar
    J_Peralta
    Level 4
    17 years ago
    I've got a very similar problem except:

    - 11D Rev 6235, Windows 2003 R2 SP1.
    - It happened on a quick erase of a tape.
    - Event entry description reads "Faulting application BkupExec.exe, version 11.0.6235.0, faulting module comctl32.dll, version 6.0.3790.2778, fault address 0x0001bc19."

    I've only gotten three times previously, twice back in February one was an error on BEEngine.exe, the other on BkupExec.exe.  The only other time was in May and the app. was BkupExec.exe.

    I've never noticed anything that it is consistent on.  This time it just happened to be on an erase of a tape.

    Any suggestions are always appreciated.
  • ariesbabu's avatar
    ariesbabu
    Level 4
    17 years ago
    Hello
     
    You need to give mroe information.
     
    What are you backing-up?
     
    We can examine crash dumps.
     
    Cheers.
  • Morph27's avatar
    Morph27
    Level 4
    17 years ago
    I'm backing up Windows 2003 R2 file server + 1 Exchange server. Remote and Exchange agent is installed. Total data is around 102GB (90GB file server, 12GB Exchange). I'm using LTO2 external tape drive (200GB/400GB capacity).
  • Morph27's avatar
    Morph27
    Level 4
    17 years ago
    Strange thing happened last night. Backup completed successfully. All I did was flipping Resource Order. It could very well be a coincidence.
     
    Here's what exactly happens in chronological order:

    1) Resource Order: backup Server1 (domain controller) then Server2 (Exchange member server). Backup works great for about 6 months. No problem whatsoever.

    2) I change Resource Order to backup Server2 (Exchange) then Server1. I got 1 successful backup followed by 2 failures on the next 2 nighly backups (see original post for errors).

    3) Last night I changed it back to backup Server1 then Server2. Backup was successful.

    This is weird.



    Message Edited by Ronnie J on 09-11-2007 10:28 AM
  • ariesbabu's avatar
    ariesbabu
    Level 4
    17 years ago
    It is possible that the resource order required a continuous stratch of the tape. Changing the resource order might have backed up the first resource first and the second resource ran out of tape space.
     
    The job must have waited for a long time for you to put in another tape and eventually the job engine service must have failed.
     
    As long as the backup is working it is great. However if you want to backup server2 first. Check the tape capacity and media set(overwrite protection and append protection)settings. For example start the job in a scratch media.
     
    Hope this helps.
  • Morph27's avatar
    Morph27
    Level 4
    17 years ago

    That can't be it. As I said before I got an LTO2 tape with 200GB capacity (uncompressed). I'm only backing up about 100GB (uncompressed) data. Everything fits in 1 tape. If it works 1 way (Server1 then Server2), it should work the other way too (Server2 then Server1). Btw, backup crashed during verify.

    I got a second successful backup since I posted this problem last week. Again, the resource order is the same as original resource order. The reason I changed the order is because I want Exchange online backup to run either before or after Exchange online maintenance (scheduled to run between 1 am to 5 am). I don't want Exchange backup and online maintenance to run simultaneously.



    Message Edited by Ronnie J on 09-12-2007 09:53 AM
  • Morph27's avatar
    Morph27
    Level 4
    17 years ago
    (9/13) Update
     
    I got another bengine.exe crash last night (backup did not start at all). No changes were made. This time it says:
     
    Event Type: Error
    Event Source: Application Error
    Event Category: (100)
    Event ID: 1000
    Date:  9/12/2007
    Time:  9:00:10 PM
    User:  N/A
    Computer: WIN2003SRV
    Description:
    Faulting application bengine.exe, version 11.0.6235.0, faulting module ntdll.dll, version 5.2.3790.3959, fault address 0x0002c855.
     
    The other 2 crashes earlier this month (crash during verify):
     
    Event Type: Error
    Event Source: Application Error
    Event Category: (100)
    Event ID: 1000
    Date:  9/7/2007
    Time:  12:40:39 AM
    User:  N/A
    Computer: WIN2003SRV
    Description:
    Faulting application bengine.exe, version 11.0.6235.0, faulting module bengine.exe, version 11.0.6235.0, fault address 0x00153eff.
    Event Type: Error
    Event Source: Application Error
    Event Category: (100)
    Event ID: 1000
    Date:  9/8/2007
    Time:  8:08:11 AM
    User:  N/A
    Computer: WIN2003SRV
    Description:
    Faulting application bengine.exe, version 11.0.6235.0, faulting module msvcr71.dll, version 7.10.3052.4, fault address 0x00002eee.
     
    Faulting module is different on every crash. This problem just started this month. I've been using BE v11d for about 6 months and it's been running fine.
     
    Back in the old Win NT/2000 days, I rarely had problem with BackupExec version 8.x and older. Why is BE becoming a piece of crap now? I regret buying BE v11. I should've got different backup product.
  • J_Peralta's avatar
    J_Peralta
    Level 4
    17 years ago
    This might be off target but it could be SCSI card problems.  The only other thing I've noticed that gives me errors along with this one, is errors on my SCSI card.  The SCSI card looses communication  sometimes and I think that it can crash BEengine.exe or indirectly BkupExec.exe since it looses touch with the autoloader and/or tape drive while in use.  I really can't find any info on that being a correlation but It seems logical. 

    None of the other threads I've seen really touch on this problem too much......Symantec Employees??

    I'll keep this thread posted with anything new I find out.

    J
  • Morph27's avatar
    Morph27
    Level 4
    17 years ago
    Thanks J. I've done (SCSI settings) troubleshooting in the past. I don't think this particular problem is related to my SCSI controller settings (there's no SCSI related entries in the event log).
     
    None of the other threads I've seen really touch on this problem too much......Symantec Employees??
     
    That's correct. I found a few similar posts but there's no resolution. My next move is to upgrade my build to 7170. Somehow I doubt that'll fix the problem but worth trying.
  • Morph27's avatar
    Morph27
    Level 4
    17 years ago
    Update
     
    At the end of last week I ended up patching build 6235 with SP1 followed by SP2. I've had 5 successful backups since then.