Suggest you to install the latest device drivers from the following link:

http://support.veritas.com/docs/275676

Reconfigure the device in Bsckup Exec:
1. From Backup Exec | Devices Right Click the device/library | Properties | Uncheck “Enable device for backup Exec” Right click and delete the device.
2. Power cycle the device and the server
3. From rogram FilesVERITASBackup ExecNT
4. Run tapeinst.exe
5. Install Veritas tape drivers 275676
6. Check the results.

Article written by MyComputerAid.com

Post from: MyComputerAid.com Computer support

Backup Exec Physical Volume Library Drive or Robot paused, offline, or disabled

Over the years we have had the benefit to work with many antivirus vendors and their products, for those who are looking for a comparison of our top picks for business class anti-virus we have written up an overview from our own experiences.



Symantec
While Symantec Antivirus Corporate Edition came out ahead in overall performance, it was somewhat lacking in ease of use and installation qualities. There is a lot of work involved when installing product, and the administrator may find the job especially tedious on a large network.

Functionally, Symantec’s ACE is assuredly top of the line. It provides for detecting a possible virus and quarantine of that file for analysis by the administrator or Symantec. This Digital Immune System was developed in conjunction with IBM, and really sets this product apart.

McAfee
Perhaps the best known of Antivirus Corporate Editions, McAfee offers a high degree of reliability at the cost of simplicity in use. In addition to virus protection, this product offers limited but effective spyware and adware protection as well, plus SiteAdvisors Web safety ratings to help you identify potential trouble locations.

Installation is not overly difficult, but does require multiple stages to complete properly. And while this may be a deterrent for administrators, the scanner makes up for it by including a few network tools, such as McAfee QuickClean which can be used to clean up the cookie collections, clear temp folders, and other useful tasks.

Sophos
For those who demand a product that’s fully functional and easy to implement, this is the corporate antivirus scanner of choice. As a stand alone scanner, Sophos beats out both McAfee and Symantec in usability and speed. But at the administration level, it starts to go bad.

Excluding files that must be scanned is a manual project, and it may even require the editing of .INI files to accomplish some exclusions. Overall, there is very little automation in this product. While it may be powerful and fast, the initial set up is a long and bulky process.

Trend Micro
Trend Micro OfficeScan Corporate Edition is a bird of a different color. It starts off being less expensive than the high-end models, such as Mcafee and Symantec, and gets better from there. The scanner/disinfector is web-based, and can be accessed from the server or any workstation. It is as reliable as Symantec, and about as easy to implement as an administrator could want.

While no antivirus software is fun to use, Trend Micro has made it less of a burden. Administration as well as installation can be accomplished without visiting every workstation, and its results are comparable to other big-name products.

Article written by MyComputerAid.com

Post from: MyComputerAid.com Computer support

Comparing the top business anti-virus software

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.
OR

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

You must first do the Symantec fix: http://seer.entsupport.symantec.com/docs/287554.htm

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:
Symptoms:
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
 
Figure 2
 

***********************************************************************************************************************************************************
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)

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 2.0.0.0 version to the GAC.
In order to do that just drag the file at
“<windows_directory>Microsoft.NETFrameworkv2.0<your_subversion>System.EnterpriseServices.dll”
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 MyComputerAid.com

Post from: MyComputerAid.com Computer support

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