BEServer Service won't start after SQL2005 install
For the last year we've had 10d SP3 running under Win2003 R2 without problems. The server also ran a business app that used MSDE 2000. This week that app was upgraded, which included replacing it's MSDE with SQL 2005 (and installing Visual Studio 2005). Since the app vendor did these installs BE hasn't run, because BEServer won't start.
The event log has nothing to indicate what the problem is -- just that the Backup Exec Server Service terminated unexpectedly.
I uninstalled and reinstalled (using the existing MSDE instance) to ensure that BE had everything it needed. When I used BEUtility to recover the backed up BEDB the recovery completed with errors; the dbrecover log indicated that the recovery succeeded, but BEService wouldn't start, which was presumably the error.
I then used BEUtility to recover the base DB. At that point BE would run, but when I ran an catalog or even an inventory job, BEService again died.
I ran SGMon to log what happens when I try to start BEServer. I don't see anything obvious indicating a problem, and the log ends with:
beserver: [3712] 05/16/07 17:17:57 12 AdammAdminBO::Query() - hr = 0x0beserver: [5116] 05/16/07 17:17:57 17 CJobManager::Deinitialize( ): killing dispatcher...beserver: [5116] 05/16/07 17:17:57 17 CJobManager::Deinitialize( ): flushing cache...beserver: [5116] 05/16/07 17:17:57 17 CJobManager::Deinitialize( ): empty cache...beserver: [5116] 05/16/07 17:17:57 17 CJobManager::Deinitialize( ): remove alert monitor...beserver: [5116] 05/16/07 17:17:57 17 CJobManager::Deinitialize( ): complete!beserver: [5116] 05/16/07 17:17:57 17 CJObManager::Initialize( ) - initializing cache...beserver: [5116] 05/16/07 17:17:57 17 CJobManager::Initialize( ) - loading schedules...beserver: [5116] 05/16/07 17:17:57 17 CJobManager::Initialize( ) - 9 schedules loadedbeserver: [5116] 05/16/07 17:17:57 17 Job Dispatcher: GetServerIsRunningOnCluster()==FALSEbeserver: [5116] 05/16/07 17:17:57 17 Job Dispatcher: UseClusterRestart=0beserver: [5116] 05/16/07 17:17:57 17 CJobManager::LoadAllJobData( ): loading task definitions...beserver: [5116] 05/16/07 17:17:57 17 CJobManager::LoadAllJobData( ): loading solutions...beserver: [5116] 05/16/07 17:17:57 17 CJobManager::LoadAllJobData( ): loading work items...beserver: [5116] 05/16/07 17:17:57 17 CJobManager::LoadAllJobData( ): loading policies...beserver: [5116] 05/16/07 17:17:57 17 CJobManager::LoadAllJobData( ): making solution associations...beserver: [5116] 05/16/07 17:17:57 17 CJobManager::LoadAllJobData( ): generating workitem linkages...beserver: [5116] 05/16/07 17:17:57 17 CJobManager::LoadAllJobData( ): recovering tasks...beserver: [5116] 05/16/07 17:17:57 17 Job Dispatcher: RecoverActiveTask() job name= Daily Backup, JobState=16beserver: [5116] 05/16/07 17:17:57 17 Job Dispatcher: Not restarting jobbeserver: [5116] 05/16/07 17:17:57 17 Job Dispatcher: Marking task for possible reschedule.
I know 10d can't use a SQL 2005 instance for BEDB, but there should be no problem running BE's MSDE on the same server as SQL2005.
What can I do to get this running?
Thanks, in advance!
Comments
A Symantec tech worked through this issue, and eventually got the BEServer service to work by a Repair+Rebuild+Dump+Compact+Age+Check of the DB. I thought this had solved the problem.
BUT the BEServer service won't stay running. I started a tape inventory, and the BEServer service terminated shortly after.
I'm on hold again to Symantec to re-open this case, but any suggestions would be appreciated...
Would you like to reply?
Login or Register to post your comment.