Forum Discussion

Lavee383's avatar
Lavee383
Level 4
11 years ago

All jobs "BE job engine system service is not responding" after 2012 SP4/hotfix

I just recently installed SP4 and the hotfix that was listed after the upgrade (215906). 

Now every job fails even on the SBE server itself.  I've updated the Agent on all servers and rebooted all just to be safe.  Still nothing.  Jobs either fail outright or get missed and placed on hold.  As soon as I release the job, they either fail or go into the eternal spin "queued" until it places itself on hold.

Also, now when I try to view the errors from the Backup and Restore tab by clicking on the specific server's error, it errors out with:  "The server was unable to complete the requested operation.  Unknown reason: 2  BEMSDK Failure Code: 2:X8  Error: 2: The job log for this job may not be generated."  The only way I can view the log error is to go into the specific server and click on Active Alerts, then I can review the error messages.

SBE server:  2008R2 Standard

2012
Backing Up
Backup and Recovery
Backup Exec
Error messages
Troubleshooting
Upgrade
Windows Server (2003-2008)
  • pkh's avatar
    pkh
    11 years ago

    Go to Programs and Features and do a repair of BE.

20 Replies

Sort By
  • CraigV's avatar
    CraigV
    Moderator
    11 years ago

    Hi Lavee,

     

    Have you tried to repair the BEDB through BEutility.exe?

    Thanks!

  • Lavee383's avatar
    Lavee383
    Level 4
    11 years ago

    Thanks for the reply Craig...but can you explain to me what it is that I'm to do?  I've never had to use the utility...

  • CraigV's avatar
    CraigV
    Moderator
    11 years ago

    Not a problem...do a search for BEutility.exe and follow the TN below:

    http://www.symantec.com/business/support/index?page=content&id=TECH67239

    Thanks!

  • Lavee383's avatar
    Lavee383
    Level 4
    11 years ago

    I ran the repair according to your link and still nothing.  The jobs sit "Status: Queued"

  • Lavee383's avatar
    Lavee383
    Level 4
    11 years ago

    I may have spoke too soon...it looks like I was able to get one of the jobs to start working...it just sat as "queued" for longer than I'm normally used to seeing it.  Will update later after I get a couple more jobs kicked off and running.

    The job for the SBE server is "running" with 0.0 on both Bytes and Rate...

    ***scratch that...as soon as I hit reply on this message the SBE's job finally started...that was about 22min sitting in queue...?

  • pkh's avatar
    pkh
    Moderator
    11 years ago

    Go to Programs and Features and do a repair of BE.

  • Lavee383's avatar
    Lavee383
    Level 4
    11 years ago

    I was able to get one job to succeed but all after that are still failing.  I keep getting "The job failed with the following error: The Backup Exec job engine system service is not responding."

  • Lavee383's avatar
    Lavee383
    Level 4
    11 years ago

    I was able to get one job to succeed last night after I manually kicked it off.  But then the same exact server/job was ran again on it's own (per schedule) and it failed with the following:  "The job failed with the following error: The Backup Exec job engine system service is not responding."  All other jobs are failing as well.

  • Lavee383's avatar
    Lavee383
    Level 4
    11 years ago

    One side question since SBE2014 was mentioned...I thought SP4 was supposed to give Server2012R2 capability...yet when I try to edit the jobs of my two servers that I just rebuilt to 2012R2, it shows the server on one but when I try to delve into the C:\ drive it states it can't set up a network connection.  Where my other just won't show anything.  On my 2012 server, everything still shows up and I can drill down to specific folders/files on the job.

    I'm assuming that I need to upgrade to SBE2014 correct?  Also, if the job fails that are happening aren't fixed prior to upgrading to SBE2014, will they still be present in 2014?