UBQ000234: Common Backup Errors Explained

UBQ ID: UBQ000234
Last Modified: 2005-06-01

Summary:

The list of errors below are commonly found in UltraBac backup log files. Along with the error, basic trouble shooting steps can help to quickly resolve backup issues.

Details:

Error 5 - Access is denied.

5/31/2005 1:00:39 PM Error!

Failed to open file for backup '\\FIPI\D$\goldmine\GM4W6.DOC', error: (5-Access is denied.)

This error is directly related to permissions. If the user does not have permission to access the specified file, this error will be the result.

Error 23 - Data error (cyclic redundancy check).

5/30/2005 11:52:16 AM Error!

CheckWriteStatus, Error:(23 - Data error (cyclic redundancy check).)

This error usually means the tape device cannot properly read from or write to the current tape. Often times, this error can be cleared by cleaning the tape drive. It is strongly recommended to check the Windows System log for corresponding errors from the tape driver, SCSI driver or other hardware sources.

Error 32 - The process cannot access the file because it is being used by another process.

5/31/2005 3:42:22 AM Warning!
\\FIPI\D:\Program Files\Microsoft SQL Server\MSSQL\Data\master.mdf (32 - File In Use) (SHARING VIOLATION).

This error is returned when the file being backed up is open or exclusively locked by another application or service. To back these files up, either the application or service using the file needs to be closed, or a locked file backup agent can also back up many of these files safely.

In the case of Exchange or SQL database files, it is strongly recommended to use the corresponding backup agent in a separate set to ensure database integrity.

Error 53 - The network path was not found.

5/31/2005 2:02:44 PM Error!
Unable to find files \\LELE\H$\*.*, error: (53-The network path was not found.)

This error is returned when the share or folder being backed up cannot be found on the network. This error is often seen when there is a firewall blocking the system being backed up, when there are failures/issues on the network, and when the system to be backed up has been turned off.

Error 64 - The specified network name is no longer available.

5/9/2005 4:11:38 PM Error!
Unable to find files \\LELE\H$\*.*, error: (64-The specified network name is no longer available.)

This error is returned when the computer being backed up can no longer be contacted on the network. This error is usually caused by some kind of network issue, or the computer being turned off/rebooted during backup.

Error 170 - The requested resource is in use.

5/15/2005 7:00:20 PM Error!
Could not open device Tape0, error:(170-The requested resource is in use.)

This error is returned when the backup target device is being used by another application or process. Ensure there is not another backup process running when this error occurs. In the Windows Task Manager, check for any orphaned UB.exe processes, or more than one UBMS.exe process. This error can also be caused by UBUI.exe when in the beginning stages of a restore.

Error 1117 - The request could not be performed because of an I/O device error.

This error is often related to error 23. This error is almost always accompanied by entries in the Windows System log from either the SCSI card or the tape device. On occasion, cleaning the device can resolve this error, but usually this error means there is a critical failure in the hardware.

Error 10061 - No connection could be made because the target machine actively refused it.

5/13/2005 3:53:34 AM Warning!
Unable to start agent on FIPI (10061-No connection could be made because the target machine actively refused it.), attempting locally.

This error occurs when UltraBac's management service cannot connect to the management service on a remote system. This error usually means that the UltraBac Management service is either not started or not installed on the connection target (usually specified in the error). Ensure that UltraBac is installed on the remote target, and that there is an instance of UBMS.exe running.