Database errors: Difference between revisions
No edit summary |
mNo edit summary |
||
| Line 5: | Line 5: | ||
= Database Error – Read Failure = | = Database Error – Read Failure = | ||
[[Image:]] | [[Image:Database errors_Figure_1.jpg]] | ||
Need to determine whether the database (.dbf) or the index (.mdx) is corrupt: | Need to determine whether the database (.dbf) or the index (.mdx) is corrupt: | ||
| Line 19: | Line 19: | ||
While a missing index can often be corrected by Enabler automatically reindexing the database for the missing index, which re-creates the index, a missing database file cannot be repaired automatically in most cases. | While a missing index can often be corrected by Enabler automatically reindexing the database for the missing index, which re-creates the index, a missing database file cannot be repaired automatically in most cases. | ||
[[Image:]] | [[Image:Database errors_Figure_2.jpg]] | ||
| Line 32: | Line 32: | ||
An unknown fieldname error message indicates an incompatibility between the database structures and the fields that Enabler is expecting to see in the database. This could occur if problems happened with an Enabler upgrade, or if a file was replaced from a different version of Enabler. | An unknown fieldname error message indicates an incompatibility between the database structures and the fields that Enabler is expecting to see in the database. This could occur if problems happened with an Enabler upgrade, or if a file was replaced from a different version of Enabler. | ||
[[Image:]] | [[Image:Database errors_Figure_3.jpg]] | ||
The first check to be done is to ensure every till in the store is on the same version of Enabler. They aren’t then all tills should be upgraded to the same version. The store server must ALWAYS be on the same or a higher version of Enabler as the tills. | The first check to be done is to ensure every till in the store is on the same version of Enabler. They aren’t then all tills should be upgraded to the same version. The store server must ALWAYS be on the same or a higher version of Enabler as the tills. | ||
| Line 46: | Line 46: | ||
A “Number is out of range” message will likely have a similar cause to the “Unknown Fieldname” message, and can often occur immediately after the “Unknown Fieldname” error. | A “Number is out of range” message will likely have a similar cause to the “Unknown Fieldname” message, and can often occur immediately after the “Unknown Fieldname” error. | ||
[[Image:]] | [[Image:Database errors_Figure_4.jpg]] | ||
The first check to be done is to ensure every till in the store is on the same version of Enabler. They aren’t then all tills should be upgraded to the same version. The store server must ALWAYS be on the same or a higher version of Enabler as the tills. | The first check to be done is to ensure every till in the store is on the same version of Enabler. They aren’t then all tills should be upgraded to the same version. The store server must ALWAYS be on the same or a higher version of Enabler as the tills. | ||
Revision as of 06:28, 24 April 2009
Created: 24 November 2008. Last Reviewed: 24 April 2009
Database errors in Enabler, although not common, can occur for a variety of reasons. Below are some sample errors with suggested resolutions. With all database errors, unless you are 100% sure of the method for fixing the problem, it is strongly recommended that you contact Magenta Retail for assistance before proceeding.
Database Error – Read Failure
Need to determine whether the database (.dbf) or the index (.mdx) is corrupt:
- Close all Enabler applications including Nibbler
- Delete the index relating to the error. In the above sample this is c:\enabler\local\posdiv.mdx.
- Re-index the database that experienced the error. In the above sample this is c:\enabler\local\posdiv.dbf so the reindex command would be c:\enabler>infoctrl indexlocal posdiv)
- Start POS again.
- If Database error re-occurs then most likely the .dbf is corrupt.
- If the database is in the LOCAL folder, refer to “Enabler Database Files – LOCAL” for information about replacing or recovering the file.If the database is in the LANTRAN folder, refer to “Enabler Database Files – LANTRAN” for information about replacing or recovering the file. If the database is in the LANMNT folder, refer to “Enabler Database Files – LANMNT” for information about replacing or recovering the file. If unsure, please contact Magenta Retail for further advice.
Required Database Missing
While a missing index can often be corrected by Enabler automatically reindexing the database for the missing index, which re-creates the index, a missing database file cannot be repaired automatically in most cases.
To determine the best course of action, refer to the suggestions below.
- If the database is in the LOCAL folder, refer to “Enabler Database Files – LOCAL” for information about replacing or recovering the file.
- If the database is in the LANTRAN folder, refer to “Enabler Database Files – LANTRAN” for information about replacing or recovering the file.
- If the database is in the LANMNT folder, refer to “Enabler Database Files – LANMNT” for information about replacing or recovering the file. If unsure, please contact Magenta Retail for further advice.
Unknown fieldname
An unknown fieldname error message indicates an incompatibility between the database structures and the fields that Enabler is expecting to see in the database. This could occur if problems happened with an Enabler upgrade, or if a file was replaced from a different version of Enabler.
The first check to be done is to ensure every till in the store is on the same version of Enabler. They aren’t then all tills should be upgraded to the same version. The store server must ALWAYS be on the same or a higher version of Enabler as the tills.
If all tills are on the same version, in most cases the error can be fixed by performing a migrate. The command for this would be:-
Infoctrl migrate
which needs to be run from a command prompt in the folder where Enabler is installed, which in the above example would be c:\enabler. Ensure that all Enabler applications are closed before running this command.
Number is out of range
A “Number is out of range” message will likely have a similar cause to the “Unknown Fieldname” message, and can often occur immediately after the “Unknown Fieldname” error.
The first check to be done is to ensure every till in the store is on the same version of Enabler. They aren’t then all tills should be upgraded to the same version. The store server must ALWAYS be on the same or a higher version of Enabler as the tills.
If all tills are on the same version, in most cases the error can be fixed by performing a migrate. The command for this would be:-
Infoctrl migrate
which needs to be run from a command prompt in the folder where Enabler is installed, which in the above example would be c:\enabler. Ensure that all Enabler applications are closed before running this command.
See Also
Enabler Database Files – LANMNT
Enabler Database Files – LANTRAN
Enabler Database Files – LOCAL
Retrieved from "http://192.168.2.6/wiki/index.php/Database_errors"
Views[[Image:]][[Image:]][[Image:]][[Image:]][[Image:]][[Image:]]
