Can't get Backup Exec services to start. Urgent!
Running Backup Exec 10d on a Windows 2000 SP4 server.
3 of the 5 BE services are starting. 2 are not. Here is what I am seeing:
Processing services
Start services on server: RFPLTSTJMFNPP1
Starting Backup Exec Remote Agent for Windows Servers on RFPLTSTJMFNPP1.
The service Backup Exec Remote Agent for Windows Servers is already running on RFPLTSTJMFNPP1.
Starting Backup Exec Device & Media Service on RFPLTSTJMFNPP1.
The service Backup Exec Device & Media Service is already running on RFPLTSTJMFNPP1.
Starting Backup Exec Server on RFPLTSTJMFNPP1.
In the event viewer it says:
Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7001
Date: 7/25/2007
Time: 6:23:02 PM
User: N/A
Computer: RFPLTSTJMFNPP1
Description:
The Backup Exec Job Engine service depends on the Backup Exec Server service which failed to start because of the following error:
%%0
When I try to start the Backup Exec Server service it gives me the error:
Could not start the Backup Execc Server service on Local Computer. The service did not return an error. This could be an internal Windows error. If the problem persists, contact your system administrator.
The only changes in the system was that I added 2 more hard drives last week. I have checked to make sure that are not SCSI conflicts.
Any ideas?
Thanks,
3 of the 5 BE services are starting. 2 are not. Here is what I am seeing:
Processing services
Start services on server: RFPLTSTJMFNPP1
Starting Backup Exec Remote Agent for Windows Servers on RFPLTSTJMFNPP1.
The service Backup Exec Remote Agent for Windows Servers is already running on RFPLTSTJMFNPP1.
Starting Backup Exec Device & Media Service on RFPLTSTJMFNPP1.
The service Backup Exec Device & Media Service is already running on RFPLTSTJMFNPP1.
Starting Backup Exec Server on RFPLTSTJMFNPP1.
In the event viewer it says:
Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7001
Date: 7/25/2007
Time: 6:23:02 PM
User: N/A
Computer: RFPLTSTJMFNPP1
Description:
The Backup Exec Job Engine service depends on the Backup Exec Server service which failed to start because of the following error:
%%0
When I try to start the Backup Exec Server service it gives me the error:
Could not start the Backup Execc Server service on Local Computer. The service did not return an error. This could be an internal Windows error. If the problem persists, contact your system administrator.
The only changes in the system was that I added 2 more hard drives last week. I have checked to make sure that are not SCSI conflicts.
Any ideas?
Thanks,
ASKER
Also, I have verified the user account that we use to logon these services. All is well on that end. It is a domain account called Backup Admin and is in the Domain Admins group.
ASKER
More developments.
I can now start every BE service with the Domain credentials that we have set up EXCEPT for the Backup Exec Server service which will only start with the Local System Account.
So, I know that the credentials are good. Again they are Domain Admin credentials we created for this purpose.
I know that the Backup Exec Server Service will start, because I can start it with the Local Admin Account.
What am I leaving out here??? Why will the other 4 services start, but not the BE Server service?
I can now start every BE service with the Domain credentials that we have set up EXCEPT for the Backup Exec Server service which will only start with the Local System Account.
So, I know that the credentials are good. Again they are Domain Admin credentials we created for this purpose.
I know that the Backup Exec Server Service will start, because I can start it with the Local Admin Account.
What am I leaving out here??? Why will the other 4 services start, but not the BE Server service?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Eagle,
Thanks for the reply. The logon settings are exactly the same for all BE services. Backup Exec on this server was working until I rebooted the server on the 18th of July. Everything was fine.
The application was installed without issue and had been working for 3 years. The only other thing that has changed on the server was the new drives I put in last week, however BE went down before the drives were installed.
What perplexes me is why do the other services start with the exact same credentials and this Backup Exec Server service does not.
I did stop the Removable storage service and there was no change. BE Server service will still not come up.
Thanks for the reply. The logon settings are exactly the same for all BE services. Backup Exec on this server was working until I rebooted the server on the 18th of July. Everything was fine.
The application was installed without issue and had been working for 3 years. The only other thing that has changed on the server was the new drives I put in last week, however BE went down before the drives were installed.
What perplexes me is why do the other services start with the exact same credentials and this Backup Exec Server service does not.
I did stop the Removable storage service and there was no change. BE Server service will still not come up.
ASKER
I figured out the answer. The logon credentials had somehow been deleted out of DCOM and had no access to the BUE SQL Database.
Had to use DCOMCNFG to fix it.
Had to use DCOMCNFG to fix it.
Great work there iCoreKC. I bet that's the thing some users get when they install with the wrong credentials. In your case the credentials may have become corrupted. I hope my response helped. And thank you for letting me know how you resolved.
ASKER
Yep. No problem!
ASKER
Starting Backup Exec Remote Agent for Windows Servers on RFPLTSTJMFNPP1.
The service Backup Exec Remote Agent for Windows Servers is already running on RFPLTSTJMFNPP1.
Starting Backup Exec Device & Media Service on RFPLTSTJMFNPP1.
The service Backup Exec Device & Media Service is already running on RFPLTSTJMFNPP1.
Starting Backup Exec Server on RFPLTSTJMFNPP1.
Forgot to mention here is where it hangs....