Backup Exec server service crashes 4 AM after installing Backup Exec 2012 Service Pack 1

Problem

 The Backup Exec Server service (BESERVER.EXE) crashes at 4AM in the morning after installing Backup Exec 2012 Service Pack 1.

Error Message

 Following Events are logged in application log:

 

Log Name:      Application
Source:        .NET Runtime
Event ID:      1026
Level:         Error

Description:
Application: beserver.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: exception code c0000005, exception address 00000000721F81F3

 

Log Name:      Application
Source:        Application Error
Event ID:      1000
Level:         Error

Description:
Faulting application name: beserver.exe, version: 14.0.1798.105, time stamp: 0x4fa3de95
Faulting module name: iplops.dll, version: 14.0.1798.105, time stamp: 0x4fb29ca8
 

 

 

Solution

 

This issue is resolved in Backup Exec 2012 Service Pack 1a. (TECH186717)

 

Workaround:

 

Warning: Incorrect use of the Windows registry editor may prevent the operating system from functioning properly. Great care should be taken when making changes to a Windows registry. Registry modifications should only be carried-out by persons experienced in the use of the registry editor application. It is recommended that a complete backup of the registry and workstation be made prior to making any registry changes.

 

1. Set the following registry dword to a time when there are no backups running:

HKLM\SOFTWARE\Symantec\Backup Exec For Windows\Backup Exec\Server\CheckEvalExpireHour

Example: If the above dword is set to 15 decimal then the EvalExpire check will run at 3PM and the Backup Exec Server service will crash at 3PM. 

 

2. Set Backup Exec Server service to Restart Automatically after a failure from service properties - Recovery tab. 

 

 

 

 

 


Applies To

Backup Exec 2012

 

Terms of use for this information are found in Legal Notices.

Search

Survey

Did this article answer your question or resolve your issue?

No
Yes

Did this article save you the trouble of contacting technical support?

No
Yes

How can we make this article more helpful?

Email Address (Optional)