Backup Exec Error 57665
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 English 中文(简体) English Français Deutsch Italiano 日本語 한국어 Português Español USA Site: Veritas Veritas PartnerNet Event ID 57665 is reported in the event viewer when Backup Exec job engine receives an error on any command sent to the specified storage device Article:000025058 Publish: Article URL:http://www.veritas.com/docs/000025058 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 Article Languages Subscribe to this Article Manage your Subscriptions Problem Following is reported in the Event Viewer when the Backup Exec job engine receives an error on any command sent to the specified storage device. Error Message Event ID: 57665Source: Backup Exec Job EngineType: ErrorDescription: Storage device "%device%" reported an error on a request to %failed command%. Error reported:%error description%. Solution This is a generic event logged for tape device errors.The event was reported in the application log because the Backup Exec job engine received the specified error when issuing the specified command to the specified drive. This is most often indicative of a hardware failure.Depending on the type of error, it may indicate that the drive needs to be cleaned or that the media is no longer reliable. Other errors may be resolved by stopping the Backup Exec services cycling power on the drive or robotic library and restarting the services. If the problems persist, contact your hardware vendor. Terms of use for this informatio
Governance Backup and Recovery Business Continuity Partners Inside Veritas Vision 2016 Developers Information Governance Backup and Recovery Business Continuity Partners Inside Veritas Vision 2016 Developers Blogs Groups Vision 2016 Sign In CommunityCategoryBoardResourcesUsers turn on suggestions Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type. Showing results for Search instead for Do you mean VOX : Backup and Recovery : Backup Exec : Backups Keep failing with 33152,57665,34113 as the... VOX : Backup and Recovery : Backup Exec : Backups Keep failing with 33152,57665,34113 as https://www.veritas.com/support/en_US/article.TECH23660 the... Subscribe to RSS Feed Mark Topic as New Mark Topic as Read Float this Topic to the Top Bookmark Subscribe Printer Friendly Page Backups Keep failing with 33152,57665,34113 as the error id's Jimmy_O_Brien Level 2 08-08-2005 04:00 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content My backups keep failing with the https://vox.veritas.com/t5/Backup-Exec/Backups-Keep-failing-with-33152-57665-34113-as-the-error-id-s/td-p/38110 following error codes in my event log with 33152,57665,34113.When i search the fourms i get a lot of advice for the above codes but i am not sure what i should start with and what step i should take.Please advise Labels: 10.x and Earlier Backup and Recovery Backup Exec 0 Kudos Reply 6 Replies Re: Backups Keep failing with 33152,57665,34113 as the error id's Sharvari_Deshmu Level 6 08-09-2005 01:20 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content Hello,Please elaborate the problem?What backups are you taking?Are you backing up any remote servers?Do you get these errors on the device?Please paste the exact error message that you receive from the job log?Are you backing up exchange or SQL database?Thanks,NOTE : If we do not receive your reply within two business days, this post would be marked assumed answered and would be moved to answered questions pool. 0 Kudos Reply Re: Backups Keep failing with 33152,57665,34113 as the error id's Jimmy_O_Brien Level 2 08-09-2005 02:18 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Repo
DriverDoc WinSweeper SupersonicPC FileViewPro About Support Contact Errors Troubleshooting › Runtime Errors › Symantec › Backup Exec › Error 57665 How To Fix http://www.solvusoft.com/en/errors/runtime-errors/symantec/backup-exec/57665-backup-exec-error-57665/ Backup Exec Error 57665 Error Number: Error 57665 Error Name:Backup Exec Error 57665 Error Description: The request could not be performed because of an I/O http://www.chicagotech.net/others/backupexec9.htm device error. Developer:Symantec Software:Backup Exec Applies to:Windows XP, Vista, 7, 8 Download NowWinThruster 2015 - Scan your PC for computer errors. Compatible with Windows backup exec 10, 8, 7, Vista, XP and 2000 Symptoms of Error 57665 "Error 57665" appears and crashes the active program window. Your PC frequently crashes with Error 57665 when running the same program. “Backup Exec Error 57665” is displayed. Windows runs sluggishly and responds slowly to mouse or keyboard input. Your backup exec error computer periodically “freezes” for a few seconds at a time. These 57665 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 57665 error occurs is a critical piece of information in troubleshooting the problem. Causes of Error 57665 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 57665” 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 Erro
ID 33808: An error occurred while processing a B2D command. Drive: ReadMTFData() ReadFile failed. Error=1450 - Resolution with screenshots Event ID 57665: Insufficient system resources exist to complete the requested service - Resolution with screenshots Event ID 34113: The job failed with the following error: The backup storage device has failed - Resolution with screenshots Situation: The client is running Backup Exec to back up their data to a 4 TB external USB drive. The backup is failed with these errors: Final error: 0xe00084c8 The backup storage device has failed. Final error category: Backup Device Errors In the application event log there are these events: Event Type: Error Event Source: Backup Exec Event Category: None Event ID: 33808 Description: An error occurred while processing a B2D command. Drive: ReadMTFData() ReadFile failed. Error=1450 Event Type: Error Event Source: Backup Exec Event Category: None Event ID: 57665 Description: Storage device Friday N: reported an error on a request to read data from media. Error reported: Insufficient system resources exist to complete the requested service. Event Type: Error Event Source: Backup Exec Event Category: None Event ID: 34113 Description: Backup Exec Alert: Job Failed (Job: Friday Backup to N:) Friday Backup to N: The job failed with the following error: The backup storage device has failed. Possible cause: Possible resolutions: A. Set the USB drive to Optimize for performance. Go to Device Manager. Navigate to Disk drives>USB drive name. Right click it and select Properties. Click Policies tab. Check Optimize for performance. B. Registry setting 1 1. Click Start, click Run, type regedit in the Open box, and then click OK. 2. Locate and then click the following registry subkey: 3. HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management 4. On the Edit menu, point to New, and t