About
Error 6 - “System Overflow” means the software is having difficulty connecting to, or reading, a database
Determine when the Error 6 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. Typically, the way to prevent this error is to put the site on SQL. SQL is a more stable environment over Access and prevents database corruption.
Error 6: (Runtime Error 6) When upgrading from Version 7 to Version 9
Typically this is caused when the Windows framework is not set to the correct version or SQL is not being used.
- Enable .NET Framework 4.7 or 4.8 and reinstall the upgrade
- Ensure the system is on SQL
Error 6: Updating order screen buttons
Typically this is caused when menu/button changes are being made on a remote terminal and it cannot connect to the file server. Please double check the pathing to the file server or ensure the file server is powered on.
Error 6: SQL encryption error when trying to connect POS to SQL server
This means a firewall is turned on and is conflicting with the program. Turn off the firewall in Windows to correct the error.
Error 6 Overflow message on time clock
An apostrophe was used in an employee's name. An apostrophe cannot be used. MicroSale blocks you from typing in forbidden characters, but copy/pasting allows the entry. Change the employee's name to fix the issue.
Error 6 Running Reports
An error 6 indicates you’re not able to connect to a database or a resource on the network, such as a printer; If you’re trying to view a report that is formatted for an 80 col.
Make sure you have a printer properly installed in Windows and is set as the default printer
Error 6 on Phone Orders
Typically caused by 1 of 2 issues:
Not enough characters supported:
Customer was adding gate, apt. number, gate code, etc. and it got an error 6 overflow and kicked out of microsale. Error log shows a timeout error. Went into the call in orders database and increased the address field length to 200 chars.
After an upgrade, SQL was not enabled:
Reinstall MicroSale using the “Run as Administrator” option (by right clicking the setup.exe). Install SQL and import the call in order customer data to the SQL data set
Error 6 when paying an order
The chk-stat.mdb was missing from the M$ directory. Copy the chk-stat and transaction history databases from another terminal. The transaction history.mdb database is basically a copy of the chk-stat.mdb file that M$ uses to create a backup of the chk-stat.mdb file during the close out.
Notes:
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.