Ref: 11640090 Title: Miscellaneous Error Messages From 3+Backup Date: 8/24/90 Copyright 3Com Corporation, 1991. All rights reserved. The following messages are in alphabetical order. BAD DATE The date you entered is not in the format dd-mmm-yy, hh:mm or part of the date is out of the reasonable range. Enter the correct date. BAD DEVICE TYPE When issuing a 3F LINK command, you tried to link to an unidentifiable device type. Try the link procedure again, and check to make sure you are using the right version levels. BAD DOS PATHNAME The DOS pathname you entered contains incorrect characters. Enter a valid DOS pathname. BAD DRIVE ID The drive identifier does not fall within the range of C: through Z:, or c: through z:. Enter a valid driver identifier. BAD FILENAME The specified filename or extension contains invalid characters or is longer than the allowable DOS maximum. Enter a valid filename. BAD PARTITION RANGE Partitions are specified incorrectly with the highest partition first (for example, f: to c:). Enter the partitions in sequence from c: to z:. BAD PASSWORD You have included an incorrect password with a shared directory name. Reenter the correct password with the shared directory name. BAD REQUEST A disk error has occurred on the server. Retry the operation. If the message appears again, have your network administrator check for data corruption of the hard drive. BAD TYPE One of the parameters in a 3B transaction is bad. This message should rarely appear; if it does, try a new version of 3B.EXE. BACKUP COMPLETED (UN)SUCCESSFULLY This is the status of the backup once it is completed. If the backup was unsuccessful, look at the log file to determine the reason why. BACKUP SERVICE NOT INSTALLED The server that received a 3+Backup command was not running 3+Backup at the time. Specify a 3+Backup default server using Set Tape Backup Unit. CHANGE THE TAPE A backup or restore operation has come to the end of data on the present cartridge. If running a backup, insert a tape (one not containing data from the present backup operation). If running a restore, insert the next tape in the sequence. CONTROLLER READ-AFTER-WRITE FAILURE The tape drive refused to write data to the tape, but reports no errors. Retry the backup. Run tape test check for bad controller. Check jumper settings and cabling. CURRENT DATA The tape holds data from the present backup operation. Insert another tape, one not holding current backed-up data. EMPTY TAPE The tape contains no data; it has been erased. Insert a tape containing data. ERROR CONNECTING TO DRIVE (DRIVE ID) 3+Backup cannot connect to the drive you specified for backup. Retry the backup beginning with that partition. Check the status of the source server and make sure it is up and running. ERROR DISCONNECTING FROM DRIVE (DRIVE ID) The file service reported an error when 3+Backup attempted to unlink the given drive ID. Try the operation again. If the error persists, write down the error message and contact your authorized 3Com reseller. FILE ACCESS ERROR The file service reported an error when 3+Backup was trying to access a remote file. The specific operation it was trying to perform may have been a read, write, search, open, close, or create. Retry the operation and check the file access error list for definition of error numbers. FILE ACCESS ERROR, FILE IN USE 3+Backup was unable to access a file because the file was already in use--either it was already open or a range within the file was locked. Perform the backup or restore only when files are not in use. FILE BEGINS AT OFFSET file: The first file on the tape is the continuation of a file on a previous tape. FILE SIZE DIFFERENT THAN EXPECTED The size of a file is not accurately recorded in a directory, or it was changed while a backup was in progress. Run the DOS CHKDSK command on the file in question. Make sure that the file area is not in use while a backup is in progress. FILE TRUNCATED AT OFFSET The file being backed up was in use and could not be completely backed up onto the tape, or the tape was truncated at one end and continues on another. INSERT TAPE There is no tape cartridge in the backup server. Insert a tape cartridge. INTERNAL ERROR The system has encountered inconsistency in the software. Restart 3+ Backup. If the error message appears again, shut down and restart the server. INTERNAL ERROR An unexpected software error has occurred during a backup or restore operation. Write down the occurrence and the error number. Shut down and restart the server, then repeat the operation. If the error recurs, contact your authorized reseller. MINDSPRO 12 and 9 ERROR You are trying to run backup from a LPO workstation. The PRO.SYS and BUF.SYS drivers need to be in the CONFIG.SYS and AUTOEXEC.BAT RUNMINDS command. For example: autoexec.bat runminds mindspro mindsbuf config.sys device=pro.sys 12 2 2 device=buf.sys ONE OR MORE PARTITIONS DO NOT EXIST One or more partitions specified in a backup do not exist. Check the partitions you specified for backup and try again. This information could be entered manually under 3BMEN or 3BMENDOS or in AUTOTIMS. OPERATION CANCELLED The operation you wanted to cancel has been cancelled. OTHER OPERATION IN PROGRESS You tried to start an operation when another operation was in progress. Read the section titled "Other Operation in Progress." OUT OF MEMORY 3+Backup cannot run without more memory. Eliminate any other programs that are using too much memory while 3+Backup is running, or add more memory, or retune the 3+Backup server. PATH PART TOO BIG A segment of the pathname exceeds the limit of eight characters. Reenter the correct path. PATH TOO BIG A DOS path exceeds the limit of 64 characters. Enter a shorter path. PLEASE LOGIN FIRST You must log into the network before you can use the 3+Backup command. POWER FAILED DETECTED. OPERATION CANNOT CONTINUE A system power failure has occurred and the operation you requested cannot continue. Wait until the power is restored and try the operation again. READY TIME OUT (RDY TIME OUT) When a 3Server was upgraded to a 3Server3, it had an old ADSI tape unit with the jumper on JI (should have been J2) and no terminator on the back of the unit. If you erase tapes and start a backup, a couple of minutes into the backup it dies with a RDY TIME OUT. You can usually recover by rebooting. SECTOR NOT FOUND There is a disk error on the server. Retry the operation. If the message appears again, check the server hardware. SEEK ERROR There is a disk error on the server. Retry the operation. If the message appears again, check the server hardware. SEE LOG FILE(S) The BACK_LOG file contains important information concerning the present operation. Check the backup logs. SHARE SERVER NOT RESPONDING or BACKUP IN PROGRESS When the backup command is given, nothing happens but a status check, but the "backup in progress" message is displayed. If you try to cancel the backup, the response "No backup in progress" is given. This is a known bug with CIOSYS that manifests itself during backup. CIOSYS disallows any new threads during the first three minutes after it is loaded. Backup will fail for all backups, restores and dir /f's for a few minutes after the LCD shows the amount of free memory. Always wait five minutes after boot before beginning the backup operation. SHARE SERVER NOT RESPONDING There is an unspecified problem with the share server. Make sure that the share server is operating and that there is no problem with the network in general. STRANGE FORMAT The beginning of the tape is not recognizable as a 3+Backup tape. Either erase the tape or insert a 3+Backup tape. SYNTAX ERROR A 3+Backup command contains improper syntax. Check for the correct command syntax. TAPE DRIVE ERROR; CONTROLLER BUSY There is a problem with the tape unit. First, retry the operation. If the problem occurs again, check the connection to and condition of the tape unit. TAPE DRIVE ERROR; DATA ERROR An unrecoverable data error has occurred and 3+Backup cannot read or write to the tape. Adjust the tension of the tape by erasing the tape twice. Try to use the tape again. If the error recurs, discard the tape. TAPE DRIVE ERROR; DRIVE FAULT The tape drive needs repair or replacement. TAPE DRIVE ERROR; DRIVE NOT ATTACHED 3+Backup did not detect the presence of the tape drive. If the tape drive is a separate unit, turn on the tape backup unit before starting the server. Check all cable connections and make sure you are using the correct version of TDRIVE.SYS or TAPE.SYS. TAPE DRIVE ERROR; END OF RECORDED DATA The end of the recorded data has been reached unexpectedly and 3+Backup cannot decipher the resulting tape format. There may be a problem with the last file on the tape. If the message occurs during a backup, redo the backup. If the message occurs during a restore, the last file restored may be incomplete. You may need to recreate the last file using an earlier backup tape. TAPE DRIVE ERROR; END OF TAPE REACHED The physical end of the tape has been reached unexpectedly and 3+Backup cannot decipher the resulting tape format. All information on the tape is intact and can be read. However, if this message occurs during a backup, redo the backup. If this message occurs during a restore, recreate the file using an earlier backup tape. All other files on the second tape are still accessible. TAPE DRIVER ERROR; INTERNAL ERROR A hardware error occurred that 3+Backup is not ready to handle. Retry the operation, then call 3Com Tech Support. TAPE DRIVE ERROR; MISCELLANEOUS 3+Backup has encountered an unexpected error condition. Retry the operation. If the error recurs, shut down and restart the server with the tape unit. TAPE DRIVE ERROR; NEW TAPE IN PLACE The tape cartridge has been changed since the last time 3+Backup read or wrote to the tape. Repeat the backup or restore operation. Do not remove or replace cartridges while either operation is in progress. TAPE DRIVE ERROR; NO TAPE IN PLACE There is no tape in the tape drive. Insert the appropriate tape and retry the operation. TAPE DRIVE ERROR; OPERATION TOOK TOO LONG The tape drive took longer than expected to complete a single command. The tape controller or drive may need repair. Try the operation again and restart the server if necessary. TAPE DRIVE ERROR; SCSI BUS ERROR The server is unable to communicate with the tape drive. Check the SCSI cabling and termination. TAPE DRIVE ERROR; SOFTWARE ERROR (message) 3+Backup is having difficulty communication with the other server software. Shut down the server and restart it. TAPE DRIVE ERROR: SOFTWARE ERROR (handle) The tape was in place but the door on the tape drive was not shut. This error can occur when identifying a tape from the 3BMEN menu or when trying to run a backup. If the error does not go away, reboot the server to re-initialize the tape unit. TAPE DRIVE ERROR; UNEXPECTED FILE MARK A file mark is present on the tape in a unusual place and 3+Backup cannot decipher the resulting tape format. Erase and re-record the tape. TAPE DRIVE ERROR; WRITE-PROTECTED TAPE The write-protect switch on the tape is in the Safe position and data cannot be written to the tape. Rotate the tape write- protect switch away from Safe. TAPE FULL The tape you want to use for a backup is full. Use a different tape that contains sufficient space to perform a backup. TAPE IS BLANK The tape in the tape drive contains no information. TAPETEST MESSAGE DISPLAY HANGS AT "Q" This error occurred in version 1.1.1. Use version 1.3.2 TAPETEST. THERE IS NO CURRENT OPERATION TO CANCEL You tried to cancel an operation but there was no operation in progress. UNKNOWN COMMAND (string) 3+Backup does not recognize the command you entered. Enter the proper command. UNKNOWN MEDIA TYPE There is a disk error on the server. Retry the operation, then check your server hardware. UNABLE TO BUILD DESTINATION PATH A destination path specified in the restore operation cannot be built. Enter a different destination path. UNABLE TO DETERMINE WHICH DRIVES TO ACCESS The server being backed up has failed to report which of its disks are networked. Shut down the server and restart it or check CMOS. UNABLE TO HANG UP ON FILE SERVER The virtual circuit between the backup server and the file server was not disconnected properly. Be alert for errors in the next backup. If any occur, restart both the backup server and the file server. Check for data corruption. UNABLE TO GET TAPE BUFFER FROM CIOSYS CIOSYS is not able to give the backup software a memory buffer. Reconfigure CIOSYS. UNABLE TO INTERPRET TAPE FORMAT 3+Backup does not recognize the tape. 3+Backup can read data only from tapes it has recorded. UNABLE TO WRITE FINAL TAPE BLOCK The final write operation of the backup failed. Use the tape directory selection or dir /f command to confirm that the backup tape and the tape drive are listed. Label the tape and watch for future errors on the same tape. Backup 1.3 can only be used by a network administrator or server user. UNEXPECTED FILE MARK A file mark was encountered on an alleged 3+Backup tape that should have contained data. This tape is not a 3+Backup tape. Insert a different tape or erase the current tape before using it. USER OPERATIONS NOT SUPPORTED IN 3+BACKUP A user attempted to use 3+Backup to back up a home directory. The network administrator must perform this operation. UNEXPECTED S/W INT NNnnnn:nnnn The server has received a spurious interrupt, where "NN" is the interrupt number. For software interrupts, "nnnn:nnnn" is the segment:offset address from which the interrupt has occurred. This message usually indicates a software error if it appears more than once. Enter 3Console mode and run CHKDSK on each partition. Sometimes this error requires reinstalling system software. WRITE PROTECTED The tape has the write-protect switch set to the Safe position. Insert a tape that can be written, or change the write-protect switch away from Safe. Or, you are trying to back up files onto a wrong size tape. For example, a 45 MB tape in a 150 MB tape unit could be read but not written to. If you try and write to this tape you will get the write protected error message. Use the correct size tapes. WRONG TAPE The tape does not contain the remaining portion of the data to be restored. Insert the tape containing the correct data. 3+BACKUP FAILURE Appears on the LCD of the server when rebooting the server after a power failure. It indicates data corruption as would occur if 3+Backup was in progress when the power failed. Re-install 3+Backup software. Or, parameters were changed on the server and there is not enough memory to load 3+Backup.