Error Messages

Created: 27 November 2008. Last Reviewed: 3 October 2014

Error Messages

Database Errors That Might Occur When Staging a machine

Required database missing \branch.dbf

Cause:

This could occur when starting Back Office for the first time and importing configuration via the diskette option. This error is a result of attempting to import Enabler configuration on a machine where configurations have been 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 configuration set as Enabler installed on D: drive, the machine which configuration have been imported on had Enabler on the C: drive.

Solution:

This will require you to manually edit the drive letter in tills configurations files on H/O server to ensure it's correctly setup. The three configuration file called winsuite.ini, winpos.ini and wshware.ini are located under enabler\comms\config\,region>\<branch>\<Till> . Will need to open each file with notepad and manually do a find/replace of the drive letter for the new till. You will also need to update the new tills local copies, located in the enabler folder with the correct drive letter to enable Back office to open. Then export the updated configuration from Enabler H/O to branch again and reimport it into a new till via Back Office > File Menu > Import Configurations option

Unable to access file \\servername\enserver\enabler\lanmnt\comflg.dbf

Cause:

This could occur on a till (node) if you don’t have sharing and permissions setup correctly. A Store or Head Office server MUST have the Enabler DRIVE shared as ‘enserver “and till database paths must be correctly configured to access this path.

Solution:

Shut down enabler application on all tills and server, update tills windows user to have appropriate permissions to access and write to the shared locations. Check database paths set on till located under Back Office > Till Setup > Database Setup are correctly configured. These database paths must contain the correct share name. test via network drill down from till to server that database path access is available. Restart machine and open nibble to confirm access. Any changes to database path will require the Administrator User code and password to apply. Contact Magenta Support if you require this information

Shared Memory Error – Shared Memory Conflict

Cause:

This is likely to occur when Enabler applications are started on a XP or Windows 7machine, the error relates to the BDE (Borland Database Engine) that Enabler uses. One application is conflicting with another when opening. Usually occurs nibbler is running and Pos attempts to open for scheduled resume . Solution: from Enabler Back Office select Till Setup, Database Setup and then the BDE Settings tab.

• Key in one of the recommended values into the BDE Shared Memory Address field
• Close ALL Enabler applications and restart again
• Try starting nibbler, once running you should be able to start PoS or back Office without getting the error.
• If this is unsuccessful you will need to try another value, the value can vary from machine to machine

Too many maxi file handles open

Cause:

This is likely to occur when Enabler applications are started for the first time on a XP or Windows 7machine and unable to update the registry with appropriate values.

Solution:

Start up enabler applications once for the first time by right clicking shortcut in start-up menu and run as Administrator. This is a security requirement to update register setting for Windows 7

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
• In extreme circumstances re-run a manual upgrade over machine

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

LAN Error – The LAN server 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 a red 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 is Corrupt other than header

Cause:

On occasion, a .DBF file might be physically corrupt and POS or Nibble is unable to run

Solution: In these cases you might need to replace the file with a copy from backup or from another computer, 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 with fix as well

• 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. Contact Magenta Support if you are unsure if a file can be replaced.

Reporting – Crystal Run Time Error

Cause: This can happen when the printer manufacturer drivers have been used to install printer.

Solution: Add the report printer using Windows drivers Retrieving Error Messages when Further Investigation is Required

• .ERR ,*.DBE *.DMP and *.*LOG 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. Contact Magenta Support if unsure.

<RRBBTT>b.dbf approaching the maximum size.

Cause:

The tills local copy of the nibble backup file has exceeded its maximum file size and is unable to open the nibble application

Solution:

Locate file under tills enabler\local folder and rename to *.old then restart nibble.exe and system will generate a new copy of file. Check History purging to ensure purging of nibble log is set for 5-7 days maximum.

See Also

Anti Virus Software