Hi, Im running Backup Exec 2010 on a Windows 2008 R2 Server and I've been experiencing a strange problem the last few weeks. Every morning when I log onto the server I am greeted by the backup exec services manager dialog box that prompts me to restart the backup exec services. Since they have all been stopped overnight apparently for some reason I have to restart the services every morning and this is getting really frustrating. Please advise as to how I get solve this very annoying issue? Regards,

I too am unable to apply the SP4 update to the BKUPEXEC instance. What I did was to go to Windows Update and hide the update. This way, Windows Update will not try to update the instance.

The next time this happens, open the Windows Servvices console and see if all the Be services are stopped. Search in the windows event viewer for any messages related to a service crash. Check if there are any pending updates for SQL. I have typically seen this before when there is an update trying to install over SQL Instance and ends up stopping/crashing BE.

...are you on BE 2010 R3? Might be worth the upgrade as it fixed a number of issues with previous versions. You can use the same license keys. You just need to grab copies of the Data/Catalogs folders before doing any upgrade. Otherwise check and make sure that any AV running on the server isn't perhaps blocking the BE services... Thanks!

Hi Guys, Thanks for the speedy replies. I've checked the event viewer and the following backup exec services were indeed not running: Backup Exec Agent Browser Backup Exec Device & Media Service Backup Exec Job Engine Backup Exec Server I also found the following error in the event viewer: The Backup Exec service 'Backup Exec Server' failed to start because it uses a Windows Server account that does not have the following necessary privileges: Create Token Object As for the AV, we are currently using Kaspersky Endpoint Security 10 and not sure what to look for there...

Hi Sy, The BESA needs the following rights: http://www.symantec.com/business/support/index?page=content&id=TECH23689 Without them, you're going to run into issues. As for your AV, check to see if it is actively scanning the BE services, and if so, put in exclusions for them. I've had McAfee block BE services for some strange reason on a number of occassions. Thanks!

Hi Graig, Thanks for the link. Unfortunately that didn't do me much good, as on friday checked and confirmed that the domain admin account has all the rights as listed in the article. However that did not solve my problem, as this morning I was once again faced with the same dillema. I'm still getting the services stopped dialog box which I then have to manually restart. I also set my backup exec service manager to be excluded in my AV Firewall, however I think this has been an issue before I installed the new AV. Will still test like this and get back to you. Best Regards,

Backup Exec Stopped Services

18 Replies

Colin_Weaver
Moderator
11 years ago
As things now appear to be worse you should log a formal support case.

BTW your original problem was probably caused by the automated attempt to patch/update SQL as any attempt to stop the SQL instance for the Backup Exec database will stop the BE services.
Storm_Trooper
Level 3
11 years ago
Yes that sure was most certainly the case. The eventviewer logged events for the SQL update almost every night, so I thought upgrading to SP3 would solve all those problems for me. Is there a specific number or email address that I should use to log a formal support case?

Regards,
Storm_Trooper
Level 3
11 years ago
Thanks for the help guys. I did log a call with symantec and after much trial and tribulations, managed to get a successfull install of BE 2010 SP3. However that still did not solve my problem with the Microsoft SQL Express 2005 SP4 Update. The update is still failing each and every night and every morning I still have to start the BE Services manually.

But I'm not completely discouraged yet, will keep looking for a solution, the one I haven't tried yet is fiddling with the registry keys. Yes I am a little scared of making a mess of things again once I start messing with the registry, so I'm still gonna need some expert advice there.

Regards,
pkh
Moderator
11 years ago
I too am unable to apply the SP4 update to the BKUPEXEC instance. What I did was to go to Windows Update and hide the update. This way, Windows Update will not try to update the instance.
Storm_Trooper
Level 3
11 years ago
Thanks for the tip pkh, I did just that. Will let you know if it resolved my issue.
Storm_Trooper
Level 3
11 years ago
Hi Guys,

Looks like all my sql updates are failing and it's not just SP4. Last night I had a security update that also failed to install for the current SQL version (SP3). This is what i'm getting from the eventviewer:

Product: Microsoft SQL Server 2005 Express Edition - Update 'GDR 4060 for SQL Server Database Services 2005 ENU (KB2494113)' could not be installed. Error code 1603. Additional information is available in the log file C:\Program Files (x86)\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\SQL9_Hotfix_KB2494113_sqlrun_sql.msp.log.
pkh
Moderator
11 years ago
This is more a question for Microsoft rather than BE.
Storm_Trooper
Level 3
11 years ago
Thanks pkh, that actually worked for me as well. I think this is generally a SQL problem and so should be taken up with microsoft...!

Forum Discussion

Backup Exec Stopped Services

18 Replies

Related Content

Index services keep stopping

Backup exec service is stopped

BE Services Stopped

BackupExecAgentAccelerator services stopped

Index service stops after starting

Recent Discussions

Backup Exec Job got canceled

BackupExec for Oracle 23ai?

Add Oracle DB in Backup Exec

Veritas Backup Exec version upgrade & migrate to another new Server

Veritas Backup Exec 23 - Slow Backup after Windows server 2019 upgrade