FS127 Error when pressing F9 to save information (AREV Specific)
At 14 AUG 2000 01:48:01PM Perry Blacken wrote:
I have a user who is using AREV 2.0 and receives the following error message when attempting to enter information into the database:
FATAL ERROR READING 022422256 IN FILE ETT
FS127
GROUP FORMAT ERROR:
OS FILE: FATAVOL\REV58140.LK
GROUP #: 00004809
RECORD LENGTH INCORRECT OR FRAME LINKAGE ERROR.
This database is being housed on an NT4.0 server.
At 14 AUG 2000 02:30PM Warren wrote:
The file has been corrupted. It is highly recommended that the NT Linear Hash Service be used when running ARev on an NT server. The minimum release of ARev that will support the NT Service is version 2.03. The update files can be downloaded from this website to update version <2.03 to version 2.03. The NT service must be purchased separately.
The fix the file:
1)From TCL
CW LH_VERIFY
enter the appropriate Volume and file name (however it would be wise to scan all volumes and files) use the D & F options
2) Note the groups that have errors (or you can re-run this with the XP options which will use the existing results without rescanning and print a report to the printer.)
3) Backup the files *IMPORTANT*
4) Then from TCL:
DUMP filename
in dump do a "ctl F" enter in the frame, a range or all. All should be used with caution because some DOS and ARev combinations would create a temp file at DOS, delete the old REVxxxxx file and not rename the temp file back to the original REVxxxx file. This could be solved by manually renaming the file. This should not be a problem with v2.03 and NT but be aware of the possibility.
5) Inspect the FIX_DUMP_TEMP and FIX_DUMP_GARBAGE files (I'm not sure on the file names but they should be similar). Records from here should be regarded with suspicion as they may be truncated or otherwise corrupted.
6) Run LH_VERIFY again on the file after fixing.
NOTES:
Data will most likely be lost depending on the types of problems in the file. Groups and overflow frames can be truncated and all the remaining data lost, although some of this should find its way to the TEMP and GARBAGE files.
Depending on how old your last good backup is, it may be better/simpler to restore the file. Be sure to make a current backup first though.