Home > Backup Exec > Backup Exec Error Codes

Backup Exec Error Codes


If replacing the tape doesn't work, the problem is most likely related to device drivers or the tape drive itself. We ended up having to abandon Backup Exec and go elsewhere.  0 Jalapeno OP Craig IT Feb 20, 2015 at 7:37 UTC well that turns my stomach... 0 The following error can occur if C: drive on the server does not have enough free space. Specifically, one of the VSS writers used to back up an application running on the server reported a status of failed, which caused Backup Exec to produce error E000FED1. have a peek at this web-site

Designed by Elegant Themes | Powered by Wordpress Home Symantec Backup Exec 2014 Error e000fe30 - A communications failure has occurred by Craig IT on Feb 20, 2015 at 6:30 UTC If occurs with an specific job, test the jobs credentials. 5. Watch at the top for a process named "_Setup.exe". Check if VSS (Volume Shadow Copy) writers are in a stable state using the "vssadmin list writers" cmd.

Backup Exec Error Codes

d. Translated Content This is machine translated content Login to Subscribe Please login to set up your subscription. By creating an account, you're agreeing to our Terms of Use, Privacy Policy and to receive emails from Spiceworks.

WARNING: Installation has been canceled. Close Sign In Print Article Products Related Articles Article Languages Subscribe to this Article Manage your Subscriptions Problem When attempting to run a backup job "Physical Volume Library Drive not available" Writer Name: Registry, Writer ID: {AFBAB4A2-367D-4D15-A586-71DBB18F8485}, Last error: The VSS Writer ran out of memory or resources (0x800423f1), State: Failed during prepare snapshot operation (8).  V-79-57344-65233 - AOFO: Initialization failure on: Storage Has Not Been Configured For The Backup Exec Server In Backup Exec, go to Tools, Options, Advanced Open File b.

About Us Contact Us Privacy Policy Advertisers Business Partners Media Kit Corporate Site Contributors Reprints Archive Site Map Answers E-Products Events Features Guides Opinions Photo Stories Quizzes Tips Tutorials Videos All V-79-57344-33967 - The Directory Or File Was Not Found, Or Could Not Be Accessed. Enabling the Backup Exec Advanced Open File Option (AOFO) can be used to avoid the error on certain types of open files. Best Answer Serrano OP Elias_VTC (Veritas) Feb 20, 2015 at 8:12 UTC Brand Representative for Veritas Double check your firewall ports that you have opened on the server(s)While this is an SearchDataBackup Search the TechTarget Network Sign-up now.

If a reboot does not clear the error, you will have to troubleshoot the VSS writer itself (and the underlying application) rather than Backup Exec. Ready No Backup Exec Servers Are Available 2012 No Yes How can we make this article more helpful? Note: (This will require the server be rebooted so make sure you have scheduled maintenance for downtime)  2.  Defragment the volume where the data in question resides   3.  If the Solution Disable Microsoft Windows ''Install updates and shutdown'' feature.

V-79-57344-33967 - The Directory Or File Was Not Found, Or Could Not Be Accessed.

Kindly try the following steps: 1.  Go to the command prompt and run CHKDSK /r /f to verify the integrity of the disk and fix any file system errors. Privacy Please create a username to comment. Backup Exec Error Codes A user session or Backup Exec services restart  is neccessary after changes in accounts used with Backup Exec. 2. Backup Exec 2014 Discovering Resources Create/Manage Case QUESTIONS?

The list might be empty with a connection error. Check This Out Thank You! The following services need to be running: SQL (Bkupexec) BE Remote Agent BE Device and Media BE Server Service BE Job Engine Service BE Agent Browser Oftentimes, you can force a This would include another backup running against the same resource at the same time as a problematic job.More files are open than the memory cache manager can handle. Backup Exec Service Account Permissions

In many cases, the error is accompanied by a message indicating the tape drive needs to be cleaned. Veritas does not guarantee the accuracy regarding the completeness of the translation. In some cases, it can be related to a problem with the Microsoft .NET Framework. http://netlookmag.com/backup-exec/backup-exec-rpc-service.html After making any changes, it is a good idea to reboot the server.

No Yes How can we make this article more helpful? The Backup Exec Server Service Did Not Start. An Internal Error (10) Occurred In Object 13. This has the same result (that is, the paged pool is exhausted). Click on "View Selection Details". 4.

Additional services may be required depending on how Backup Exec was installed.

I recommend downloading and installing the latest device drivers for your tape drive. OR Unable to run Setup.exe. The operation cannot be retried (0x800423f4), State: Failed during prepare snapshot operation (8). Backup Exec Error 1068 The Dependency Service Add Cancel × Insert code Language Apache AppleScript Awk BASH Batchfile C C++ C# CSS ERB HTML Java JavaScript Lua ObjectiveC PHP Perl Text Powershell Python R Ruby Sass Scala SQL

Great care should be taken when making changes to a Windows registry. No Yes How can we make this article more helpful? Figure 2:   Scenario 8: An error is recorded in the Windows event viewer: Event Type: ErrorEvent Source: Backup ExecEvent Category: NoneEvent ID: 57481Date:  7/13/2010Time:  7:47:30 PMUser:  N/AComputer: Test123Description:An unusual error http://netlookmag.com/backup-exec/install-failed-with-error-code-1603-backup-exec.html The Backup Exec server is not rebooted and/or Backup Exec services are not restarted after a tape library is replaced. 3.

This causes Windows to launch the Service Control Manager, which can be used to view the properties for the various services. The answer? You also agree that your personal information may be transferred and processed in the United States, and that you have read and agree to the Terms of Use and the Privacy Unfortunately, you will need to actually log in remotely or physically to your server you want to install the agent on manually as an account with administrative privileges.  The Solution: Log

We'll send you an email containing your password. The root cause is that the installer is spawning a process twice, and both processes are conflicting with each other. If the resource does not exist, modify the backup job selection list and remove the entry for the  resource per the following steps: 1. Attachment Products Subscribe to Article Search Survey Did this article answer your question or resolve your issue?