cancel
Showing results for 
Search instead for 
Did you mean: 

BackupExec 2010 engine crashes

Recently I have taken over a rather lousy administered BackupExec environment. Last nignt backupexec engine crashed with the error as follows:

Faulting application name: bengine.exe, version: 13.0.2896.109, time stamp: 0x4b83ebf7

Faulting module name: MSVCR80.dll, version: 8.0.50727.4927, time stamp: 0x4a27427d

Exception code: 0xc0000005

Fault offset: 0x000000000001e371

Faulting process id: 0xf7c

Faulting application start time: 0x01cc768b38e191b6

Faulting application path: C:\Program Files\Symantec\Backup Exec\bengine.exe

Faulting module path: C:\Windows\WinSxS\amd64_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.4927_none_88dce9872fb18caf\MSVCR80.dll

Report Id: 7761ab9f-f06f-11e0-8dcf-001b78315ad8

 

I know that BE engone faults might be caused by various reasons, but I couldn't find th technote that matches my case.

Could someone point me out to a proper patch or solution? Thank you very much in advance.

 

1 Solution

Accepted Solutions
Accepted Solution!

Ok guys, I found the solution

Ok guys, I found the solution on my own. It was verify function that I had to turn off.

View solution in original post

4 Replies

Hi Anton,   First thing to do

Hi Anton,

 

First thing to do would be to upgrade to BE 2010 R3. You can use your current licenses. It fixes a number of issues with previous versions of BE. Once done, run LiveUpdate and install SP1 or download and install manually.

You can then push-install these updates out to the remote servers you have.

Download BE 2010 R3 from the link below:

https://www4.symantec.com/Vrt/offer?a_id=93355

Just remember to grab a copy of your Data/Catalogs folders before running the upgrade just in case anything goes wrong.

Once done, run a backup and check to see if it gives you the same hassle.

 

Thanks!

Are you backing up DSFR data?

Are you backing up DSFR data?  Could this Known Issue apply to you?

https://www-secure.symantec.com/connect/issues/backup-dfsr-data-having-long-path-fails-causing-berem...

Accepted Solution!

Ok guys, I found the solution

Ok guys, I found the solution on my own. It was verify function that I had to turn off.

View solution in original post

RE: Ok guys, I found the solution

Turning off Verify really isn't a "solution", you know

More of a Band-Aid