Error 6 - “System Overflow”- this error usually means that the software is having difficulty connecting to a database. Find out what function the customer is using when the error occurs (starting check, closing check, reports, gift cards, etc.) to diagnose which database is being used. One issue is that a required field may be missing from the database. The Dbase Text Files folder located in the Micro$ale directory as well as on the Micro$ale CD, web site, and ftp site contains the latest database text files (dud’s). These files outline the structure of the databases (tables, fields, data format). Micro$ale compares these files to the actual databases, and then adds any missing fields. Copy the latest .dud files into the Micro$ale directory on the appropriate computer and then restart Micro$ale. When starting Micro$ale, a message should appear stating “upgrading databases” to let you know that it was done correctly. If the problem persists after copying in the .dud files then the database in question may be missing or corrupt. First, go to register configurationÆ database options, and use the “compact databases” function. If the database or its index is corrupt, then this might repair it. If the database is beyond repair or missing then the final solution would be to copy a blank database into the Micro$ale directory. Please note that performing this action will erase all data contained within that database.
Error 9 – “Subscript out of range” – One possible cause for this error is an incorrect value set in “register options” after an upgrade. Go to “register options”, look through the options for anything incorrect (i.e. text in a numeric field, etc.) and then touch the “save” button. This error can also occur in older versions if the number of users does not match up with the number of remote register locations.
Errors 13 – “Type Mismatch” – there are 3 possible reasons for this error message. The first is that there is a database corruption. Try using the “compact databases” function in register configuration. The other two reasons would require you to examine the database in question using Microsoft Access. The first thing to look for would be a “date” in an incorrect format (i.e. mm/dd/yy instead of mm/dd/yyyy). The other thing to look for would be an alphanumeric character in a field that should contain only numeric characters, and vice versa.
Error 52 – “Bad file name or number” - Computer cannot find another computer, cash drawer, or printer. Make sure all devices and computers are on and communicating. Also verify all Windows network hardware and software settings.
Error 53 – “file not found” – This error occurs when Micro$ale cannot find a specific file. Find out what function the customer was using at the time to diagnose which file will need to be replaced and replace it. One common reason for this error message is if the “status API” is not selected when the Epson advanced printer drivers are installed. To correct this issue reinstall the ADT209e.exe and select StatusAPI from the list.
Error 62 – “Input past end of file” – This error only occurs if one of Micro$ale’s .dat files is empty.
Error 70 – “Permission Denied” – Access to a file or directory is blocked. Make sure that the Micro$ale directory is shared for full access and that file attributes are not read only. Also verify all Windows user account names and passwords are the same across all terminals and that all user passwords have not expired.
Error 75 – “Path/file access error” – Micro$ale file is not shared for full access. Share all files in the Micro$ale directory for full access. This error can also occur if Micro$ale is trying to access two different devices attached to the same serial port when one of the devices has the port locked (EX: if the cash drawer is attached to the receipt printer which is attached to the LPT printer port, and a failed print job has the port locked, using the Open Drawer button will result in this error).
Error 94 – “Invalid use of Null” – there is an empty field in a database from which we are trying to load data, or there is a date in one of the databases that is not in the expected format: DD/MM/YYYY. This can be caused by database corruption or due to a hardware or software error during a process that was writing to the database. You will have to search the database to find the blank fields and delete them, or correct the dates in the wrong format, or you will have to replace the database in question.
Error 339 – “Component VSPRINT7.ocx or one of its dependencies not correctly registered. A file is missing or corrupt” – This error occurs sometimes after an upgrade. Reinstalling the VSPRINT component usually resolves the issue. On the Micro$ale CD, in the install support folder, there is a folder called “VSView Upgrade”. In that folder is an executable file. Run that to install the VSPRINT components.
Error 372 – “System Error: Application-defined or object-defined error” – When printing anything in Backoffice Mode. VSPRINT7.ocx or a file associated with it is damaged or missing from the Micro$ale directory. Run the VSView setup from the Micro$ale CD or download it from www.microsale-pos.com.
Error 380 – “Invalid Property array value” – this message can either be caused by a database with a corrupt index or by an ocx component file that is corrupt or missing that we use to format information on the screen. Try compacting the databases or running a Micro$ale upgrade for the same version they are running (to reinstall and register the program files without losing any current data)
Error 429 – “Active X Error" – Micro$ale component file is missing or out of date. Rerun the upgrade Install for that version of Micro$ale.
Error 3078 – “Microsoft Jet database engine could not find the input table or query ( )" – This error means that one or more of the databases being used is not up to date. First, find out what function the employee was using to determine what database the error relates to, or reference the “table name” with the Dbase Text files to find out which database. After that is determined copy the .dud files into the Micro$ale directory on the appropriate machine and restart Micro$ale to upgrade the databases.
Error 3159 – “Not a Valid Bookmark" – this error usually refers to a corrupt database index. The first thing to try is to use the compact database utility in register configuration. If this utility is not able to repair the database then you will need to replace it. Determine which database is corrupt by finding out what function the customer was using at the time and then replace the database with a blank from the “Blank Databases” folder located in the Micro$ale directory as well as the Micro$ale CD.
Error 3265 – “Item not found in this collection" – There is a filed missing from one of the databases. Copy the dud files into the Micro$ale directory and restart Micro$ale to initiate a database structure upgrade (existing data will NOT be affected).
Error 3343 – “Unrecognized Database Format" – this error refers to a corrupt database. The first thing to try is to use the compact database utility in register configuration. If this utility is not able to repair the database then you will need to replace it. Determine which database is corrupt by finding out what function the customer was using at the time and then replace the database with a blank from the “Blank Databases” folder located in the Micro$ale directory as well as the Micro$ale CD.
Error 3704 – “Operation is not allowed when the object is closed” – Micro$ale has lost its connection to a component library file or data set while trying to use it. Restart Windows on each terminal to reinitialize all files