Video Screencast Help
Search Video Help Close Back
to help
New in the Rewards Catalog: Vouchers for "Symantec Technical Specialist" and "Symantec Certified Specialist" exams.

Backup Exec job engine system service is no responding.

Updated: 21 May 2010 | 3 comments
noidea's picture
0 0 Votes
Login to vote

Backups keep failing as the job engine service fails to start after automatic reboots (windows update) or fails to respond if running - i have tried a repair installation of symantec so far.

Windows SBS 2008 
Backup Exec 12.5 SP 2

Back exec error code: e00081d9 - The Backup Exec job engine system service is not responding

Windows Application log: 

Event id: 34113

(Server: "SERVER") (JOB: "DailyBackup") DailyBackup -- the job failed with the following error: The Backup Exec job engine system service is not responding

Any ideas ?

Comments

Dev T's picture
16
Nov
2009
0 Votes 0
Login to vote

.NET repair install

Hello,

I would suggest you to perform a repair install of .NET Framework OR uninstall and reinstall .NET framework.

Let me know

Its a best practice to have a "Support Contract" with Symantec...
 

noidea's picture
17
Nov
2009
0 Votes 0
Login to vote

 Hi,  Thanks for your

 Hi, 

Thanks for your suggestion - Tried this and after a reboot the service failed to start again

I set up a new backup job (to disk folder this time) and scheduled a few minutes away and the service failed to start here aswel

Any more suggestions ?

bknysak's picture
20
Nov
2009
0 Votes 0
Login to vote

I'm having what seems to be

I'm having what seems to be the same problem:
Server 2008 Standard, R2 with SP2
BKEXEC 12.5
x64 Dell T410

The job engine service keeps stopping on me with error e00081d9. I've tried everything I could find in the KB:
repair/reinstall .NET
verify System Writer in vassadmin
apply all BKEXEC updates/patches

I am unable to complete these updates, each time returning with an error:
Update to MS SQL Server 2005 service pack 3 (returns error 737d: unknown error)
Apply BKEXEC Service Pack 3 (error LU1812)

Suggested fixes for both of these yield nothing.

Possibly of iterest, I migrated from a 11d install on a Server 2003 machine, moving the backup jobs as suggested by an article here.

Help!