Go to the Keystroke POS Home Page

Keystroke Errors & Warnings

Sections:

Common Error Messages Section

Error Messages Section - listed by Error Number

Error Messages Section - No Error Number

Warning Messages Section - listed by Warning Number

This page describes the most common problems and error messages that can be encountered using the Keystroke system.

The best and fastest way to resolve a problem is to first write down any error messages and/or other details which may help in resolving the problem before calling SBS Technical Support Services at: 800.ASK.4SBS or 800.275.4727 (toll-free for current Software Maintenance Service plan holders).

When calling for assistance, you will be asked for the Serial Number of your Keystroke system. The easiest place to find this number is on the Keystroke logo screen.

IMPORTANT: If you are experiencing random errors with your system, please review the section on Power Conditioning at the beginning of the Custom Modules and Advanced Features User Guide Appendix.

Common Error Messages Section

Internal Error:
This error message is usually the result of running the DOS Keystroke program with insufficient available conventional memory. In many cases, certain modules will run without problems, while others, which are larger and require more memory, will cause the system to crash. This error can also be encountered by shelling out of Keystroke using the DOS Shell command on the Utility menu and then loading Keystroke again (by running KEYSTROK.EXE) instead of properly exiting the DOS Shell by typing EXIT at the DOS prompt.

Solution:
If an Out of Memory error is encountered, you should first attempt to free up additional base memory. It is recommended that you have at least 550K (532,480 bytes) of conventional memory available (The maximum is 640K on any PC Compatible computer). To check the amount of memory available, type the command MEM at the DOS prompt. The amount of memory available will be displayed as Largest Executable Program Size. If you can't free up more memory, you may want to try the /LOWMEM Switch (see System Startup Switches).

Printer Not Ready:
This error will result when sending data to a printer (also a cash drawer or other external device) that is not ready to receive data.

Solution:
First, check to see that the printer (or other device) is on line (usually indicated by a green light on the front of printer). If the printer is not on line, check to see that it is properly plugged in, the power is turned on, and paper is loaded; sometimes it is necessary to disconnect and reconnect the printer cable to ensure a good connection. Check that the printer cable is connected to the same port that is specified in the Printer or Cash Drawer Setup. If you're not sure, try switching either the cable connection or the specified port.

WARNING: Disk is almost full!:
This warning message will appear when the Keystroke program is started if there is less than one megabyte of unused disk space available on the hard disk.

Solution:
Free up additional space on the hard disk by removing unnecessary files as soon as possible. If the hard disk becomes completely full, the system will not be able to store additional data and other errors will occur. Refer to the Managing Transaction Data Files section of the Custom Modules and Advanced Features User Guide Appendix. On newer machines with hard disks greater than 2GB, the /NOD switch can be used if you are certain there is enough disk space. See the section on Startup Switches earlier in the Custom Modules and Advanced Features User Guide Appendix.

If Keystroke prints odd characters instead of lines on Reports and Forms:

Solution: Change the character set or symbol set on your printer to one which includes the line draw characters (single and double lines and intersections; usually called the ASCII Extended or PC-8 character set). This is typically controlled by either a dip switch setting or menu functions on the printer. This problem can also be resolved by not printing documents which use the line draw characters. Try using an alternate Form File (i.e., one that uses the dash and equal signs instead of unbroken line draw characters), or changing the Single and Double Line codes in the Printer Driver to 45 and 61 respectively. These are the decimal form of ASCII codes which represent the dash and equal symbols.

Keystroke Error Messages listed by Error Number

Error 5 - Illegal Function Call:
Make sure Keystroke is running from a mapped Drive letter and not from a UNC path. This error can be caused by many different things and is usually a sign of some form of corruption (a form file, or the program itself). Back up and reinstall the program disks. If it is encountered during installation, it indicates an invalid COMMAND.COM file. Add SET COMSPEC=C:\COMMAND.COM to AUTOEXEC.BAT file. If it occurs on a database record, delete SCRN##.DAT. If it occurs in Label Manager, delete LBL#.DAT. If it occurs in Report Manager, delete RPT#.DAT. If it occurs in Importer, there may be double quotes in the source file fields. Note: The "#" in the above file names indicates a specific file name/number. Call SBS for assistance in identifying these file names.

Error 6 - Overflow (number too large):
This error is usually caused by the entry of too large of a number. It is most often seen when running a report. It can also be a sign of data corruption. Try to pinpoint which record (Invoice, Inventory item, etc.) is causing the error and look at the data for any fields with *** (multiple asterisks). If incorrect, delete the record, pack, and then reenter it.

Error 7 - Out of Memory:
This error is usually the result of running the Keystroke program with insufficient available conventional memory (under 640K). Keystroke requires 550 - 600K of conventional memory to run properly. Use a utility like MEMMAKER to free up more conventional memory, or try starting the program using the /LOWMEM switch.

Error 9 - Subscript Out of Range:
If this error occurs on the Logo screen, a database index is corrupt. Use /LOWMEM to get into program, then Pack the suspected database. I may also be due to a corrupt configuration file; try renaming KSCNF.DAT. If occurs accessing a database screen, it may be a corrupt screen file (SCRN#.DAT). It may also be memory related. Note: The "#" in the above file names indicates a specific file name/number. Call SBS for assistance in identifying these file names.

Error 11 - Division By Zero:
This error occurs either the DOS or Windows version in Purchase Manager only. It indicates a problem with the invoice being properly calculated when the invoice is saved. This only happens when importing in the line items from the Special Import Line Items function. To avoid this error, use the page up key [PGUP] through the entire transaction until getting to the top and then save. This forces Keystroke to recalculate the transaction totals before it is saved. This problem has been fixed in releases beyond version 4.20 Build 62.

Error 13 - Type Mismatch:
This error is usually due to an incorrect Import setup or incorrect source data. It may also be a corrupt database screen file; delete SCRN#.DAT. Note: The "#" in the above file names indicates a specific file name/number. Call SBS for assistance in identifying these file names.

Error 14 - Out of String Space:
This error will sometimes occur when several functions are called upon simultaneously (i.e., stacking several levels of dialog boxes on top of one another). If it occurs on a database record, delete SCRN##.DAT. If it occurs in Label Manager, delete LBL.DAT. If it occurs in Report Manager, delete RPT#.DAT or turn off Detailed setting. It may also be memory related. Note: The "#" in the above file names indicates a specific file name/number. Call SBS for assistance in identifying these file names.

Error 24 - Device Timeout:
This error is usually caused by a hardware device (printer, drawer, display, scale, etc.) which is either not attached, not ready, or not responding correctly. Check to see that it is turned on, the cables are connected, and that it is on line and has plenty of paper. Make sure you are sending data to the correct port. It may also be a print buffer overflow; slow down baud rate or change COM parameters, if possible.

Error 25 - Device Fault:
This error is usually caused by a hardware device (printer, drawer, display, scale, etc.) which is either not attached, not ready, or not responding correctly. Check to see that it is turned on, the cables are connected, and that it is on line and has plenty of paper. Make sure you are sending data to the correct port. It may also be a print buffer overflow; slow down baud rate or change COM parameters, if possible.

Error 27 - Printer Out of Paper:
This error is usually caused by a printer that is out of paper. It can also be caused by a hardware device (printer, drawer, display, scale, etc.) which is either not attached, not ready, or not responding correctly. Check to see that it is turned on, the cables are connected, and that it is on line and has plenty of paper. Make sure you are sending data to the correct port. It may also be a print buffer overflow; slow down baud rate or change COM parameters, if possible.

Error 28 - Out Of Stack Space:
This error indicates the need to check conventional memory. (See Error 7 above for details).

Error 48 - Error In Loading DLL:
This error indicates that the file BCLW32.DLL, which is required to be located in the \keystrok\bin directory, is not being found there.

Error 52 - Bad File Number:
This error almost always is a follow-up error to a previous problem. This error by itself does not really help much in determining what went wrong. It you get this error, first try to remember what was being done when it occurred. Also note any other errors or warning messages that may have preceded it.

Error 53 - File Not Found:
This error can be caused by a missing program or form file; reinstall the Keystroke program. It may also occur when attempting to run Keystroke from somewhere other than the Keystroke program directory, or if the Keystroke directory in the PATH statement, or when logged into a network without full read/write access.

Error 54 - Bad File Mode:
This error may occur when sharing the LPT1 port on a network. Use port setting: "port=file=lpt1." (including the period character).

Error 55 - File Already Open:
This error is usually encountered when using a cash drawer or pole display. Make sure the Keep Port Open setting is OFF.

Error 57 - Device I/O Error:
This error is most likely due to a problem with hardware (typically hard drive, network card, or network). If it is the network connection, first try restarting the computer and then possibly also restarting the server. Secondly, check the network cards and cables. The hard disk may also be developing a bad spot; run Scandisk or another third party hard disk diagnostic program.

Error 58 - File Already Exists:
If this error is encountered during the Pack function, Keystroke may be running on another computer. File attributes may be set to read-only; check using the ATTRIB command.

Error 59 - Bad Record Length:
This error may indicate that a data file may be corrupted. May also be caused by CONFIG.SYS file not existing (HIMEM.SYS or EMM386.EXE not loaded).

Error 61 - Disk Full:
Hard disk is full. This error may indicate that the disk being written to has run out of space (less than 1MB available). You must delete some files before continuing.

Error 62 - Input Past End:
This is usually caused by an incorrect or corrupted Form file. Try switching to a different Form file. It may also be caused by an improper Import source file.

Error 63 - Bad Record Number - Pack Data:
This error is a sign of a corrupted data file. Back up immediately and then pack the indicated file. Be careful to not back up this corrupted data over the top of an existing (good) backup set. It may be necessary to use the /LOWMEM startup switch to get into Keystroke to run the Pack function.

Error 64 - Bad File Name:
This error usually indicates an incorrect configuration, file name, or setup. It could be the KSTRNTBL.DAT file. Delete it and restart Keystroke.

Error 67 - Too Many Files:
This error indicates the need to increase the value of the FILES=## line in CONFIG.SYS file, and reboot the computer. A number around 80 should be adequate.

Error 68 - Device Unavailable:
This error indicates that the program is attempting to send data to a port that does not exist (e.g. a printer is set up on serial port COM2: when there is no COM2: available on the computer). It may also occur when a workstation has lost the network connection. The error message usually displays the device or file that is unavailable.

Error 70 - Permission Denied:
This error indicates a network connection may be lost, sharing may be disabled, or O/S user rights are insufficient. If it is encountered during the Pack function, another computer may be in Keystroke.

Error 71 - Disk Not Ready:
This error indicates the need to retry. Check cables, check network connection, reboot if necessary.

Error 75 - Path/File Access Error:
This error usually indicates a lost connection to the network. It may also occur if file attributes are set to read-only; check using the ATTRIB command.

Error 76 - Path Not Found:
This error indicates that the SET TEMP line in your AUTOEXEC.BAT may point to a directory that does not exist. It may also occur due to a lost network connection. Windows XP/2000/2003 has an autodisconnect set to 15 minutes so if the system is idle for 15 minutes, it might get booted off the network. Use the NET USE command and look for the status of the network drive. Use NET CONFIG to set it to 999 minutes.

Error 80 - Feature Removed:
This error is caused by very low conventional memory. The computer is unable to display the "out of memory" message or to display the correct error. (See Error 7 above).

Error 91 - Object Variable Or Width Block Variable Not Set:
If using the Windows version, start the DOS version and look for a different error to help determine what the problem may be.
- Entering Sales Manger - Ingenico is selected as Signature Capture and the port is set to None. - Starting Winstroke - May have just created a shortcut instead of running setupWS. Run setupWS again. Make sure network drive is shared as Full Access (not Read Only)

Error 111 - showing form 3 - \Keystrok\Ingenico\WAIT.ICF
Happens after installing Microsoft Security Update, 03/14/06. Power off Ingenico Signature Capture device, reboot computer, then re-run LOADFRMS.EXE from the \Keystrok\Ingenico directory.

Error 326 - Resource with Identifier version not found
Please call SBS for assistance with an Error#326.

Error 339 - *.OCX Not Registered (could be a number of .ocx files) :
A spyware or anti-virus program has blocked the file. This file is used by Keystroke when you monitor All Keystrokes in the Audit Parameters. It is sometimes seen as BlackBox (ZoneAlarm) or Keyloger (Norton/McAfee). You need to Always Allow this file or Ignore the blocking of this file.
May also indicate the need to run SETUPWS.EXE.

Error 372 - Failed to load control status bar from MSCOMCTL.OCX:
This error may indicate the need to upgrade the computer operating system from Windows 95A to 95B or 95C.

Error 380 - Could Not Open.... Device Unavailable:
This error may indicate a problem setting up a device on a COM port in the Windows version (such as a Pole Display), and using a port setting of port=file=COM3: (for example). Change the port setting to port=file=COM3:9600,N,8,1.

Error 381 - Invalid Property or Array Value
May be a corrupt index (Transactions, Customers, etc). Pack suspected file(s).

Error 429 - ActiveX Component Missing:
This error may indicate that a Windows 2000 computer may not have rebooted after running SETUPWS.EXE. Restart the computer. If that doesn't work, un-install & re-install SETUPWS.EXE and then manually restart the computer. or try running REGDLLS.BAT from the server Drive/Directory from a DOS prompt. (On Windows2000 or XP, DO NOT open a DOS prompt w/ COMMAND.COM, must use CMD.EXE for this to work.)

Error 430:
Indicates the need to run REGDLLS.BAT from the server\keystrok directory and then restart the computer. It can also occur if SETUPWS.EXE was run thru Network Neighborhood or under Run-Browse. Run SETUPWS.EXE from a network drive\directory using the Run Command (K:\KEYSTROK\SETUPWS.EXE).

Error 432 - FileName Or ClassName Not Found During Automation Operation:
This error indicates the need to rename WS*.INI and WS*.ATB in keystrok\data directory. There may also be the need to reinstall KS and rerun SETUPWS.EXE or try running REGDLLS.BAT from the server on the computer displaying the error and restart the computer.

Error 438 - Object doesn't support this property or method:
Run Tutor for Keystroke POS. If error comes up in Tutor as well then re-run SETUPWS.EXE from a mapped drive letter. If error happens only with a certain icon, check that icon's START IN directory and make sure it matches the beginning of the TARGET line in the shortcut.

Error 440 - Automation Error - TRY GUI=0:
May be a problem with the size of the Keystroke window. Try resizing or maximizing the window. If it happens when selecting a customer in Sales Manager then try GUI=0. It will only happen with customers that have a contact. It happens when the select contact list is attempting to load. If running in GUI=0 mode works then the error is related to Visual Basic Runtime Library files being out of date or not compatable for the operating system. This can also happen in Purchase Manager going to Edit/Print. Most commonly happens with older operating systems like Win98, WinME, WinNT. Solution is to install and update to a current operating system or run the program in GUI=0 mode. It is possible to get this error on a new O/S if some other application has been installed that has overwritten some of the Visual Basic 6 Library files.

Error 480 - Print Text Error:
This error may indicate that a Windows only printer (multi use printer/fax/scanner), after printing from another application, has retained that application's settings. Restart the computer.

Error 481 - Illegal Picture:
This error indicates that the Keystroke ini file being used to start Keystroke could be pointing to a corrupt or nonexistent graphic.

Error 482 - Print Text Error:
This error indicates that the network printer being printed to may be powered off or unavailable.

Error 521:
When on a Citrix setup and getting "Cannot open Clipboard (or Notepad)". Need to use the /K command line switch (e.g. /K C:\TEMP). Also may need to disable the client clipboard mapping in Citrix and restart the Citrix session to have the change take effect. If the error appears on a peer to peer setup, restart the computer (some other program may be locking the clipboard).

Error 3324 - Could not remove open order for stock number n
May be caused because Keystroke cannot read or write from KSBKO.NDX. Run DELUTIL.EXE to Update Open/Back Orders.

Error 8002:
This error is very similar to the Error 70's series errors. Most likely due to looking for a file path that is already open or doesn't exist. It may also be due to a hardware problem (cash drawer doesn't exist, pole display conflicting with printer port, etc.) Refer to the file number in the error text for more details.

Error 8005 - Print Text Error:
This error may occur if the Windows version is looking for a Customer Display or Cash Drawer that is not attached to the computer. Either turn it off or use the /C command line switch to specify an alternate KSCNF.DAT file. It may also if the Windows version is printing to a COM port. First, try changing the printer port to file=COM1. (if on COM1:). Second, try changing the printer port to file=COM1:9600,N,8,1 (if on COM1:). Third, try using the Windows printer driver and set the port to a Windows printer. Also may try using Windows to delete the hardware port, restart the system and let Windows recreate the port. This error may be followed by Error 6, overflow. If using PCCharge with a Pin Pad, turn off the pin pad in PCCharge.

Error 8012 - Printer is not ready. Could not open a Com port:
- A port is selected in cashdrawer setup with no cashdrawer connected. Change port to none.
- Possibly pole display & cash drawer or receipt printer are conflicting.
- The file replication service cannot process the request. The system volume is busy with a previous request.
- When printing from Windows version: change port to file-com1. or com1:

Error 8015 - Could Not Open Com:1 Filenum=156:
- A port is selected in cashdrawer setup with no cashdrawer connected. Change port to none.
- Possibly pole display & cash drawer or receipt printer are conflicting.
- The file replication service cannot process the request. The system volume is busy with a previous request.
- When printing from Windows version: change port to file-com1. or com1:
- On WinXP or Win2000, the receipt printer SHOULD NOT be setup in Windows as a Generic/Text Only printer or as any printer at all, because Windows locks the port for use in Keystroke for serial printers.

Error 50003 - Unexpected Error:
This error occurs if printing to screen (Labels or Reports). Add GUI=1 to shortcut target line.

Error 2147024770 - Automation Error:
Toolbars (ws.atb)

This error indicates the need to rename WS#.ATB in data directory (Windows version Toolbars).

Error 2147319779 - Automation Error:
Library not registred

Run SETUPWS.EXE from mapped drive. Use Start-Run and type full path and setupws.exe.

Error 2147417848 - Method {of object} Failed:
Run SETUPWS.EXE from mapped drive. Use Start-Run and type full path and setupws.exe.

Keystroke Error Messages with no Error Number

Error - CashMan does not support AR:
Keystroke is reading the wrong license files. Make sure the proper license files are installed.

Error - Date Mask Not Yet Supported:
This error may occur if the file GLLINK.DAT is corrupt. Write down all parameters, posting accounts, inventory departments, and payments types. Delete GLLINK.DAT and re-enter all the information.

Error - Error in Backup:
Probably due to a PKZIP problem. Run ksback.bat from the keystrok directory and look for PKZIP errors, then refer to PKZIP documentation.

Error - Error Loading Overlay:
This error has to do with Keystroke having Matrix files initialized but not using Matrix Manager (usually in the DOS Version). Delete KSMT*.DAT and MTX*.DAT from the keystrok\data directory, but only IF NOT USING MATRIX MANAGER.

Error - File Locked By Another User:
If on Windows XP and error contains "user1.tmp is locked by another user" and if it only happens opening Keystroke, then add MNUM=# to the command or target line, where the # is unique to each computer.

Error - Illegal Operation:
This error can start as a white error box that says Winstrok at the top. The text begins "An error has occured on this program. To....." & only has ignore or cancel as options. After cancelling, the illegal operation error appears. Check the Details tab on the error window: If it refers to VGA...... - check windows display settings. - it may be set to 16 colors.It must be set to at least 256 colors. - may need to add FontName=Courier New to WS#.INI file.

If the error refers to oleaut32.dll (usually when running setupws.exe): 1) Check error message when opening Keystroke. It will probably say oleaut32.dll is out of date. If so: 2) Copy the file from the Keystroke CD \setup\system\oleaut32.dll to c:\windows\system folder on the computer & overwrite the existing file. THIS FILE MUST BE COPIED WHEN THE COMPUTER IS BOOTED TO DOS MODE, (Windows cannot be running or cannot be in DOS shell) 3) Reboot the computer to Windows.

If this error occurs after running SETUPWS.EXE, run the Tutor for Windows, if it works and the data files in the keystrok\data directory still display this error, rename WS.ATB or WS#.ATB.

Error - Internal Error:
Error may display after a failed data file conversion from v4 to v5 and then restoring a v4 backup and trying to convert again. The error may display converting from v4.55 (which was a beta version). Solution: Rename *.DAT to *.SBS (or any other extension that doesn't exist). Check the directory for .DAT files (DIR *.DAT) to make sure none exist. Restore the v4 backup. Then start Keystroke with no startup switches (can use the shortcuts under Start-Programs).

Error - "You are trying to convert from version prior to 2.01. You must install version 2.01 before using this version":
Use the [Shift F12] key combination to display the Keystroke informational screen. If the DataDir=[ ], check the CurDir (usually c:\keystrok) for bad .DAT files. It is also possible that KSTRNHDR.DAT is corrupted. Copy this file from the keystrok\tutor directory and then correct the Next Number for all transactions (Sales, Quotes, Purchases, etc.).

Keystroke runs very slowly over the network:
Microsoft has identified a bug in Windows XP SP2 due to Security Update MS04-044 (KB885835) and knows of the issue. Microsoft will not be fixing this bug until the next major release of Windows. This link to Microsoft explains the problem: http://support.microsoft.com/?kbid=894463
Please call SBS for information on how to obtain the Hotfix. After the Hotfix has been applied, Keystroke runs up to 1000 times faster. Keep in mind that Norton Anti-Virus, Norton Internet Security, and McAfee Security Suite still cause a significant delay. Keystroke may run as much as 5 to 10 times slower on machines using these products.

Keystroke Error File Number Descriptions:
File Number = Description
1 = Inventory
2 = Customer
3 = Vendor
4 = Clerk
5 = Department/Categories
6 = Transactions
7 = Matrix
8 = Back Orders / Credit Memos
9 = File Sort
10 + File is Index files (Example - 11=Inventory Index, 18=Back Order Index)
20 + File is Comment files (Example - 22=Customer Comments)
30 + File is Alternate Data files (Example - 31=KSINV1.DAT or KSINV2.DAT)
36 = KSTRNHDR.DAT (holds counters)
46 = Trans2 (used when splitting trans files)
155 = [KSTEMP]KSDLG.SCR
155 = [KSTEMP]KSMENUS.SCR
156 = Cash Drawer
200 = 203 Tax Tables
204 = 206 Price Tables
207 = 209 Commission Tables
226 = Variance
235 = [kstemp] KSSTRING.SCR
236 = [datadir] USERS.TMP
237 = [datadir] USER#.TMP (used to lock the machine #)
238 = [userdir] BFR#.TMP (used for comments)
240 = Scale
241 = Pole Display
242 = Pole Display File
247 = [data]KSSTORES.DAT (StoreLink - Store Setup)
255 = KSDLG.SCR

Keystroke Warnings listed by Warning Number

#200 - Not enough disk space.

#201 - In Keystroke POS Version 6.10 through 6.21 Build 24, in some cases it was possible for more than one register to write audit entries to the data file at the same time which could sometimes result in "Warning 201" errors. In cases where the Warning #201 message was left on the screen, other workstations would start getting a "File...KSTRNHDR.DAT is Locked" message.

Keystroke v6.21.26 was released to correct this problem by increasing the strength of the File Locks used when writing Audit entries. Versions prior to 6.10 do not have this problem.

The actual size of the file is different than the counter that stores the number of records that should be in the file. (e.g., File#6 = Transaction file). Look at the number of records and compare it to the actual size of the file. Usually adjust based on the size. Answer "YES" to "adjust the number of records to match its size" when the size is larger.

#201 - Matrix - The actual size of the file is different than the counter that stores the number of records that should be in the file. Usually resolved by adjusting based on size, and Packing the suspected file (e.g., File#6 = Transaction file).

#202 - (ADDRECORD) Similar to warning #201. The question is worded opposite while Packing. Typically answer "NO" when asked "base the pack on the number of records" when the number of records is LESS than the size. Always want to base on size.

#203 - File size is greater than 8Mb (64K in version 4.0). Keystroke will display the file name in the warning box.

#204 - Free Disk Space less than 1,048,575 (1MB). Hard drives over 2GB will read incorrectly because of the jump from 32 bit to 64 bit. Partition hard drive to less than 2GB or use the /NOD startup switch if certain there is enough disk space.

#205 - (AR) The Customer Number on the credit memo is not the same as the Customer Number on the Index. Indicates a corrupted index.

#206 - (AR - Credit Invoice) Keystroke was unable to locate the Invoice in order to apply payments to it. AR will be out of balance. Clear/delete the transaction and re-enter it.

#207 - (AR - Credit Invoice) Keystroke was unable to locate a payment. Clear/delete the transaction and re-enter it.

#208 - (AR - UnCredit Invoice) Keystroke was unable to locate the Invoice in order to remove payments from it. AR will be out of balance. Clear/delete the transaction and re-enter it.

#209 - (AR - UnCredit Invoice) Keystroke was unable to locate payments in order to remove them from the Invoice. AR will be out of balance if the Invoice is ever re-saved. Clear/delete the transaction and re-enter it.

#210 - (AR - UCI) - Same as above, happens when trying to delete a payment in AR to fix the addition of an Applied amount to the Amount Due after the balancing entry has been deleted from the invoice.

#210 and #211 - (Posting Variance) Err#210 indicates the Stock Number was not found when reading in a Variance. Err#211 indicates the Variance would have posted to the wrong item.

#212 - (Updating Purchase Order from Receiving Function) The item being received (which was found in the Open Order file) was found on its actual Purchase Order/Invoice. This is caused by a corrupted transaction or Back/Open order file. Rebuild Back/Open order file using the Update function in Delete Utility.

#215 - caused by a bad Stock Number index in the data set being updated to. The warning only pauses (for 3 seconds) when run from the command line. Run it from inside StoreLink to get it to stop on the record. May need to pack.

Keystroke POS Point of Sale Software

Home | Products | Support | Dealers | Downloads | Search | Contact | Questions?
Tech Support |Training Services | F.A.Q. | Updates

|