Backup Exec 11d Services won't start

[Brett_N]

First off, I know there are threads on this, yet I have tried the solutions in there, re-entering the credentials for the service. Running the BEutility to check and repair the database. Nothing has made any change.

Here is the story, raid array went into predictive failure. I repaired the array, array is now rebuilt OK. I had to stop the BUE services during this process as it was failing until I had killed the services. Then the array rebuild went through OK. I have since restarted the server after the array rebuild. This morning I go to start the services and they fail. Only the device and media service will run. So the credentials are good then.

I can access the utility, so let me know what logs or files you may need to help with this.

A big thanks in advance to the community out there.
 

[Colin_Weaver]

If device and media runs then it is probably the server service that is failing.

Try opening a Command console
Changing to the Backup Exec program files folder
and then running

beserver.exe -console

to see if it captures an error.

[Brett_N]

OK nice, here is the dump from that.
 

C:\Program Files\Symantec\Backup Exec>beserver.exe -console
[6964] 12/09/09 11:47:39 -1 Starting beserver console application
[8660] 12/09/09 11:47:39 -1 Starting Service: BackupExecRPCService
[8660] 12/09/09 11:47:39 -1 Entered RpcXfaceServiceMain.
[8660] 12/09/09 11:47:39 -1 Sending start status to scm. (hint 300000)..
[8660] 12/09/09 11:47:39 -1 Initializing ACE...
[8660] 12/09/09 11:47:39 -1 Cblmanger, shutdown Immenient: started.
[8660] 12/09/09 11:47:39 -1 Cblmanger, shutdown Immenient: complete.
[8660] 12/09/09 11:47:39 -1 Cblmanger, check shutdown Ready: started.
[8660] 12/09/09 11:47:39 -1 Cblmanger, check shutdown ready: complete.
[8660] 12/09/09 11:47:40 -1 Initializing work queue...
[8660] 12/09/09 11:47:40 -1 Read from Registry: DBTimeoutInSec=30 ServerInternal
=0x0
[8660] 12/09/09 11:47:40 -1 Server Connection String = Application Name=BEWS Ser
ver;Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security Info=False;Ini
tial Catalog=BEDB;Data Source=corrigan-sql1;Locale Identifier=1033;
[8660] 12/09/09 11:47:40 -1 Initializing Persistent Store (CORRIGAN-SQL1, BEDB,
Backup Exec Server, 30 seconds)...
[8660] 12/09/09 11:47:40 -1 Attemp to GetMyPartition ComputerName=CORRIGAN-SQL1
PartitionID=0 PartitionGUID=7c2a5461-7be5-4c84-8df1-8c8868bda895
[8660] 12/09/09 11:47:40 -1 InitializePartition() Data partition ID from registr
y=0
[8660] 12/09/09 11:47:40 -1 GetMyPartition() Data partition to use for 'CORRIGAN
-SQL1' is 0
[8660] 12/09/09 11:47:40 -1 InitializePartition() returning 0x0
[8660] 12/09/09 11:47:40 -1 Successfully GetMyPartition ComputerName=CORRIGAN-SQ
L1 PartitionID=0 PartitionGUID=7c2a5461-7be5-4c84-8df1-8c8868bda895
[8660] 12/09/09 11:47:40 -1 InitializePartition() ok, partitionID=0, oldComputer
Name=
[8660] 12/09/09 11:47:40 -1 Creating Business Objects...
[8660] 12/09/09 11:47:40 00 VSN BO Initialization succeeded.
[8660] 12/09/09 11:47:40 -1 Server Configuration: Getting network configuration.
..
[8660] 12/09/09 11:47:40 -1 UpdateDynamicInfo: cluster open unsuccessful.
[8660] 12/09/09 11:47:40 -1 ServerName:CORRIGAN-SQL1, ActiveNodeName:,
InstanceName:, DatabaseName:BEDB.
[8660] 12/09/09 11:47:40 01 Server Configuration: BEServer schema version checks
 OK.
[8660] 12/09/09 11:47:40 01 Server Configuration: Initialization Complete.
[8660] 12/09/09 11:47:40 02 Ownership: Initialization Complete.
[8660] 12/09/09 11:47:40 03 JobManBO: starting initialization...
[8660] 12/09/09 11:47:40 03 JobManBO: initialization complete...
[8660] 12/09/09 11:47:40 04 CAuditLogBO: Initialization completed.
[8660] 12/09/09 11:47:40 05 LoginAccount: Initialization Complete. BO=5.
[8660] 12/09/09 11:47:40 06 Resource: Initialization Complete.
[8660] 12/09/09 11:47:40 07 ServersBO: Initialization Complete.
[8660] 12/09/09 11:47:40 08 CMediaServerPoolBO: Initialization completed.
[8660] 12/09/09 11:47:40 09 ScriptMgrBO: Initialization Started. BO=9.
[8660] 12/09/09 11:47:40 -1 Operation: Verify default availability window.
[8660] 12/09/09 11:47:40 -1 Operation: success.
[8660] 12/09/09 11:47:40 09 ScriptMgrBO: Initialization Complete.
[8660] 12/09/09 11:47:40 10 MessageQueue: Initialization Started.
[8660] 12/09/09 11:47:40 10 MessageQueue: Shrinking DAT files.
[8660] 12/09/09 11:47:40 10 MessageQueue: Start Dump of Original File.
[8660] 12/09/09 11:47:40 -1
Entering CMQBO : DumpMsgQContents.

C:\Program Files\Symantec\Backup Exec>

[Colin_Weaver · Accepted solution]

Did it end up back at the command prompt withouth any keyboard intervention  - or did you interrupt with CTRl+C or similar?

As that seems to show that BESERVER started and connected to the Device and Media with no problems.

If it failed and dropped to the command prompt just after accessing Message Queue files - then it might be that your disk problems corrupted the message queue files in which case it might just be a case of deleting the corrupt files as they will (usually) be recreated.

Message queue files are usually located in
C:\Program Files\Symantec\Backup Exec\Data
and are named with the format

msgq*.dat

Obviously I would suggest you move them rather than delete them just as a general precaution.

[Brett_N]

Right on Colin.

Removing the .dat file from that directory, then starting the services. Now BUE runs like new. 

Thank you so much.