Troubleshooting

Overview

This topic includes troubleshooting information that may be helpful should EZScale generate an error or behave unpredictably. The information here is intended for administrators and technicians only.

Error During Compact and Repair

If an unrecoverable error occurs while the database is being compacted and repaired, an ERROR.LCK file will be created in \DATA directory and EZScale will abort to protect your data. If EZScale can not automatically recover from the error the next time you start the program, the following message will appear.

If this error appears, you will not be able run EZScale until you clear (delete) the ERROR.LCK file.

IMPORTANT:      DO NOT delete the ERROR.LCK file or make any changes until you read and understand the information below. Failure to follow these instructions carefully may result in the irretrievable loss of data.

Backup Your Files

Before you do anything else, make backups of any of the files below that are in your \DATA folder under the application folder. Note, depending on when the error occurred, one or more of the following may not be present.

    EZScale000.mdb

    EZScale000.bak

    EZScale000.tmp

Compact & Repair File Protection

To protect your data in the event of an error during the compact and repair process, EZScale performs the following tasks:

    EZScale creates the ERROR.LCK file so that if anything happens, no matter how severe... even a power failure... the ERROR.LCK file is in place. EZScale will not start again until the ERROR.LCK file is cleared (deleted).

    Next, EZScale makes a backup copy of your master EZScale000.mdb data file to a file named EZScale000.bak.

    Only after making the backup does EZScale attempt to compact and repair your master EZScale000.mdb data file. The compact process generates a new file named EZScale000.tmp. This is the the compacted and repaired database.

    With the database successfully compacted and repaired to EZScale000.tmp, EZScale deletes your master EZScale000.mdb and renames the EZScale000.tmp file back to EZScale000.mdb.

    If we get this far, the process was successful and EZScale clears (deletes) the ERROR.LCK file.

Interpreting Results

If the process completes successfully, you will have a compacted and repaired master EZScale000.mdb data file intact and a backup (EZScale000.bak) of your master data file BEFORE it was compacted and repaired. Even if an error did occur, as long the EZScale000.mdb file exists, EZScale will automatically clear (delete) the ERROR.LCK file and attempt to use the EZScale000.mdb file. In the worst case, if the EZScale000.mdb exists it simply didn't get compacted and repaired.

If the process does not complete successfully, review the steps above carefully do decide where the process failed and how to recover.

REMINDER:      Before you do anything else, we strongly recommend that you backup the EZScale000.mdb, EZScale000.tmp and EZScale000.bak files.

For example:

    If the EZScale000.mdb and EZScale000.tmp files both exist, then the compact and repair operation probably did not complete. In that case, the best copy you have is the EZScale000.bak version. After making backups, delete the EZScale000.mdb, EZScale000.tmp and rename the EZScale000.bak to EZScale000.mdb. Clear (delete) the ERROR.LCK file and run EZScale and try compacting and repairing again. If the problem persists, contact technical support.

    If the EZScale000.tmp file exists but the EZScale000.mdb does not, then the compact and repair process probably succeeded, but for some reason the program was not able to rename the EZScale000.tmp file back to EZScale000.mdb. After making backups, try renaming the EZScale000.tmp file manually to EZScale000.mdb. If that works, clear (delete) the ERROR.LCK file then run EZScale and test that the the program seems to be running correctly. If the problem persists, contact technical support.

    If the EZScale000.mdb file exists and the EZScale000.bak file exists but the EZScale000.tmp file does not exist, then the compact and repair operation never got started. After making backups you can try clearing (deleting) the ERROR.LCK file then running EZScale and trying the compact and repair option again. If the problem persists, contact technical support.