cancel
Showing results for 
Search instead for 
Did you mean: 

Unexpected Error. Could not start the back up... Error 1068: The dependency service or group failed to start.

Pejogasa
Level 3
Hi, i'm going to resume the problem.

Since october, the program was running ok, but sudently the situation changed. I did some modification in dns and ip system due to some new requirements. Since that moment:
 

Im unable to log into Backup exec. My password doesnt' seem to work even after i rest it. There are several services that are not started. When I attempt to start them I receive this error mesage

"Could not start the Backup Exec Job Engine service on Local Computer.  Error 1068: The dependency service or group failed to start."
 
I hope to find some solution cos i've tried everything that i've found searching in the web, and nothing fix it. 

Thanks and regards.
 
 
14 REPLIES 14

Colin_Weaver
Moderator
Moderator
Employee Accredited Certified
If the BE Device and Media Service is starting and no other BE Service - then it is likely that the BE Server Service is the cause of your issue as the Job Engine depends on it.

Suggest you open a command prompt, change to the Backup Exec program files folder and then enter
beserver -console
to see if any obvious error occurs.

Pejogasa
Level 3
I already did it and the result was this:

C:\Program Files\Symantec\Backup Exec>beserver.exe
[0552] 12/15/09 15:28:33 -1 Starting beserver system service applicat
[0552] 12/15/09 15:28:48 -1 BEServer failed to connect to service con
r:1063
[0552] 12/15/09 15:28:48 -1 Cblmanger, shutdown Immenient: started.
[0552] 12/15/09 15:28:48 -1 Cblmanger, shutdown Immenient: complete.
[0552] 12/15/09 15:28:48 -1 Cblmanger, check shutdown Ready: started.
[0552] 12/15/09 15:28:48 -1 Cblmanger, check shutdown ready: complete
[0552] 12/15/09 15:28:48 -1 Uninitializing ACE...
[0552] 12/15/09 15:28:48 -1 ERROR uninitializing ACE: -1.
[0552] 12/15/09 15:28:48 -1 BEServer shutdown completed.
[0552] 12/15/09 15:28:48 -1 Cblmanger, shutdown Immenient: started.
[0552] 12/15/09 15:28:48 -1 Cblmanger, shutdown Immenient: complete.
[0552] 12/15/09 15:28:48 -1 Cblmanger, check shutdown Ready: started.
[0552] 12/15/09 15:28:48 -1 Cblmanger, check shutdown ready: complete

Any suggestions? I'm trying to fix it but i don't now the way.

Thanks a lot, regards.

Hemant_Jain
Level 6
Employee Accredited Certified
Did you rename the server, before this problem?

Thanks

Colin_Weaver
Moderator
Moderator
Employee Accredited Certified

Also looks liek you just ran beserver.exe

you do not run it with teh command -console on the end making the complete command

beserver -console

 

Pejogasa
Level 3
I didn't rename de server, but yes i ran beserver.exe but now i did it properly.

C:\Program Files\Symantec\Backup Exec>beserver -console
[0376] 12/15/09 17:37:38 -1 Starting beserver console application
[2064] 12/15/09 17:37:38 -1 Starting Service: BackupExecRPCService
[2064] 12/15/09 17:37:38 -1 Entered RpcXfaceServiceMain.
[2064] 12/15/09 17:37:38 -1 Sending start status to scm. (hint 300000)..
[2064] 12/15/09 17:37:38 -1 Initializing ACE...
[2064] 12/15/09 17:37:38 -1 Cblmanger, shutdown Immenient: started.
[2064] 12/15/09 17:37:38 -1 Cblmanger, shutdown Immenient: complete.
[2064] 12/15/09 17:37:38 -1 Cblmanger, check shutdown Ready: started.
[2064] 12/15/09 17:37:38 -1 Cblmanger, check shutdown ready: complete.
[2064] 12/15/09 17:37:39 -1 Initializing work queue...
[2064] 12/15/09 17:37:39 -1 Read from Registry: DBTimeoutInSec=30 ServerInterna
=0x0
Error.  HR:0x80004005.
[2064] 12/15/09 17:37:56 -1 Persistent Store initialization failed:-1
[2064] 12/15/09 17:37:56 -1 Server Connection String = Application Name=BEWS Se
ver;Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security Info=False;In
tial Catalog=BEDB;Data Source=server01\BkupExec;Locale Identifier=1033;
[2064] 12/15/09 17:37:56 -1 Initializing Persistent Store (, , Backup Exec Serv
r, 30 seconds)...
[2064] 12/15/09 17:37:56 -1 Attemp to GetMyPartition ComputerName=SERVER01 Part
tionID=0 PartitionGUID=8972ca33-5610-4fff-814b-469a8bde0939
[2064] 12/15/09 17:37:56 -1 InitializePartition() Data partition ID from regist
y=0
[2064] 12/15/09 17:37:56 -1 InitializePartition() DB_Exception caught! native=0
10d9
[2064] 12/15/09 17:37:56 -1 InitializePartition() returning 0x10d9
[2064] 12/15/09 17:37:56 -1 Unable to obtain partition data, error 0x10d9
[2064] 12/15/09 17:37:56 -1 Business object initialization failed: 4313
[2064] 12/15/09 17:37:56 -1 RpcXfaceServiceMain: InitializeBOs() failed, BO:-1,
nRet:4313

Any suggestion? It's really weird this problem.

Thanks for your help.

Colin_Weaver
Moderator
Moderator
Employee Accredited Certified
Well the 0x10d9 error can be seen when the SQL database has somehow been placed into single user mode - so it might be that
http://support.veritas.com/docs/320569

Pejogasa
Level 3
Well thanks, but "Set a Database to Single-user Mode"  doesn't  work because i can't find  SQL Server Management Studio and the single mode user. I've changed the IP in SQL Server Configuration Manager, because i didn't change it before for the new one, but it's not working yet.

Any suggestion or explanation how to find it. Thanks, again. 

CraigV
Moderator
Moderator
Partner    VIP    Accredited
Hi there,

Have you looked at going into Services.msc and changing the password there manually, before starting up the services again?

There are a couple of other options to look into like running a DB repair using Beutility.exe, or at an extreme, dumping the database and loading from base (which means a blank DB...so be careful there!)

Laters!

Pejogasa
Level 3
Hi Craig first of all thanks  for your help, well i've tried to start in services.msc "SQL Server (BKUPEXEC)" and the error is " Could not start the SQL Server (BKUPEXEC) service on Local Computer Error 1069: The service did not start due to a logon failure", so i guess that i can reset a new password for SQL, but i have a doubt, i have to reset it for all the components ( for example back up agent browser....) I have to reset it in servrcies.msc isn't  it?.

Thanks again.

CraigV
Moderator
Moderator
Partner    VIP    Accredited
Hi there,

You can look at the following:

1. Detaching/reattatching the SQL DB
http://seer.entsupport.symantec.com/docs/274102.htm

2. Checking to see if you have proper connectivity to your SQL DB
http://seer.entsupport.symantec.com/docs/256661.htm

3. Running Beutility.exe to repair the DB. Once done, try a services restart.

The SQL Server (BKUPEXEC) service always starts up with Local System account, so there is no need to change that.

Try #3 first, as its the easiest.

Pejogasa
Level 3
With solution 1:

[SQL Native Client]SQL Network Interfaces: Error Locating Server/Instance
Specified [xFFFFFFFF].
[SQL Native Client]Login timeout expired
[SQL Native Client]An error has occurred while establishing a connection to
the server. When connecting to SQL Server 2005, this failure may be caused by
the fact that under the default settings SQL Server does not allow remote
connections.

With solution 2:

[DBNET LIB] connection open (Connect ())).]SQL Server not exit or access denied

Login Failed Catalog information can not be retrieved

With Solution 3 ( Beutility.exe)

When i execute this program:

Known Computers:

  1. Groups of server of support = no one
  2. All servers od support = SERVER01 my server with the simbol ? in the logo.
  3. All computer of remote agent = no one.
UFFFFF, any suggestion about, thanks again.



Colin_Weaver
Moderator
Moderator
Employee Accredited Certified
Error status 0x80004005 is probably an Access Denied (try typing NET HELPMSG 5 in a command prompt. So it looks like the BESERVR process can no longer access the BEDB.

BTW You can Download the Express version of SQL Studio fManager from Microsoft which might help you check the security and modes of the SQL instance - it might be in single user mode as previously mentioned - or somethoing else might have changed on the security side.

CraigV
Moderator
Moderator
Partner    VIP    Accredited
When you right-clicked your server in BEutility.exe, did it give you the option of repairing the DB?
If you don't come right here, you're looking at dumping that DB and reloading it from base...

Pejogasa
Level 3
I've tried with BEutility.exe, but when any solutions i tried always there are errors, so i'll install SQL Studio Manager. It seems to be that SQL is not connected with the program because when i tried to launch the program always appear: It can connect with support service..... so i don't know now what i have to do now.

Thanks.