Common Windows Error Codes

Several Arcserve Backup error messages include a reference to a Windows (or Microsoft) error code. These error codes indicate that the error was at least partially caused by a problem involving Windows.

The following list describes the five Windows error codes you are most likely to encounter using Arcserve Backup. For explanations of other Windows error codes, please consult your Windows documentation.

Sharing Violation (32)

• Possible Cause: The file indicated in the message is being used by another program or process, so it cannot be backed up or restored at this time.
• Possible Resolution: If you know which program or process is using the file, stop that program or process and resubmit the job. If you do not know which program or process is using the file, restart your computer, and then resubmit the job. If neither of these solutions solve the problem, you might have to modify the job so that the indicated file is not included.

Access Denied (5)

• Possible Cause: The account under which the backup job is being run does not have the proper privileges to access the specified file.
• Possible Resolution: Grant the account a higher level of access privileges, or run the backup job under an account that already has the proper privileges.

File Not Found (2)

• Possible Cause: The file indicated in the message has been moved or deleted since the backup job was created.
• Possible Resolution: Modify the backup job as appropriate and resubmit the job.

Path Not Found (3)

• Possible Cause: Arcserve Backup was unable to find the specified path, most likely because the path was deleted between the time the backup job was created and the time it was submitted.
• Possible Resolution: Modify the backup job as appropriate and resubmit the job.

Bad Net Path (53)

• Possible Cause: Arcserve Backup was unable to find the specified network path, either because the network path doesn't exist, or because there was a bad network connection.
• Possible Resolution: Verify that the specified network path is still valid and that your network connection is functional, and then make the necessary changes and resubmit the job.