beserver hangs after install of be 10d on sbs2003 with sql server 2005 and rd1000 all patched

Updated: 27 May 2010 | 7 comments

Mark Larson

0 0 Votes

I know just enough about this stuff to get by -- or so I thought. I'm moving from sbs2000 Premium to sbs2003 Premium on a new server. Also a new RD1000. Running SQL Server 2005. The OS is fully patched. I've loaded 10d and downloaded and installed SP4. Beserver just hangs when the system starts, saying "Starting". The event ID in the system log in Event Viewer is 7022 from Service CONtol manager -- "The backup exec server service hung on starting. Backup exec starts but many things don't work. If I go to Help / About BE..., it just closes.

Now when I installed, it wouldn't let me install to sql. It made me use MSDE. Said it wasn't a valid instance. Don't know if that makes a difference here, but don't know how to get around it.

I can kill the process in Task Manager. If I try to restart, I get a 1053 error. "THE service did not respond to the start or control request in a timely manner." The App log shows event id 1000 Application Error, bkupexec.exe, version 10.1.5629.0, faulting module bkupexec.exe, version (same) fault address is...."

I've tried uninstalling and reinstalling BE. I've tried uninstalling, rebooting, and reinstalling ASP.NET 2_x. I set it up using the Administrator login, like I did on the old server. I trired changing the login rights to another user with Administrator rights. I've searched symanteca and googled for9 hours. The most promising links on Symantec were to pages that were no longer available.

I've always thought BE was way too complicated for backing up a 10 person server, even with SQL and Exhcnage, and maybe it's time to find something that works. I'm open to suggestions on that, as well.

IF I was unclear, it was running OK on the old server.

discussion Filed Under:

Backup and Archiving, Backup Exec - 10.x and Earlier, Backup Exec, Installing

Comments RSS Feed

Comments

Nov

2009

0 Votes 0

BEsymc

Symantec Employee

Accredited

Certified

Do you have Microsoft Outlook

Do you have Microsoft Outlook installed on this machine? Make sure it is your default client. Also, do you observe anything in the application or system event log, when the service hangs on startup?

Please mark it a solution, if this is useful.
Thanks

Nov

2009

0 Votes 0

Mark Larson

Thanks. I'm grateful for any

Thanks. I'm grateful for any help.

Yes, I installed MS Outlook and made it the default client. (I'd seen that as a possibility in my searches and did it; I should have mentioned it.) And I did mention that the System log showed a 7022 error on boot. I get the error that "At least one service failed to start..." or words to that effect. (I'm not at the server now, but will be in an hour.)

"The event ID in the system log in Event Viewer is 7022 from Service CONtol manager -- 'The backup exec server service hung on starting.'"

Also that the Application log shows a 1000 error if I try to start the service manually.

Nov

2009

0 Votes 0

BEsymc

Symantec Employee

Accredited

Certified

Could you please run

Could you please run sgmon.exe at the time of starting server service and post the excerpts of log here?

Thanks

Nov

2009

0 Votes 0

Mark Larson

Enter subject (optional)

OK. I ended the beserver.exe service with Task Manager, started sgmon and restarted the service. Here's what the log says:

beserver: [0280] 11/24/09 19:41:24 -1 Starting beserver system service application
beserver: [2360] 11/24/09 19:41:24 -1 Entered RpcXfaceServiceMain.
beserver: [2360] 11/24/09 19:41:24 -1 Sending start status to scm. (hint 300000)..
beserver: [2360] 11/24/09 19:41:24 -1 Initializing ACE...
beserver: [2360] 11/24/09 19:41:24 -1 Cblmanger, shutdown Immenient: started.
beserver: [2360] 11/24/09 19:41:24 -1 Cblmanger, shutdown Immenient: complete.
beserver: [2360] 11/24/09 19:41:24 -1 Cblmanger, check shutdown Ready: started.
beserver: [2360] 11/24/09 19:41:24 -1 Cblmanger, check shutdown ready: complete.
beserver: [2360] 11/24/09 19:41:25 -1 Initializing work queue...
beserver: [2360] 11/24/09 19:41:25 -1 Initializing Persistent Store (FHSERVER\BkupExec, BEDB, Backup Exec Server, 30 seconds)...
beserver: [2360] 11/24/09 19:41:25 -1 Attemp to GetMyPartition ComputerName=FHSERVER PartitionID=0 PartitionGUID=a9986191-51d0-415b-98e7-fad3c8a9eaea
beserver: [2360] 11/24/09 19:41:25 -1 InitializePartition() Data partition ID from registry=0
beserver: [2360] 11/24/09 19:41:25 -1 GetMyPartition() Data partition to use for 'FHSERVER' is 0
beserver: [2360] 11/24/09 19:41:25 -1 InitializePartition() returning 0x0
beserver: [2360] 11/24/09 19:41:25 -1 Successfully GetMyPartition ComputerName=FHSERVER PartitionID=0 PartitionGUID=a9986191-51d0-415b-98e7-fad3c8a9eaea
beserver: [2360] 11/24/09 19:41:25 -1 InitializePartition() ok, partitionID=0, oldComputerName=
beserver: [2360] 11/24/09 19:41:25 -1 Creating Business Objects...
beserver: [2360] 11/24/09 19:41:25 00 VSN BO Initialization succeeded.
beserver: [2360] 11/24/09 19:41:25 -1 FillServerInfo: cw.Open() failed.
beserver: [2360] 11/24/09 19:41:25 -1 ServerName:FHSERVER, ActiveNodeName:,
InstanceName:BkupExec, DatabaseName:BEDB.
beserver: [2360] 11/24/09 19:41:25 01 Server Configuration: BEServer schema version checks OK.
beserver: [2360] 11/24/09 19:41:25 01 Server Configuration: Initialization Complete.
beserver: [2360] 11/24/09 19:41:25 02 Ownership: Initialization Complete.
beserver: [2360] 11/24/09 19:41:25 03 JobManBO: starting initialization...
beserver: [2360] 11/24/09 19:41:25 03 JobManBO: initialization complete...
beserver: [2360] 11/24/09 19:41:25 04 CAuditLogBO: Initialization completed.
beserver: [2360] 11/24/09 19:41:25 05 LoginAccount: Initialization Complete. BO=5.
beserver: [2360] 11/24/09 19:41:25 06 Resource: Initialization Complete.
beserver: [2360] 11/24/09 19:41:25 07 ServersBO: Initialization Complete.
beserver: [2360] 11/24/09 19:41:25 08 CMediaServerPoolBO: Initialization completed.
beserver: [2360] 11/24/09 19:41:25 09 ScriptMgrBO: Initialization Complete. BO=9.
beserver: [2360] 11/24/09 19:41:25 10 MessageQueue: Initialization Started.
beserver: [2360] 11/24/09 19:41:25 10 MessageQueue: Not licensed for DDM.
beserver: [2360] 11/24/09 19:41:25 10 MessageQueue: Initialization Complete.
beserver: [2360] 11/24/09 19:41:25 11 Djm: pMMSFeature is null, mmsUsable set to FALSE.
beserver: [2360] 11/24/09 19:41:25 11 Djm: pCASOFeature is null, casoUsable set to FALSE.
beserver: [2360] 11/24/09 19:41:25 11 Djm: mmsUsable is FALSE, so setting DjmEnabled to FALSE.
beserver: [2360] 11/24/09 19:41:25 11 DjmBO=11. : Initialization Complete.
CASO:0, APPO:0, DjmEnabled:0, Mgr:0, Clt:0, CasoServer:. nRetval=0x0.
beserver: [2360] 11/24/09 19:41:25 12 AdammAdminBO: Initialization Complete.
beserver: [2360] 11/24/09 19:41:25 12 AdammAdminBO::Execute() - hr = 0x80070005
beserver: [2360] 11/24/09 19:41:25 13 AdammUtilBO: Initialization Complete.
beserver: [2360] 11/24/09 19:41:25 14 Reports: Using default language = ENU
beserver: [2360] 11/24/09 19:41:25 14 Reports: Initialize for language = 1
beserver: [2360] 11/24/09 19:41:25 14 Reports: Setting remote server locations.
beserver: [2360] 11/24/09 19:41:25 14 Reports: Loading any new reports.
beserver: [2360] 11/24/09 19:41:25 14 Reports: Report Engine started.
beserver: [2360] 11/24/09 19:41:25 14 Reports: Initialization Complete.
w3wp : 2009-11-25 00:43:36.091 UTC Warning w3wp.7 DBConnection.OnReceivingInfoMessage The join order has been enforced because a local join hint is used.

Nov

2009

0 Votes 0

BEsymc

Symantec Employee

Accredited

Certified

This log is not very helpful.

This log is not very helpful. I might have to advise you to contact Tech support for further investigation. Another point of conflict i can see is coexisting instances of SQL 2005 and MSDE. Backup Exec 10d cannot use SQL 2005 as a database repository, hence you had to go for MSDE. That can be one of the possible reasons for the issue. If there is a possibility of trying any other SQL 2000 instance you might have in your environment, we can try that. Else, you may want to try a different server. Also, as a second thought, i would assume this is not a CAS or SAN setup.

Thanks

Nov

2009

0 Votes 0

Mark Larson

Can SQL server 2000 and 2005

Can SQL server 2000 and 2005 both reside on the same server? (Yeah, I'm pretty ignorant, but I'm trainable.) I installed SBS server 2005 because I was just following install directions, not really because I needed 2005 vs 2000. Everything we have is running fine on 2000. Would it be wise (and can I easily) just uninstall 2005 try again with sql 2000? (I don't really know how to go about this, but i can learn if I know it's possible and a good idea.)

Nov

2009

0 Votes 0

BEsymc

Symantec Employee

Accredited

Certified

Yes, it is definitely

Yes, it is definitely possible, but sequence does matter at times. Its advisable to install SQL 2005 after SQL 2000, for reasons like backward compatibility. If SQL 2000 is installed after SQL 2005, it might cause issues with functionality. In this case, backup Exec just cannot use SQL 2005, so SQL 2000 or MSDE is the only option.

Hope that helps.
Thanks

beserver hangs after install of be 10d on sbs2003 with sql server 2005 and rd1000 all patched

Comments

Do you have Microsoft Outlook

Thanks. I'm grateful for any

Could you please run

Enter subject (optional)

This log is not very helpful.

Can SQL server 2000 and 2005

Yes, it is definitely

Would you like to reply?

Links

Technical Support

Symantec.com

Store

Community Stats