Backup exec will not start with Microsoft Visual C++ Runtime Library Runtime Error!

Written by on Tuesday, May 27, 2008 21:29 - 0 Comments

We had this problem with a Dell Poweredge 2900 series server and Tape drive was an LTO3 system.  at first it looks like the exact error and fix as per the Symantec support website document ID: 287554, but upon further troubleshooting (and hair pulling) we discovered that it was a two step proccess to resolve this issue.

ERROR Message you may be troubleshooting:

Microsoft Visual C++ Runtime Library Runtime Error! Program: Program FilesSymantecBackup Execbeserver.exe
This application has requested the Runtime to terminate it in an unusual way. Please contact the application’s support team for more information.


Could not load file or assembly ‘System.EnterpriseServices, Version=, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a’ or one of its dependencies. Systemet could not find the file.

You must first do the Symantec fix:

If any components of the functions/features listed above are missing or corrupted, the Backup Exec Server service may fail to start with a C++ Runtime Error.  To diagnose why this issue is occurring, run the service in console mode per the following:
1. Launch a command prompt on the media server
a. Go to Start
b. Select Run
c. Type in CMD and press Enter
2. Change the path to the Program FilesSymantecBackup Exec directory on the disk partition that Backup Exec is installed on (default is the C: partition).  Type in the following and press Enter:
BEServer.exe  -console >> C:BEServer.txt
3. Locate the BEServer.txt file after the runtime error is displayed.  Review the document or submit it to Symantec Technical Support for assistance.

One possible reason that the service may not start after an upgrade or re-install of Backup Exec is covered in the example listed below:
The Backup Exec Device and Media Service starts successfully but the following dialog boxes appear when attempting to start the Backup Exec Server service (Figures 1 & 2):
Figure 1
 c++ error
Figure 2
Symantec SCM error 

The Windows System Event Logs shows:
Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID:       7022
Date:        14/02/2007
Time:        10:10:44
User:        N/A
Computer:     VM2003BE11D
Description:  The Backup Exec Server service hung on starting.

The debug log from the BEServer.exe -console process will show the following at the end of the log:

[5272] 02/14/07 02:13:13 14 Reports: Using default language = ENU
[5272] 02/14/07 02:13:13 14 Reports: Initialize for language = 1
[5272] 02/14/07 02:13:13 14 Reports: Setting remote server locations.
[5272] 02/14/07 02:13:13 14 Reports: Loading any new reports.
[5272] 02/14/07 02:13:14 14 Reports: Report Engine started.
[5272] 02/14/07 02:13:14 14 Reports: Initializing CRF.

***If the logging stops at the “Initializing CRF” line above, then confirm that the following registry key/value exists:

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. Go to Start, Run, type REGEDT32 and press Enter.

2. Select the HKey_Local_Machine on Local Machine window.  Browse to the SoftwareSymantecCRF key and confirm that it exists.  When you click on this key, a Port value should show in the right window with a DWord value of 1d97 in hex or 7575 in decimal. (Figure 3)

Registry Edit

Figure 3
***If the CRF key or Port value do not exist, create them and attempt to start the Backup Exec Server service again.


If the BEServer -console debug does not stop at “Initializing CRF” and instead continues with the next line “Reports: Initialization Complete”, then look through the other entries in the log for errors.  Review the TechNotes in the Related Documents Section below or contact Symantec Technical Support for further assistance.


***After you are done that step you must then do this patch:

you probably have a different version of the System.EnterpriseServices assembly in the global cache. Or you don’t have it at all. You need to add the version to the GAC.
In order to do that just drag the file at
to the “<windows_directory>assembly” folder.

 Remember to check the properties of the file to be sure it has the appropriate version number!!!

(Images from Symantec and are copywrite symantec) ')}

Article written by

Comments are closed.

Ad Sponsor


2003 server - Sep 30, 2008 22:34 - 0 Comments

instant messaging srv records

More In Computers & PC

Microsoft Outlook - Mar 22, 2009 11:22 - 0 Comments

Outlook: Duplicates in Mailbox

More In Computers & PC

Microsoft Desktop, Web browsers and Internet, Windows 2000, Windows 7, Windows 98, Windows Firewall and networking, Windows Vista, Windows XP - Feb 8, 2010 18:09 - 0 Comments

Disable Proxy settings in IE

More In Computers & PC