cancel
Showing results for 
Search instead for 
Did you mean: 

Removed DAT drive and SCSI card, BEServer not starting

Timothy_Trace
Level 3
Greetings,
 
I removed and shipped away the DAT drive and SCSI card in my BE 11d server.  Then, I noticed that BEServer was not running.  When I try to start it, it crashes.
 
I've run a repair from the original media, and I've rebooted the server several times.
 
My installed BEServer version number is 11.0.7170.27 .
 
This is what happens when I try to start BEServer from the Services management console.  The event error shown is the only one that appears in the system or application logs.
 
 
If I use the following command, the resultant textfile is blank.
Code:
beserver.exe -console>>c:\beserver.txt
 
This is the console output when I try to start BEServer from the command line.
Code:
[c:\program files\symantec\backup exec]beserver[3816] 12/18/07 11:25:52 -1 Starting beserver system service application[3816] 12/18/07 11:25:52 -1 BEServer failed to connect to service control manager:1063[3816] 12/18/07 11:25:52 -1 Cblmanger, shutdown Immenient: started.[3816] 12/18/07 11:25:52 -1 Cblmanger, shutdown Immenient: complete.[3816] 12/18/07 11:25:52 -1 Cblmanger, check shutdown Ready: started.[3816] 12/18/07 11:25:52 -1 Cblmanger, check shutdown ready: complete.[1104] 12/18/07 11:25:53 -1 App stopped: SCM pending thread exiting...[3816] 12/18/07 11:25:53 -1 Uninitializing ACE...[3816] 12/18/07 11:25:53 -1 ERROR uninitializing ACE: -1.[3816] 12/18/07 11:25:53 -1 BEServer shutdown completed.[3816] 12/18/07 11:25:53 -1 Cblmanger, shutdown Immenient: started.[3816] 12/18/07 11:25:53 -1 Cblmanger, shutdown Immenient: complete.[3816] 12/18/07 11:25:53 -1 Cblmanger, check shutdown Ready: started.[3816] 12/18/07 11:25:53 -1 Cblmanger, check shutdown ready: complete.[c:\program files\symantec\backup exec]
 
 
 
Please, what do I need to do to get my backups working again?
 
Best regards,
 
Tim ==


Message Edited by Timothy Trace on 12-18-2007 09:31 AM
2 REPLIES 2

Ben_L_
Level 6
Employee
Tim,

Try these steps.

1. Run a repair of .NET 2.0 and reboot the server.

if that does not fix the issue.

2. Uninstall and re-install .NET 2.0 and reboot the server.


This issue has nothing to do with the SCSI Card and drive getting removed, it just happened to happen at the same time.

Timothy_Trace
Level 3
Thanks, Blipsey - this worked a treat.
 
How to repair an existing installation of the .NET Framework:
 
Would't repair.  Had to manually remove.  This tool is invaluable:
 
Removed .NET 2.0 and reinstalled with this download: