Job Engine service fails to start and gives the following message:
Windows could not start the Backup Exec Job Engine service on Local Computer.
1053: The service did not respond to the start or control request in a timely manner.
The issue was seen on one of the user setup.
Workaround:
Disable the Lockdown feature from Backup Exec Global settings and then start the Job Engine service.
Note: The Backup Exec console works even with Job Engine service not starting (make sure other services are in running state) so one can open the BE console -> type the BE credentials and then, once inside the BE console -> Go to BE Global Settings -> Network and Security section to disable Lockdown settings. If the console does not allow login, then the issue could be different and it should be worked by opening a case with Technical Support.
This issue is currently under investigation by Veritas Technologies LLC. Pending the outcome of the investigation, this issue may be resolved by way of a patch or hotfix in current or future revisions of the software. However, this particular issue is not currently scheduled for any release. If you feel this issue has a direct business impact for you and your continued use of the product, please contact your Veritas Sales representative or the Veritas Sales group to discuss these concerns.
Note: Customers experiencing this issue are encouraged to contact Veritas Technical Support as data is still being collected to assist in resolving this issue.