17.12.2012 Views

Iomega Backup (Ditto) Error Codes

Iomega Backup (Ditto) Error Codes

Iomega Backup (Ditto) Error Codes

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

ERROR CODE TYPE: FIX:<br />

2000 and 8000 range<br />

LIBRARIAN ERROR CODES DELETE LIBRARIAN<br />

FILES<br />

// LIBRARY ERROR CODES [2000-2099]<br />

2000 MSR_LIB_FATAL_FILE_ERROR<br />

2001 MSR_LIB_FATAL_ERROR<br />

2002 MSR_LIB_UNIQUE<br />

2003 MSR_LIB_RECORD_DELETED<br />

// LIBRARY ERROR CODES [8000-8100]<br />

8000 MSR_LIB_CLOSE_FILE<br />

8001 MSR_LIB_CREATE_FILE<br />

8002 MSR_LIB_LEN_FILE<br />

8003 MSR_LIB_LENSET_FILE<br />

8004 MSR_LIB_LOCK_FILE<br />

8005 MSR_LIB_OPEN_FILE<br />

8006 MSR_LIB_PERMISS_FILE<br />

8007 MSR_LIB_ACCESS_FILE<br />

8008 MSR_LIB_NUMFILES_FILE<br />

8009 MSR_LIB_FILEFIND_FILE<br />

8010 MSR_LIB_INSTANCE_FILE<br />

8011 MSR_LIB_READ_FILE<br />

8012 MSR_LIB_REMOVE_FILE<br />

8013 MSR_LIB_RENAME_FILE<br />

8014 MSR_LIB_UNLOCK_FILE<br />

8015 MSR_LIB_WRITE_FILE<br />

8016 MSR_LIB_DATA_FILE<br />

8017 MSR_LIB_FIELDNAME_FILE<br />

8018 MSR_LIB_FIELDTYPE_FILE<br />

8019 MSR_LIB_RECORDLEN_FILE<br />

8020 MSR_LIB_RECORDLEN_FILE<br />

8021 MSR_LIB_SEEK_FILE<br />

8022 MSR_LIB_ENTRY_FILE<br />

8023 MSR_LIB_INDEX_FILE<br />

8024 MSR_LIB_TAGNAME_FILE<br />

8025 MSR_LIB_UNIQUE_FILE<br />

8026 MSR_LIB_TAGINFO_FILE<br />

8027 MSR_LIB_COMMAEXPECTED_FILE<br />

8028 MSR_LIB_COMPLETE_FILE<br />

8029 MSR_LIB_DATANAME_FILE<br />

8030 MSR_LIB_LENGTHERR_FILE<br />

8031 MSR_LIB_NOTCONSTANT_FILE<br />

8032 MSR_LIB_NUMPARMS_FILE<br />

8033 MSR_LIB_OVERFLOW_FILE<br />

8034 MSR_LIB_RIGHTMISSING_FILE<br />

8035 MSR_LIB_TYPESUB_FILE<br />

8036 MSR_LIB_UNRECFUNCTION_FILE<br />

8037 MSR_LIB_UNRECOPERATOR_FILE<br />

8038 MSR_LIB_UNRECVALUE_FILE<br />

8039 MSR_LIB_UNTERMINATED_FILE<br />

8040 MSR_LIB_TAGEXPR_FILE<br />

8041 MSR_LIB_OPT_FILE


8042 MSR_LIB_OPTSUSPEND_FILE<br />

8043 MSR_LIB_OPTFLUSH_FILE<br />

8044 MSR_LIB_LOOKUPERR_FILE<br />

8045 MSR_LIB_RELATE_FILE<br />

8046 MSR_LIB_RELATEREFER_FILE<br />

8047 MSR_LIB_REPORT_FILE<br />

8048 MSR_LIB_STYLECREATE_FILE<br />

8049 MSR_LIB_STYLESELECT_FILE<br />

8050 MSR_LIB_STYLEINDEX_FILE<br />

8051 MSR_LIB_AREACREATE_FILE<br />

8052 MSR_LIB_GROUPCREATE_FILE<br />

8053 MSR_LIB_GROUPEXPR_FILE<br />

8054 MSR_LIB_TOTALCREATE_FILE<br />

8055 MSR_LIB_OBJCREATE_FILE<br />

8056 MSR_LIB_REPWIN_FILE<br />

8057 MSR_LIB_REPOUT_FILE<br />

8058 MSR_LIB_REPSAVE_FILE<br />

8059 MSR_LIB_REPRET_FILE<br />

8060 MSR_LIB_REPDATA_FILE<br />

8061 MSR_LIB_INFO_FILE<br />

8062 MSR_LIB_MEMORY_FILE<br />

8063 MSR_LIB_PARM_FILE<br />

8064 MSR_LIB_PARM_NULL_FILE<br />

8065 MSR_LIB_DEMO_FILE<br />

8066 MSR_LIB_RESULT_FILE<br />

8067 MSR_LIB_VERIFY_FILE<br />

8068 MSR_LIB_STRUCT_FILE<br />

8069 MSR_LIB_NOTINDEX_FILE<br />

8070 MSR_LIB_NOTMEMO_FILE<br />

8071 MSR_LIB_NOTRENAME_FILE<br />

8072 MSR_LIB_NOTWRITE_FILE<br />

8073 MSR_LIB_NOTCLIPPER_FILE<br />

8074 MSR_LIB_NOTLOCK_FILE<br />

8075 MSR_LIB_NOTSUPPORTED_FILE<br />

8076 MSR_LIB_VERSION_FILE<br />

8077 MSR_LIB_MEMOCORRUPT_FILE<br />

8078 MSR_LIB_MEMOCREATE_FILE<br />

8079 MSR_LIB_TRANSVIOLATION_FILE<br />

8080 MSR_LIB_TRANS_FILE<br />

8081 MSR_LIB_ROLLBACK_FILE<br />

8082 MSR_LIB_COMMIT_FILE<br />

8083 MSR_LIB_TRANSAPPEND_FILE<br />

8084 MSR_LIB_CORRUPT_FILE<br />

8085 MSR_LIB_CONNECTION_FILE<br />

8086 MSR_LIB_SOCKET_FILE<br />

8087 MSR_LIB_NET_FILE<br />

8088 MSR_LIB_LOADLIB_FILE<br />

8089 MSR_LIB_TIMEOUT_FILE<br />

8090 MSR_LIB_MESSAGE_FILE<br />

8091 MSR_LIB_PACKETLEN_FILE<br />

8092 MSR_LIB_PACKET_FILE<br />

8093 MSR_LIB_MAX_FILE<br />

8094 MSR_LIB_CODEBASE_FILE<br />

8095 MSR_LIB_NAME_FILE<br />

8096 MSR_LIB_AUTHORIZE_FILE<br />

8097 MSR_LIB_SERVER_FILE


8098 MSR_LIB_CONFIG_FILE<br />

8099 MSR_LIB_CAT_FILE<br />

8100 MSR_LIB_OTHER<br />

<strong>Error</strong> Code Type: Fix:<br />

Hardware <strong>Error</strong> codes Use this for reference only<br />

5000 range Hardware caused problem;<br />

Use normal Hardware troubleshooting<br />

// 5001 - 5099 are returned from the Tape Drive Itself<br />

5001 FTDVR_QIC117DRIVENOTREADY The tape drive received a command that is illegal until the<br />

drive ready bit is asserted. Power off the tape drive, close the application and attempt the operation<br />

again.<br />

5002 FTDVR_QIC117NOCART There is no cartridge present in the tape drive. Insert a cartridge into<br />

the drive mechanism.<br />

5003 FTDVR_QIC117MOTORSPEEDERROR The tape cartridge is not moving freely. Ensure that the<br />

cartridge wheel turns freely and the tape moves smoothly.<br />

5004 FTDVR_QIC117MOTORSPEEDFAULT The tape cartridge is jammed. Ensure that the cartridge<br />

wheel turns freely and the tape moves smoothly.<br />

5005 FTDVR_QIC117CARTWRITEPROTECT A command was received that requires the cartridge to<br />

not be write protected. Make sure the write protect tab is in the non-protected position.<br />

5006 FTDVR_QIC117RESERVEDERRORCODE The tape drive has encountered a fatal error<br />

condition. It will no longer respond to commands until powered off. Reboot the system.<br />

5007 FTDVR_QIC117ILLEGALTRACKFORSEEK<br />

5008 FTDVR_QIC117ILLEGALCOMMANDINRPT The tape drive received a command that is illegal<br />

until the report command has been cleared. Retry the operation. If this condition persists, reboot<br />

and retry the operation.<br />

5010 FTDVR_QIC117BROKENTAPE The hole sensors on the tape drive have detected that the tape is<br />

broken. Use another tape.<br />

5011 FTDVR_QIC117READGAINERROR The tape drive cannot detect the proper magnetic<br />

transitions on the tape. Reformat or use another tape.<br />

5013 FTDVR_QIC117NEWCARTPENDING The tape drive received a command that is illegal until<br />

the new cartridge pending bit has been cleared. Close the application and attempt the operation<br />

again.<br />

5014 FTDVR_QIC117ILLEGALCMDPRIMARY The tape drive received a command that is illegal in<br />

primary mode. Reboot and attempt the operation again.<br />

5015 FTDVR_QIC117ILLEGALCMDFORMAT The tape drive received a command that is illegal in<br />

format mode. Reboot and attempt the operation again.<br />

5016 FTDVR_QIC117ILLEGALCMDVERIFY The tape drive received a command that is illegal in<br />

verify mode. Reboot and attempt the operation again.<br />

5017 FTDVR_QIC117NOTLOGICALBOT A command was received that requires the tape to be<br />

rewound. Reboot and retry the operation.<br />

5018 FTDVR_QIC117LOGICALEOT The tape reached logical end of tape before all segments were<br />

generated. Power off the system and reattempt the operation.<br />

5019 FTDVR_QIC117CARTNOTREFERENCED The tape drive was unable to reference the tape<br />

cartridge. Reformat the tape or use another cartridge.<br />

5020 FTDVR_QIC117SELFDIAGFAILED The tape drive was unable to perform a self-diagnostic or<br />

the diagnostic failed. NOTE: The tape drive must be powered off before it can be used again.<br />

There is no software recovery for this error.<br />

5021 FTDVR_QIC117EEPROMNOTINIT The EEPROM on the tape drive is being initialized.


5022 FTDVR_QIC117EEPROMCORRUPTED The tape drive was has detected that the EEPROM is<br />

corrupted or there was a fatal hardware error.<br />

5023 FTDVR_QIC117MOTIONTIMEOUTERROR The tape drive encountered a motion time out<br />

error.<br />

5024 FTDVR_QIC117DATASEGMENTTOOLONG The encountered a data segment that was too<br />

long.<br />

5025 FTDVR_QIC117OBS This is an obsolete error code.<br />

5026 FTDVR_QIC117POWERONRESET The tape drive reports that a power on reset has occurred.<br />

5027 FTDVR_QIC117SOFTWARERESET The tape drive reports that it has been reset by software.<br />

5028 FTDVR_QIC117DIAGNOSTICMODE1 The tape drive encountered a diagnostic mode 1 error.<br />

5029 FTDVR_QIC117DIAGNOSTICMODE2 The tape drive encountered a diagnostic mode 2 error.<br />

5030 FTDVR_QIC117NONINTPROCESS A command was received while the tape drive was<br />

executing a non-interruptible process. Power off the system and retry the operation.<br />

5031 FTDVR_QIC117RATESELECTIONERROR A tape and drive combination exists that does not<br />

support the selected transfer rate. Make sure that the tape is compatible with the drive for the<br />

requested operation. This usually occurs when attempting to write to a QIC-80 tape in a <strong>Ditto</strong><br />

3200 drive.<br />

5032 FTDVR_QIC117ILLEGALSEEKINHSMODE The tape drive reports that it received a command<br />

that is illegal when the drive is in high-speed mode.<br />

5033 FTDVR_QIC117ILLEGALSEEKSEGMENT The tape drive was programmed with an illegal<br />

value for a segment seek command.<br />

5034 FTDVR_QIC117INVALIDMEDIA The tape drive reports that it has determined that the media is<br />

invalid.<br />

5035 FTDVR_QIC117HEADPOSFAILURE The tape drive encountered a head positioning failure.<br />

5036 FTDVR_QIC117WRITEREFFAILURE The drive failed to write reference bursts. Retry the<br />

operation.<br />

5037 FTDVR_QIC117PROMCODEMISSING The tape drive cannot download the prom code.<br />

5038 FTDVR_QIC117INVALIDFORMAT The tape drive reports that the tape format is invalid.<br />

5039 FTDVR_QIC117EOTBOTSYSTEMFAILURE The tape drive reports a failure with the<br />

Beginning/Ending of tape system.<br />

5040 FTDVR_QIC117PROMACHECKSUM The tape drive reports that the checksum failed on Prom<br />

A.<br />

5041 FTDVR_QIC117DRIVEWAKUPRESET The tape drive reports that a drive wakeup reset has<br />

occurred.<br />

5042 FTDVR_QIC117PROMBCHECKSUM The tape drive reports that the checksum failed on Prom<br />

B.<br />

5043 FTDVR_QIC117ILLEGALENTRYFORMAT The tape drive reports that it was forced into<br />

format mode illegally.<br />

5050 FTDVR_QIC117TRAYJAMMED The tape tray loader on the tape drive is jammed.<br />

5051 FTDVR_QIC117ILLEGALSEEKPARTITION The tape drive reports that it was programmed to<br />

seek to an illegal partiiton.<br />

Driver Generated <strong>Error</strong> <strong>Codes</strong> (5100-5199)<br />

5105 FTDVR_OFFTRACK The tape drive read a sector id that does not belong on the current track.<br />

5106 FTDVR_UNINITIALIZED An application program sent the driver an operation command prior to<br />

sending the initialization command.<br />

5107 FTDVR_FORMATTINGUNSUPPORTED A format command was sent to the driver, but the<br />

attached tape drive is not a formatting model.<br />

5108 FTDVR_INVALIDWRITEHEADER 1. An application attempted to write data to the header or<br />

duplicate header. 2. The tape has changed since building the header to be written. 3. The active<br />

partition has changed since building the header to be written.<br />

5109 FTDVR_INVALIDIOCTL An application sent the driver an invalid command.<br />

5110 FTDVR_DEFECTIVETAPE 1. There are more entries in the bad sector map than will fit in 1<br />

segment. 2. An on-the-fly markout passed the last data segment. 3. The bad sector map is out of<br />

order or has duplicate entries.


5111 FTDVR_INCOMPATABLERATES The tape, drive, controller, and operation do not share a data<br />

rate that is compatible.<br />

5112 FTDVR_INVALIDDMACOMMAND An invalid command was passed to the DMA controller<br />

internal to the program. This is error internal to the driver's logic and should never occur.<br />

5113 FTDVR_HEADERNOTREAD 1. A program requested information about an unmounted tape. 2.<br />

A program requested the header of an unmounted tape. 3. A program attempted to rename an<br />

unmounted tape. 4. A program attempted to read a segment from an unmounted tape. 5. A<br />

program attempted to change partitions on an unmounted tape.<br />

5114 FTDVR_NODATABUFFER A program sent a command that requires the program to supply a<br />

buffer of sufficient size to the driver. This command failed because the buffer was either not<br />

supplied or not large enough for the data.<br />

5115 FTDVR_UNCORRECTABLE The driver read a segment that had more than three ( 3 ) sectors<br />

bad. The Reed-Solomon error correction code is unable to correct the segment due to the number<br />

of sectors that are unreadable.<br />

5116 FTDVR_ABORT The abort flag has been set.<br />

5117 FTDVR_REGISTRY_ERROR Failed to open a registry key or retrieve a value that the driver<br />

needed.<br />

5118 FTDVR_INVALID_PARAMATER The flags passed into the function that configures the parallel<br />

port chipset are invalid. This is an internal logic error.<br />

5141 FTDVR_ERROR 1. The parallel port mode requested is unavailable. 2. A fatal error occurred<br />

during parallel port configuration 3. The Microsolutions parallel port code returned and unknown<br />

error. 4. When reading a byte from the FDC, RQM or DIO failed to assert 5. When writing a byte<br />

to the FDC, RQM failed to assert<br />

5142 FTDVR_UNREADABLE This is an obsolete error code.<br />

5143 FTDVR_CORRECTED This is used for internal statistics and should never be seen by the user. It<br />

means that the Reed-Solomon algorithm was invoked successfully.<br />

5144 FTDVR_COMMANDTIMEOUT 1. Report command failed more than 50 times while waiting<br />

drive ready. 2. An interrupt did not occur within the specified interval. 3. A calibrate tape length<br />

command took too much time to complete. 4. We failed to write a segment within 16 segments of<br />

its intended segment 5. We failed to get an interrupt while attempting to read a segment 6. We<br />

failed to get an interrupt while attempting to write deleted data.<br />

5145 FTDVR_CRC 1. The CRC calculation failed for the parallel port transfer 2. The FDC detected\ a<br />

CRC in the ID field of a sector.<br />

5146 FTDVR_NOTREADY This is an obsolete error code.<br />

5147 FTDVR_SYNCERROR This is an obsolete error code.<br />

5148 FTDVR_EQUIPMENTCHECK This is an obsolete error code.<br />

5149 FTDVR_PASTLASTTRACK Failed to receive TC at the end of a read data or write data<br />

command.<br />

5150 FTDVR_DATAERROR The FDC detected a CRC in the data field of a sector.<br />

5151 FTDVR_OVERRUN FDC did not receive CPU or DMA service in the required time interval,<br />

resulting in a FIFO overrun or underrun.<br />

5152 FTDVR_NODATA 1. The FDC could not find the requested sector on a read data command. 2.<br />

The FDC could not read the ID field without an error.<br />

5153 FTDVR_WRITEPROTECT The WP pin on the FDC was asserted during execution of a write<br />

data command<br />

5154 FTDVR_MISSINGID 1. Could not seek to a specified segment within 3 attempts. 2. The FDC did<br />

not encounter and address mark after 2 index pulses 3. The FDC cannot find a data address mark<br />

for the specified sector.<br />

5155 FTDVR_CONTROLMARK 1. On a read data command, the FDC encountered a deleted address<br />

mark. 2. On a read deleted data command, the FDC encountered an address mark.<br />

5156 FTDVR_WRONGCYLINDER The track address in the sector ID field is different from the track<br />

address maintained in the FDC.<br />

5157 FTDVR_BADCYLINDER The track address from the sector ID field is different from the track<br />

address maintained inside the FDC, and is equal to 0xFFh which indicates a bad track with a hard<br />

error according to the IBM soft-sectored format.<br />

5158 FTDVR_REQUESTED Internal status - will not be presented to the user.


5160 FTDVR_INVALIDCOMMAND IC indicates an invalid command was received.<br />

5161 FTDVR_ABNORMTERMINATE IC indicates a command terminated abnormally.<br />

5162 FTDVR_NOTAPE A report drive status command was issued to the tape drive and the response<br />

indicated that the drive was ready, but there was no cartridge present.<br />

5163 FTDVR_UNFORMATTED A report drive status command was issued to the tape drive and the<br />

response indicated that the drive was ready and a cartridge was present, but the cartridge was not<br />

referenced.<br />

5164 FTDVR_ENDOFTAPE 1. During an on-the-fly rewrite, the new segment exceeded the LLDS. 2.<br />

An program requested that a segment be written past the LLDS 3. Internal to the program, a<br />

CHRN address was computed past the LLDS.<br />

5165 FTDVR_INVALIDFORMAT 1. The drive contains a non-<strong>Iomega</strong> tape formatted to the <strong>Iomega</strong><br />

format. 2. There is a TR-1 tape in a <strong>Ditto</strong> Max drive 3. The header values for segments per track or<br />

tracks per cartridge are zero. 4. The user is attempting to access a 10GB tape with non-pro<br />

software.<br />

5166 FTDVR_INVALIDDMA This is an obsolete error code.<br />

5167 FTDVR_INVALIDIRQ The driver has been configured with an IRQ setting of zero<br />

5168 FTDVR_INVALIDBASEADDR 1. When reading the MSR, 0xFFh, an impossible response, is<br />

read. 2. A parallel port chipset cannot be detected at the specified port address. 3. A parallel port<br />

base address has not been specified.<br />

5169 FTDVR_MEMALLOCFAILURE 1. Not enough physical memory could be allocated for DMA<br />

transfers. 2. NT only - Not enough memory could be allocated for the resource list.<br />

5170 FTDVR_IRQINUSE This is an obsolete error code.<br />

5171 FTDVR_BADREPORT 1. After a report command, the drive did not acknowledge. 2. The last bit<br />

of the report sequence was not a 1<br />

5172 FTDVR_BADINFDC TK0 status could not be read after issuing a sense drive status command to<br />

the FDC.<br />

5173 FTDVR_BADOUTFDC 1. No interrupt was generated after sending pulses to the drive. 2. An<br />

attempt to send pulses to the drive failed. 3. A configure command was rejected by the Floppy<br />

Disk Controller. 4. No interrupt was generated after issuing a recalibrate command.<br />

5174 FTDVR_BADINTERRUPT This is an obsolete error code.<br />

5175 FTDVR_FDCBUSY 1. While writing to the FDC, the MSR indicates data needs to be read. 2.<br />

While reading from the FDC, the MSR fails to indicate ready status.<br />

5176 FTDVR_UNCORRECTED The Reed-Solomon error correction algorithm was invoked, but failed<br />

to correct the data.<br />

5177 FTDVR_UNSUPPORTED A parallel port tape drive is attached with an unsupported (old)<br />

parallel port interface ASIC.<br />

5178 FTDVR_INVALIDMEDIA On a reformat, the cartridge header contains an invalid specification<br />

for the number of tracks per cartridge.<br />

5179 FTDVR_TRACEPOINTERROR1 This is an obsolete error code.<br />

5180 FTDVR_TRACEPOINTERROR2 This is an obsolete error code.<br />

5181 FTDVR_TRACEPOINTERROR This is an obsolete error code.<br />

5182 FTDVR_EMPTYSEGMENT A segment is marked as containing 3 sectors or less, thus not<br />

containing enough space to hold the error correction code..<br />

5183 FTDVR_MISSINGDATA The FDC was unable to detect a data address mark.<br />

5184 FTDVR_RESOURCE_CONFLICT NT only - The I/O manager will not allow use of the specified<br />

resources because there is a conflict.<br />

5185 FTDVR_ECC An error was detected in the data using the Reed-Solomon algorithm<br />

5186 FTDVR_ERRORLOGOVERRUN A query error log message was sent to the driver, and the<br />

driver is reporting back that the log is not complete due to an overrun.<br />

5187 FTDVR_ASICLOCKED The parallel port ASIC mode has been locked by the BIOS and can't be<br />

changed.<br />

5188 FTDVR_CORRUPTEDBSM The tape's Bad Sector Map is corrupt.<br />

5189 FTDVR_BOGUSNODATA This is an internal status for tracking statistics and will not be seen by<br />

the user.<br />

5190 FTDVR_DRIVERBUSY This is an obsolete error code.


5191 FTDVR_COMMANDFAILED Status indicates success on a change partition command, but the<br />

partition failed to change.<br />

5192 FTDVR_CABLEREVERSED Due to the reporting of an invalid vendor id with all commands<br />

succeeding, the ribbon cable is determined to be attached backwards.<br />

5193 FTDVR_NOTAPEDRIVE This is an obsolete error code.<br />

5194 FTDVR_MODELOCKED The parallel port ASIC mode has been locked by the BIOS and can't be<br />

changed.<br />

5195 FTDVR_POWEROFF The parallel port ASIC's power is turned off.<br />

5196 FTDVR_DISABLED The parallel port ASIC is disabled.<br />

5197 FTDVR_COMMFAILURE The parallel port ASIC has been detected, but there was a<br />

communication failure when attempting to access the parallel port device.<br />

5201 MSR_OUTOFDRIVERMEMORY<br />

5202 MSR_ERROR_IOCTLFAILED<br />

5203 MSR_ERROR_DRIVERNOTLOADED<br />

ERROR CODE TYPE: FIX:<br />

Generic Operating System <strong>Error</strong> <strong>Codes</strong> Exit program, Close all Open programs<br />

100, 500, 600, 700, 800,900 & 1000 Range Run a Scan disk and restart.<br />

Uninstall and reinstall the software.<br />

// Generic error codes [100-499]<br />

100 MSR_NULL_POINTER // A function has encountered a null pointer<br />

101 MSR_MEMORY_ERROR // Generic memory error encountered<br />

102 MSR_INVALID_PARAMETER // A function has been passed an invalid parameter<br />

103 MSR_ITEM_NOT_FOUND // The target item has not been found in some list or tree<br />

104 MSR_NULL_HANDLE // Invalid handle has been encountered<br />

105 MSR_NO_MATCH // A search for an item has failed<br />

106 MSR_BUFFER_OVERFLOW // A function has exceeded the bounds of a buffer<br />

107 MSR_MAXIMUM_EXCEEDED<br />

108 MSR_RETURN_UNINIT // A function has exited without setting the return code<br />

109 MSR_OUT_OF_MEMORY<br />

110 MSR_OPERATION_ABORT<br />

111 MSR_NOT_OVERLOADED // A virtual function has not been properly overloaded<br />

// MSRU64 error codes [500-599]<br />

500 MSR_MSRU64_OVERFLOW // A 64 bit number<br />

501 MSR_MSRU64_UNDERFLOW // has not been<br />

502 MSR_MSRU64_DIVIDE_BY_ZERO // handled correctly<br />

// MSRSEM error codes [600-699]<br />

600 MSR_CANT_CREATE_MUX // The operating system is out of resources<br />

601 MSR_CANT_CREATE_EVENT // The operating system is out of resources<br />

602 MSR_SEM_SET_ERROR // A fatal error has occurred in the OS<br />

603 MSR_SEM_RESET_ERROR // A fatal error has occurred in the OS<br />

604 MSR_SEM_WAIT_ERROR // A fatal error has occurred in the OS


605 MSR_SEM_REQUEST_ERROR // The operating system is out of resources<br />

606 MSR_SEM_RELEASE_ERROR // The operating system is out of resources<br />

// The following are conditions and are not necessarily fatal errors//<br />

#ifdef MSR_SYSTEM_WIN32<br />

607 #define MSR_SEM_WAIT_ABANDONED<br />

#endif<br />

608 #define MSR_SEM_WAIT_TIMEOUT<br />

// MSRTHD error codes [700-799]<br />

700 MSR_CANT_CREATE_THREAD // The OS could not create a thread. The system is out<br />

of resources<br />

701 MSR_CANT_SUSPEND_THREAD // The Task Scheduler is not functioning properly<br />

702 MSR_CANT_RESUME_THREAD // The Task Scheduler is not funcitoning properly<br />

703 MSR_CANT_SET_THREAD_PRIORITY // The Task Scheduler is not functioning properly<br />

704 MSR_THREAD_WAIT_ERROR<br />

705 MSR_THREAD_WAIT_ABANDONED // The requested resource was in use by an aborted<br />

thread<br />

706 MSR_THREAD_WAIT_TIMEOUT // The function has timed out while waiting for a<br />

thread<br />

707 MSR_THREAD_THREW // A 95 object has been thrown<br />

// TreeMgr error codes [800-899]<br />

800 MSR_INVALID_SIBLING_NODE // The file tree contains an invalid node<br />

801 MSR_INVALID_PATH // The file tree contains an invalid path<br />

802 MSR_INVALID_FLAG // The file tree contains an invalid flag<br />

803 MSR_CORRUPT_TREE // The file tree is corrupt<br />

804 MSR_TOO_FEW_ROOT_PATHS // The file tree does not contain enough root paths<br />

805 MSR_TREEMGR_SEM_CREATE_FAILED // The system is out of resources and cannot<br />

create a semaphore<br />

// LFMgr error codes [900-999]<br />

900 MSR_FILE_NOT_OPEN // The backup engine is trying to read data from a closed file<br />

901 MSR_INVALID_ORDER // The qic-113 tree is in an invalid order<br />

902 MSR_INVALID_ACTION // Cannot backup security info on a 95 file<br />

903 MSR_BUFFER_TO_SMALL // The backup engine is trying to read from and invalid buffer<br />

904 MSR_NO_MORE_DATA // The engine is tried to read past end of file<br />

905 MSR_NOT_FILE_DATA // The engine has tried to write security information to a data<br />

field<br />

906 MSR_NO_MORE_XOS // All XOS info has been processed. The engine is trying to<br />

read more info<br />

907 MSR_OS_NOT_SUPPORTED // The engine is trying to access invalid XOS data.<br />

908 MSR_INVALID_LF_TYPE // The engine is trying to instatiate an invalid Logical type.<br />

909 MSR_THRESHOLD_REACHED // The End of tape has been reached prematurely<br />

910 MSR_COMPR_ERROR // Compression failed<br />

911 MSR_INVALID_HANDLE // An invalid file handle has been encountered<br />

912 MSR_END_OF_TAPE // Premature EOT<br />

913 MSR_BAD_OFFSET // Invalid data was read from the tape


914 MSR_LF_ABORTED // The user has aborted an operation<br />

915 MSR_FILE_FOUND // LF is refreshing information about a file<br />

916 MSR_SKIP_FILE // The engine was told to skip a file during an overwrite<br />

operation<br />

917 MSR_FATAL // An undiagnosable error has occurred<br />

918 MSR_LFMGR_NOT_PROCESSED // A file node was not processed by LF<br />

919 MSR_LF_REWRITE<br />

920 MSR_DRIVE_NOT_READY // Drive not ready for transfer, no CD in drive etc.<br />

// LFWin95 error codes [1000-1099]<br />

1000 MSR_DEADLOCK // File access or file lock will cause deadlock<br />

1001 MSR_FILE_NOT_CREATED<br />

1002 MSR_NO_MORE_SEARCH_HANDLES // Os low on resources, try closing other programs<br />

1003 MSR_LOCK_FAILED // Could not lock the file<br />

1004 MSR_FILE_ACCESS_DENIED // File access denied by os.<br />

1006 MSR_FILE_LOCKED // File locked by another process<br />

1007 MSR_FILE_EXISTS<br />

1008 MSR_NO_FILESYS_SPACE // Dest hard drive full during restore<br />

1009 MSR_FILE_NOT_FOUND<br />

1010 MSR_OS_ERROR // Unknown operating system error occurred<br />

ERROR CODE TYPE: FIX:<br />

Read/Write <strong>Error</strong>s Read <strong>Error</strong> description and Troubleshoot Hardware<br />

1100 – 1300 Range<br />

// LFQ113 error codes [1100-1199]<br />

1100 MSR_INVALID_DIR_ENTRY // Invalid data was read from the file tree section on the tape.<br />

1101 MSR_INVALID_ID // An invalid directory id was read from tape.<br />

1102 MSR_NOT_LAST_TAPE // Tape in drive is not last tape in set.<br />

// LFQ80 error codes [1200-1299]<br />

1200 MSR_NOT_FIRST_TAPE // Tape in drive is not first tape in set.<br />

// MSRLIST error codes [1300-1399] (short explanation follows each code)<br />

1300 MSR_LIST_EMPTY // User of MSRLIST called a Get??? or Delete??? method on<br />

an empty list. [This code is thrown and is fatal.]<br />

1301 MSR_NULL_LIST_OBJECT // Object data element T* TData of MSRLISTNODE is a<br />

NULL pointer. [Corrupt list or error in MSRLIST logic. // This code is thrown and is fatal.]<br />

1302 MSR_LIST_INDEX_OUT_OF_RANGE // User of MSRLIST called a Get??? or Delete???<br />

method on a nonexistant. [list item (item 5 of 2 element list for example). // This code is thrown<br />

and is fatal.]


ERROR CODE TYPE: FIX:<br />

Engine <strong>Error</strong> <strong>Codes</strong> Uninstall and Reinstall the Software<br />

Range: 1400 - 1599<br />

// Engine error codes [1400-1599]<br />

// addrstk error codes [1400-1409]<br />

1400 MSR_STACK_FULL<br />

1401 MSR_STACK_EMPTY<br />

// engq error codes [1410-1419]<br />

1410 MSR_ENGINEQ_FULL<br />

1411 MSR_ENGINEQ_EMPTY<br />

1412 MSR_ENGINEQ_ABORT<br />

// SrcObj main loop errors [1420-1429]<br />

1420 MSR_SRCOBJ_ABORTED<br />

1421 MSR_SRCOBJ_FATAL<br />

// DestObj main loop errors [1430-1439]<br />

1430 MSR_DESTOBJ_ABORTED<br />

1431 MSR_DESTOBJ_FATAL<br />

// CompObj main loop errors [1440-1449]<br />

1440 MSR_COMPOBJ_ABORTED<br />

1441 MSR_COMPOBJ_FATAL<br />

// Engine error codes [1450-1469]<br />

1450 MSR_ENGINE_FATAL<br />

1451 MSR_ENGINE_ABORTED<br />

1452 MSR_ENGINE_SKIP<br />

1453 MSR_ENGINE_PEOF<br />

ERROR CODE TYPE: FIX:<br />

Specific Device <strong>Error</strong> Use error code for reference<br />

Range 1600 – 1800 Troubleshoot the device hardware accordingly<br />

// Device error codes [1600-1699]<br />

1600 MSR_OPEN_FAILED // Couldn't open a device.<br />

1601 MSR_CLOSE_FAILED // Couldn't close a device.


1602 MSR_ADDVOL_TAPE_FULL // VolMgrAddVolume() determined that the volume passed<br />

into VolMgrAddVolume cannot fit on the device passed into VolMgrAddVolume().<br />

1610 MSR_READ_AT_END_OF_TAPE A read was attempted, and there are no more segments.<br />

1611 MSR_READ_AT_THRESHOLD_REACHED A read was attempted at the threshold.<br />

1612 MSR_WRITE_AT_END_OF_TAPE A write was attempted, and there are<br />

1613 MSR_WRITE_AT_THRESHOLD_REACHED A write was attempted at the threshold. No more<br />

segments.<br />

1615 MSR_WRITE_FAILED An fwrite() failed while writing in Write() on an image file.<br />

1621 MSR_NO_MORE_VOLUMES This error code is returned from GetVolEntry() If the caller has<br />

attempted to read a volume number greater than the possible number of volume table entries. This<br />

error is used primarily internally to DEVIMG(), but could propagate up to the user if the device<br />

logic is faulty in such a way that some function tries to read a volume table entry that is greater<br />

than the maximum number of entries.<br />

1622 MSR_VOLUME_TABLE_FULL This error is similar to the previous, except that this error is<br />

NOT internal, and is designed to be sent to the user. This error is returned by<br />

DEVICE::AddVolume() if there is no more space in the volume table for valid entries.<br />

1625 MSR_RELEASE_BAD_BUFFER A function passed to DEVIMG::Release() was not the pointer<br />

returned by the latest DEVIMG::Read() call.<br />

1629 MSR_BAD_MEDIA The media is unusable due to insufficient free space or invalid header data.<br />

1630 MSR_WAIT_TIMEOUT // Timeout waiting on tape drive to stop.<br />

1631 MSR_UNFORMATTED<br />

1632 MSR_UNSUPPORTED_FORMAT<br />

1633 MSR_DEVICE_CLOSE_FAILED<br />

1634 MSR_DEVICE_NOT_OPEN<br />

1635 MSR_MEDIA_NOT_OPEN<br />

1636 MSR_ERROR_UNWIND<br />

1637 MSR_MAXIMUM_BAD_SECTORS<br />

1638 MSR_ZERO_VALUE<br />

1639 MSR_READ_FAILED // devqimg fread failed<br />

1640 MSR_FORMAT_MEDIA_FAILED // devqimg format failed<br />

1641 MSR_SPAN // Span to another media<br />

1642 MSR_SPAN_RENAME // Span rename tape during writing<br />

1643 MSR_SPAN_VOLUME_EXISTS // Span volume we're backing up is already<br />

on this tape<br />

1644 MSR_SPAN_VOLUME_MISSING // Span volume we're reading is not on this<br />

tape<br />

1645 MSR_SPAN_FORMAT // Span check for format (y/n)<br />

1646 MSR_SPAN_ERASE // Span check for erase (y/n)<br />

1647 MSR_SPAN_CHECK // Span check with GUI for valid media<br />

1648 MSR_SPAN_CONTINUE // Span will continue to the indicated media<br />

1649 MSR_SPAN_REFORMAT // Span check for reformat (y/n)<br />

1650 MSR_SPAN_MEDIA // Span to a specific media<br />

1651 MSR_SPAN_SETARRAYS // Span to set the arrays<br />

1652 MSR_SPAN_REMOVE // Remove the current media<br />

1653 MSR_SPAN_TAPEFULL // Current tape is full


1654 MSR_DEVQRMV_NOTREADY // Zip or Jaz not ready, no disk or in sleep<br />

mode<br />

1655 MSR_DEVQRMV_WRITEPROTECT // Zip or Jaz has tools software protect on.<br />

// MSRIAO error codes [1800-1899]<br />

1800 MSR_IAO_INVALID_ACTION // Action was not backup, compare, restore.<br />

1801 MSR_IAO_ACTION_NOT_SET // Currently not used<br />

1802 MSR_IAO_VOLUME_NOT_FOUND // Needed volume is not on tape currently in<br />

drive<br />

1803 MSR_IAO_INCORRECT_TAPE // Needed tape not given by user when asked<br />

1804 MSR_IAO_INCORRECT_PASSWORD // Password from user did not match volume<br />

password<br />

1805 MSR_IAO_CLEAR_ARCHIVE_FAILED // Call to clear the archive bit failed<br />

ERROR CODE TYPE: FIX:<br />

Unknown errors Uninstall and Reinstall Software<br />

Range: 2200 - 7000<br />

// Msrwin and Msrstruct error codes [2200-2299]<br />

2200 MSR_PARM_OUT_OF_RANGE<br />

2201 MSR_NO_FILES<br />

2202 MSR_MEM_ERROR<br />

2203 MSR_INVALID_PARM<br />

// Recover Diskette Creation Utility error codes [6000-6099]<br />

6000 MSR_ZIP_FILE_OPEN_FAILED In the DISK device, if the newly created zip file cannot be<br />

opened, this error is returned.<br />

// Action server error codes [7000-7300]<br />

7000 IOMG_ERROR_DUPLICATE<br />

7007 IOMG_FATAL_ERROR<br />

7008 IOMG_PASSWORD_PROMPT<br />

7009 IOMG_NORENAMESPANNING<br />

7010 IOMG_NOCONFIGURATION<br />

ERROR CODE TYPE: FIX:<br />

User-Interface <strong>Error</strong> <strong>Codes</strong> Read the Description for error<br />

Range: 9000 The error will describe the problem<br />

There are no specific fixes<br />

// USER-INTERFACE ERROR CODES [9000-9399]


9000 MSR_UI_BAD_PARAMETER could not parse command line or invalid option combination<br />

9001 MSR_UI_BAD_FILE_SELECTION no files were selected for the operation<br />

9002 MSR_UI_OP_NOT_STARTED operation did not start, and no other return code was set<br />

9003 MSR_UI_VOL_NOT_FOUND could not find the specified volume<br />

9004 MSR_UI_FORMAT_NOT_SUPPORTED cannot format current media<br />

9005 MSR_UI_FATAL_ERROR internal GUI problem, probably couldn't initialize app<br />

9006 MSR_UI_FILE_NOT_FOUND couldn't find FSS file specified<br />

9007 MSR_UI_NO_DEVICE no device was configured in registry or specified on cmd line<br />

9009 MSR_UI_NOT_FIRST_INSTANCE "<strong>Ditto</strong> Tools is already running"<br />

9010 MSR_UI_USER_ABORT the user cancelled the operation<br />

ERROR CODE TYPE: FIX:<br />

Unknown caused errors Uninstall and Reinstall Software<br />

Range: 9400<br />

// FatHack <strong>Error</strong>s [9400-9500]<br />

9400 MSR_FATHACK_LOAD_BOOT_FAILED // Fathack was unable to locate the boot<br />

sector, disk may not be formatted with windows95<br />

9401 MSR_FATHACK_MEMORY_ERROR // Fathack ran out of conventional memory<br />

9402 MSR_FATHACK_READ_FAILED // Interupt fail to read disk<br />

9403 MSR_FATHACK_WRITE_FAILED // Interupt fail to write disk<br />

9404 MSR_FATHACK_LOCK_FAILED // Lock for low level access of disk failed<br />

9405 MSR_FATHACK_NAME_ERROR // Name tried to go past ?~999999.??? bound<br />

9406 MSR_FATHACK_INVALID_FORMAT // Disk format is not fat16 or fat32

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!