An Internal Error 4313 Occurred In Object
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 the backup exec server service did not start. an internal error (10) occurred in object 13. Profile Corporate Leadership Newsroom Research Exchange Investor Relations Careers Legal Contact Us the backup exec server service did not start. an internal error (-1) occurred in object 50 English 中文(简体) English Français Deutsch Italiano 日本語 한국어 Português Español USA Site: Veritas Veritas PartnerNet Event ID the backup exec server service did not start. an internal error (-1) occurred in object 51 57802 - The Backup Exec Server Service did not start. An internal error (4313) occurred in object -1. Article:000037533 Publish: Article URL:http://www.veritas.com/docs/000037533 Support / Article Sign In Remember
Backup Exec Server Service Will Not Start
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 Article Languages Subscribe to this Article Manage your Subscriptions Problem Event ID 57802 - The Backup Exec Server Service did not start. An internal error (4313) occurred in object -1. Error Message The Backup Exec Server Service did not start. An internal error (4313) occurred in object -1. Solution The Backup Exec Server Service (BESERVER.EXE) will not start and the following error is reported in the Application Log: ERROR: Event Type: ErrorEvent Source: Backup ExecEvent Category: (65535)Event ID: 57802 Description:The Backup Exec Server Service did not start. An internal error (4313) occurred in object -1. The Backup Exec Server service will not start if the Backup Exec SQL database (BEDB) is in Single User Mode. Please use the SQL Management Tools to determine if the BKUPEXEC BEDB SQL database is in Single User mode. If it is in Single User Mode, take the Backup Exec database out of Single User mode and restart the SQL SERVER (BKUPEXEC) service and all the Backup Exec services. How to: Set a Database to Single-user Modehttp://msdn.microsoft.com/en-us/library/ms345598.aspx Terms of use for this information are found in Legal Notices.
Related Articles ArtiDriverDoc WinSweeper SupersonicPC FileViewPro About Support Contact Errors Troubleshooting › Runtime Errors › Symantec › Backup Exec › Error 4313 How To Fix Backup Exec Error 4313 Error Number: Error 4313 Error Name:The Backup Exec Server Service did not start Error Description: The Backup Exec Server Service did not start. An internal error (4313) occurred in object -1. Developer:Symantec Software:Backup Exec Applies to:Windows XP, Vista, 7, 8 Download NowWinThruster 2015 - Scan your PC for computer errors. Compatible with Windows 10, 8, https://www.veritas.com/support/en_US/article.TECH68418 7, Vista, XP and 2000 Symptoms of Error 4313 "Error 4313" appears and crashes the active program window. Your PC frequently crashes with Error 4313 when running the same program. “The Backup Exec Server Service did not start” is displayed. Windows runs sluggishly and responds slowly to mouse or keyboard input. Your computer periodically http://www.solvusoft.com/en/errors/runtime-errors/symantec/backup-exec/4313-the-backup-exec-server-service-did-not-start/ “freezes” for a few seconds at a time. These 4313 error messages can appear during program installation, while a Symantec-related software program (eg. Backup Exec) is running, during Windows startup or shutdown, or even during the installation of the Windows operating system. Keeping track of when and where your 4313 error occurs is a critical piece of information in troubleshooting the problem. Causes of Error 4313 Corrupt download or incomplete installation of Backup Exec software. Corruption in Windows registry from a recent Backup Exec-related software change (install or uninstall). Virus or malware infection that has corrupted Windows system files or Backup Exec-related program files. Another program maliciously or mistakenly deleted Backup Exec-related files. Runtime Errors such as “Error 4313” can be caused by a variety of factors, so it is important that you troubleshoot each of the possible causes to prevent it from recurring. Runtime Errors Knowledgebase Article ID: 130345 Article Author: Jay Geater Last Updated: 18-07-2016 Popularity: star rating here
Mobile: Android BlackBerry WP7… Office 365 & Hosting Office: Word, Excel, Outlook… System Center Windows Client: Win http://www.urtech.ca/2012/03/solved-the-backup-exec-server-service-on-local-computer-started-and-then-stopped-an-internal-error-22-occurred-in-object-11/ 7 8 & 10 Windows Server Other Technologies Jokes News Contact https://www.backupassist.com/support/en/knowledgebase/BA4313-Exbackup-failed-due-to-an-internal-error.html?cshid=BA4313 SOLVED: The Backup Exec Server service on Local Computer started and then stopped. An internal error (-22) occurred in object 11 Home » SOLVED: The Backup Exec Server service on Local Computer started and then stopped. An internal error (-22) occurred in object 11 Mar an internal 2012 Posted by Ian Matthews+ in Other Technologies | Comments If you can't get your Symantec Backup Exec Server Services to start and you see errors like: The Backup Exec Server service on Local Computer started and then stopped. Some services stop automatically if they are not in use by other services or programs. and in the an internal error Windows Event Log (Application): The Backup Exec Server Service did not start. An internal error (-22) occurred in object 11. my experience has shown two causes of this: Symantec's "Live Update" is stuck on SOLUTION: look in Task Manager for LUGETUPDATES.EXE on the Processes tab and END TASK on it Some software is using Backup Exec's default port of 3527 SOLUTION: in a command line run NETSTAT -B > C:\LOG.TXT and then search that log for 3527 to find out what software is using it You might find these articles also of use: http://www.symantec.com/business/support/index?page=content&id=TECH140394&actp=search&viewlocale=en_US&searchid=1332225047506 http://www.symantec.com/business/support/index?page=content&id=TECH69603&actp=search&viewlocale=en_US&searchid=1332225442568 Share This With Your Friends Now: Related Tags: 2010, 2012, An internal error (-22) occurred in object 11, unable to start backup exec server service Leave a Reply Click here to cancel reply. Name * Email * Website Comment Add Comment Notify me of follow-up comments by email. Notify me of new posts by email.Please confirm you are a person and not a 'bot' by answering this simple question: Time lim
error and the correct way to proceed. Please send technical support a copy of the BackupAssist diagnostics file using the steps provided in the Resolution section below.ResolutionTo send us diagnostic information, please follow these steps:Open BackupAssist.Click on the Help menu at the top of the console.Select Feedback and Support... from the drop down menu.Click on Contact Support.Enter the details asked for.Make sure the tick box stating 'Submit system diagnostics to help our support team with your query' is ticked. This will zip all your BackupAssist settings so that we can review these specifically for your environment.Last updatedCreatedFurther assistance10th Feb 201010th Feb 2010BackupAssist Support page