The FOPS6 transaction file
is a keyed Btrieve file. As such, if the file server running the Btrieve engine,
maintains the file, is abnormally stopped, the file's keys are likely to be damaged.
This often becomes apparent
by the "comms" PC not being able to add any more weigh-labelling transactions
to the transaction file. When this happens the "comms" PC locks the scales out, and records a 'Error Adding
Transaction...Btrieve Error 2' message in its error file (use Utilities / View Error File).
If Btrieve reports an error '2' for the transaction file (TRANS.FIL) then the file has to be rebuilt.
If the transaction file
is large (greater than 200MB) then it may be impractical to stop the system
to rebuild the file offline. In this case use the following instructions.
Note: The rebuild operation will require free disk space to be approximately two times that of your transaction file size.
To rebuild the file without stopping production and despatch do the following steps
1. Edit FOPS6.INI file so that in section '[RECOVERY]' a line reads F6RECOVERYMODE=YES'.
2. Quit all FOPS6 programs, which are currently running.
3. Rename TRANS.FIL
to TRANS.OLD (usually held in directory: FOPS6/FIL If different see F6FILEPATH
variable in FOPS6.INI).
4. Restart FOPS6 on the desired PCs. Answer 'Y' to the Transaction File creation prompt on the first PC.
5. Recover original transaction file according to the Btrieve engine type:-
Btrieve Engine on a Netware file server (assuming F6FILEPATH=\FOPS6\FIL)
At the server console prompt ':' enter
LOAD BUTIL -RECOVER SYS: \FOPS6\FIL\TRANS.OLD SYS: \FOPS6\FIL\TRANS.RCV
Or, at a workstation's DOS command prompt set at the F6FILEPATH e.g. 'F:\FOPS6\FIL>' enter:-
BUTIL - RECOVER TRANS.OLD TRANS.RCV
Pervasive Software Btrieve Engine On a NT Server
At the NT Server's DOS command prompt set at the F6FILEPATH e.g. '\FOPS6\FIL>' enter:
\PVSW\BIN\BUTIL -RECOVER TRANS.OLD TRANS.RCV
Or, at a workstation's DOS command prompt set at the F6FILEPATH e.g. 'F:\FOPS6\FIL>' enter:
\PVSW\CLIENTS\DOS\BUTIL -RECOVER TRANS.OLD TRANS.RCV
(If it reports that BUTILDOS.MSG file is not found, enter:
SET PATH=%PATH%; \PVSW\CLIENTS\DOS and then try again).
6. Load the recovered data into the new transaction file according to the version of FOPS6:-
FOPS6 version 6.302 or above
Select Tidy | Import Recovered Trans. from the FOPS6 main menu.
FOPS6 version 6.301 or below
Use the BUTIL program again but with the following parameters:
BUTIL -LOAD TRANS.RCV TRANS.FIL
E.g. on a Netware server console enter:
LOAD BUTIL -LOAD SYS:\FOPS6\FIL\TRANS.RCV SYS:\FOPS6\FIL\TRANS.FIL
7. Edit FOPS6.INI file so that in section '[RECOVERY]' a line reads F6RECOVERYMODE=NO'
8. If FOPS6 is version
6.301 or below and the system has been used during the previous steps the stock
reports will be incorrect. Select Tidy | Rebuild Stock Totals from the FOPS6 main menu when the system is
not in use for a few hours. Using the system during a stock total rebuild will leave the stock totals reports incorrect.
Click here to return to MT Support Index