DFIC Error 55 - Keys Out of Sequence

Last reviewed: 08/04/2003
Article ID: R10612

The information in this article applies to:

Tabs3 Version 10 & 11
Tabs3 Remote Version 10 & 11
GLS Version 10 & 11
APS Version 10 & 11
TAS Version 10 & 11

SUMMARY

This error indicates a record in an "*.IDX" file does not match the corresponding information in the "*.DAT" file.

RESOLUTION

Tabs3 and TAS:

TAS Note: A known issue has been discovered that can cause an erroneous Error 55 in the TAS Payee file to be reported if a blank payee record is present. Under normal circumstances, a blank payee cannot even be saved. This particular error 55 can be ignored until you receive updated software. You can easily verify whether a blank payee is causing this error by running a Payee List. A blank payee will be shown at the top of the list. This issue can be corrected with updated TAS software. Contact Technical Support if you have this error. For all other error 55's, use the following procedures.

Make a temporary backup. Do not overwrite a current backup.
Access the Reindex Files program and select to reindex the file shown on the Error Report.
If this process successfully completes, then rerun the Data File Integrity Check program.
If the integrity check still indicates errors, you must restore the appropriate program's data files from a backup copy.
If there are no errors during the Data File Integrity Check, the errors have been eliminated (either by correction or deletion of corrupted records).

GLS and APS:

Version 11

Make a temporary backup. Do not overwrite a current backup.
Access the Reindex Files program and select to reindex the file shown on the Error Report.
If this process successfully completes, then rerun the Data File Integrity Check program.
If the integrity check still indicates errors, you must restore the appropriate program's data files from a backup copy.
If there are no errors during the Data File Integrity Check, the errors have been eliminated (either by correction or deletion of corrupted records).

Version 10

Make a temporary backup. Do not overwrite a current backup.
Run the File Reorganization program.
If this process successfully completes, then rerun the Data File Integrity Check program.
If the integrity check still indicates errors, you must restore the appropriate program's data files from a backup copy.
If there are no errors during the Data File Integrity Check, the errors have been eliminated (either by correction or deletion of corrupted records).

Tabs3 Remote

This error can occur in the remote data files or the optional validation files.

If the errors are in the validation files, run the Data File Integrity Check program in Tabs3. If there are no errors in the Tabs3 Data File Integrity Check, recreate the Tabs3 validation files and transfer the new validation files to the remote terminal. Run the Data File Integrity Check program in Tabs3 Remote again.
If the errors are in the remote data files, back up the RMT*.* files using a new set of diskettes or tape (do not overwrite a current backup). Reindex the file shown on the Error Report. If the reindex successfully completes, rerun the Data File Integrity Check program. If the reindex crashes or there are still errors in the Data File Integrity Check, you must restore your Remote data files from a back up. If there are no errors during the Data File Integrity Check, the errors have been eliminated (either by correction or deletion of corrupted records).

REFERENCES

KB Article R10167 - Data File Integrity Check Errors in Verification Files
KB Article R10102 - How the Reindex Files Program Affects Your Data
KB Article R10686 - Using the Built-In Backup Program Without Overwriting an Existing Backup

THE INFORMATION PROVIDED IN THE SOFTWARE TECHNOLOGY, INC. KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. SOFTWARE TECHNOLOGY, INC. DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL SOFTWARE TECHNOLOGY, INC. OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF SOFTWARE TECHNOLOGY, INC. OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.