Backup Exec Server Service Will Not Start Error 1053
Contents |
SERVICES Services Overview Education Services Business Critical Services Consulting Services Managed Services Appliance Services CUSTOMER CENTER Customer Center Support Community MyVeritas Customer Success Licensing Programs Licensing Process ABOUT About Corporate Profile Corporate Leadership Newsroom Research Exchange Investor Relations Careers Legal backup exec job engine error 1053 Contact Us English 中文(简体) English Français Deutsch Italiano 日本語 한국어 Português Español USA
The Backup Exec Server Service Did Not Start. An Internal Error (10) Occurred In Object 13
Site: Veritas Veritas PartnerNet When trying to start Backup Exec Server service "Error 1053: The service did not respond to the start or control request in a timely fashion" Article:000008281 Publish: Article URL:http://www.veritas.com/docs/000008281 Support / Article Sign In Remember me Forgot Password? Don't have a Veritas Account? Create a Veritas Account now! Welcome First Last Your Profile Logout Sign in to Subscribe Please sign in to set up your subscription. Close Sign In Print Article Products Related Articles Article Languages Subscribe to this Article Manage your Subscriptions Problem When trying to start Backup Exec Server service "Error 1053: The service did not respond to the start or control request in a timely fashion" Error Message Error 1053: The service did not respond to the start or control request in a timely fashion. When trying to start Backup Exec Server service the following error encountered in the event viewer EVENT ID 1000 Faulting application beserver.exe, version 13.0.2896.108, time stamp 0x4b84a57a, faulting module ntdll.dll, version 6.0.6002.18005, time stamp 0x49e0421d, exception code 0xc0000005, fault offset 0x000000000002592a, process id 0x%9, application start time 0x%10. When tried to start BESERVER service in console mode, following error was shown in output log: [5392] 07/26/10 09:28:19 -1 Business Object 71 failed to initialize:-2147024891 [5392] 07/26/10 09:28:19 -1 RpcXfaceServiceMain: InitializeBOs() failed, BO:71,nRet:-2147024891 Solution 1. From the Windows services console (Start > Run > Services.msc) - Change the properties of each Backup Exec service to start under Local system Account. 2. Reboot the media server. 3. Open Backup Exec console - Tools - Backup Exec services - Services credentials - Change service account information - Enter the Domain Administrator credentials (Backup Exec System Account) - Ok - Click on Restart all services. Terms of use for this information are found in Legal Notices.
Related Articles Article Languages x Translated Content Please note that this document is a translation from English, and may have been machine-tSERVICES Services Overview Education Services Business Critical Services Consulting Services Managed Services Appliance Services CUSTOMER CENTER Customer Center Support Community MyVeritas Customer Success Licensing Programs Licensing Process ABOUT About Corporate Profile Corporate Leadership Newsroom Research Exchange Investor Relations Careers Legal Contact Us English 中文(简体) English Français Deutsch Italiano 日本語 한국어 Português Español USA Site: Veritas Veritas PartnerNet When attempting to start the Backup Exec Server or Backup Exec Job Engine Service, "Error 1053: The service did not respond to https://www.veritas.com/support/en_US/article.000008281 the start or control request in a timely fashion" occurs. Article:000009260 Publish: Article URL:http://www.veritas.com/docs/000009260 Support / Article Sign In Remember me Forgot Password? Don't have a Veritas Account? Create a Veritas Account now! Welcome First Last Your Profile Logout Sign in to Subscribe Please sign in to set up your subscription. Close Sign https://www.veritas.com/support/en_US/article.000009260 In Print Article Products Article Languages Subscribe to this Article Manage your Subscriptions Problem When attempting to start the Backup Exec Server or Backup Exec Job Engine Service, "Error 1053: The service did not respond to the start or control request in a timely fashion" occurs. Or Backup job fails with an error " e00081d9 - The Backup Exec job engine system service is not responding." Error Message Backup Exec job engine is not starting up on server name. Error 1053: The service did not respond to the start or control request in a timely fashion Cause This can happen when: 1. SQL instance of Backup Exec or Backup Exec Server service are not set to start with Local System Account(LSA) in Windows Services Applet. OR 2. Latest Backup Exec service pack has not been installed. Solution Check the windows application and system event logs during the period of time the services w
SERVICES Services Overview Education Services Business Critical Services Consulting Services Managed Services Appliance Services CUSTOMER CENTER Customer Center Support Community MyVeritas Customer Success Licensing Programs Licensing Process ABOUT About Corporate Profile Corporate Leadership Newsroom Research Exchange Investor Relations Careers Legal Contact Us https://www.veritas.com/support/en_US/article.TECH73733 English 中文(简体) English Français Deutsch Italiano 日本語 한국어 Português Español USA Site: Veritas Veritas PartnerNet "Error 1053: The service did not respond to the start or control request in a timely fashion" occurs and https://community.spiceworks.com/topic/138503-backup-exec-remote-agent-not-starting the Backup Exec Server service fails to start, or is hung in "Starting" while using large amounts of memory Article:000039805 Publish: Article URL:http://www.veritas.com/docs/000039805 Support / Article Sign In Remember me Forgot Password? Don't have backup exec a Veritas Account? Create a Veritas Account now! Welcome First Last Your Profile Logout Sign in to Subscribe Please sign in to set up your subscription. Close Sign In Print Article Products Article Languages Subscribe to this Article Manage your Subscriptions Problem The following error occurs and the Backup Exec Server service fails to start, or is hung in "Starting" while using large amounts of memory Error Message backup exec server "Error 1053: The service did not respond to the start or control request in a timely fashion" Cause Due to corrupt XML file getting generated in Data folder. Corrupt job log file created from job logging level, or application error located in the database directory of Backup Exec Default path is C:\Program Files\Symantec\Backup Exec\Data Solution Remove the corrupt job log xml file from the data directory, by moving it to another drive or server if possible, and contact technical support. Terms of use for this information are found in Legal Notices.
Related Articles Article Languages x Translated Content Please note that this document is a translation from English, and may have been machine-translated. It is possible that updates have been made to the original version after this document was translated and published. Veritas does not guarantee the accuracy regarding the completeness of the translation. You may also refer to the English Version of this knowledge base article for up-to-date information. Attachment Products Subscribe to Article Search Survey Did this article answer your question or resolve your issue? No Yes Did this article save you the trouble of contacting technical support? No Yes How can we make this article more helpfulminutes. Join Now Greetings everyone - Operating System: Server 2008 32-bit Backup Exec Version: 2010R2 Recently I've run into a problem on my sole Server 2008 (nonR2) server. It started when the NIC was not working properly and the activation had apparently timed out (thought I activated it but apparently not). I swapped out the NIC and Windows would not boot. I though it was an activation issue, I got into safe mode and did a diagnostic startup with msconfig. Rebooted out of safe mode I got Windows activated by changing the product key from KMS to volume license. Selected a normal startup in msconfig and the system would not boot. Went back to diagnostic startup and narrowed the problem down to the "Backup Exec Remote Agent for Windows Systems" service. First my research suggested a conflict between .NET and the service. So I uninstalled both, installed .NET and then Backup Exec RAWS. It's still freezing. The other possible issues was with a lack of an email client. This server has never had Outlook or Outlook Express installed on it. It backed up files for about a month before it stopped working. If I disable the service in safe mode, boot the server, enable the service and try to start it I get an error 1053 saying the service failed to start in a timely fashion. I see no Backup Exec entries in the event viewer. If I run the BE_SupportTool.exe file on the server with a full software analysis it hangs on the Enumerate VSS Wirters and Providers. Does anyone have any insight as to what may be causing this? Thanks Reply Subscribe RELATED TOPICS: Backup Exec Remote Agent is not working correctly and I cannot connect. issue upgrading backup exec remote agent to 2014 Why doesn't Spicework recognise Backup Exec Remote Agent service?   16 Replies Mace OP Denis Kelley May 5, 2011 at 10:16 UTC Not sure if this is your utility server or not, but if you don't have much on this server I would just wipe and re-install from scratch. Might be quicker and you would know things are working. 0 Tabasco OP 1394 May 5, 2011 at 10:41 UTC Sounds like your VSS provider list is corrupt... What happens when you run "vssadmin list writers" from a command prompt? 0 Mace OP Denis Kelley May 5, 2011 at 10:49 UTC 1394 wrote: Sounds like your VSS provider list is corrupt... What happens when you run "vssadmin list writers" from a command prompt? That is possible. I had a failed backup last night due to VSS issues and used this to make sure it was working. MS/Symantec both have articles on re-registering the files if necessary. I suggested a refresh mainly because there were multiple issues that seem somewhat unrelated. NIC