Error Messages
From EnablerWiki
Created: 27 November 2008. Last Reviewed: 22 April 2009
Error Messages
New Autoscan function
Autoscan examines every .dbf file to make one of the three following determinations.
- The file is accessible but in need of a reindex
- The file is inaccessible – it may be in use or corrupt
- The file appears to be okay
Shared Memory Error – Shared Memory Conflict
Cause:
This is likely to occur when Enabler applications are started for the first time on a Windows2000/XP machine, the error relates to the BDE (Borland Database Engine) that Enabler uses. Nibbler would be running and then you have attempted to start POS. An example of this would be POS attempting to restart after the completion of the End of Day processes.
Solution:
From Enabler Back Office select Till Setup, Database Setup.
- Key in one of the recommended values into the BDE Shared Memory Address field
- Close ALL Enabler applications then power off/on the machine
- Try starting nibbler, once running you should be able to start POS without getting the error.
- If this is unsuccessful you will need to try another value, the value can vary from machine to machine.
Database Error – Unknown Field Name
Cause:
This might occur if a dbf file was copied from a machine on a different version of Enabler
Solution:
Perform a migrate of the databases
- Close ALL Enabler applications including Nibbler
- From the Run command line type:-
x:\enabler\infoctrl migrate (where x: is the drive the Enabler is installed on)
Database Error – Nibbler has detected a database error…
Cause:
An application has crashed or been abnormally terminated
Solution
End the task and re-index all databases
- Close ALL Enabler applications including Nibbler
- From the Run command line type:- x:\enabler\infoctrl\indexall (where x: is the drive the Enabler is installed on)
Lan Error – The LAN sever can not be contacted at this time
Cause:
A LAN (local area network) message would occur if a till was trying to access a file on the server and can’t because the network is unavailable. It is likely that Nibbler would have an X through it on the till. The system will try for 40 seconds to connect before displaying the message.
Solution:
Check the network connection
- Power the till off and on
- On the till try to drill down past the enserver share to the enabler folder on the store server
- On the store server drill down past the en share to the enabler folder on the till
Database Corruption
Cause:
On occasion, a .DBF file might be physically corrupt.
Solution:
In these cases you might need to replace the file with a copy from another computer, or from Head Office, or as a last resort from \upgbase. If you replace from \upgbase you would be erasing the data in that table. It is recommended that you run chkdsk.
- Close ALL Enabler applications including Nibbler
- Copy \UPGBASE\LOCAL\filename.dbf to \ENABLER\LOCAL
- You will need to perform a reindex
- When replacing a data file keep a copy of the file being replaced in case the replacement doesn’t fix the problem e.g. registry corruption.
Reporting – Crystal Run Time Error
Cause:
This can happen when the suppliers report printer drivers have been used.
Solution:
Add the report printer using Windows drivers
Retrieving Error Messages when Further Investigation is Required
.ERR and .DBE files can be copied from the \enabler directory
Transaction Recovery File
When transacting a sale, Enabler maintains a journal log of the transaction to date. This is used to recover the transaction to exactly the same point in the event of a system crash, power failure etc. (A setup flag within Sales Options controls this feature) On occasion, the journal log file has been found to become corrupt. This can cause the POS module to crash as soon as it tries to access the transaction recovery file. To overcome this, either hold down the CTRL key while the POS application is loading (keep holding the key until the main POS screen appears), or erase the file from the \enabler folder. The filename is TRANSLOG.JNL
Database Error – Required Database Missing
Cause:
An application has crashed or been abnormally terminated
Solution:
Check to see if the database file physically exists, if so:
- Delete the index (.mdx) and try and re-index the file
- If the database is missing you will need to replace it from another machine or from \upgbase.
NOTE: If the file is in \enabler\lantran on a store server you will be erasing all history, tills don’t write to lantran locally so replacing from a till (node) will NOT recover the history e.g. sales processed on a node are being written to the \enabler\lantran folder on the store server.
Database Errors that might occur when Staging a Machine
Required database missing \branch.dbf. This could occur when you start Back Office for the first time and select the diskette option to import configuration. This error is a result of attempting to import Enabler configuration on a machine where you have cloned from a machine that has Enabler on a different drive. E.g. a till was cloned on the Head Office server from a branch that has Enabler installed on D: drive, the machine you are wanting to import on has Enabler on the C: drive.
