ERROR 035 on AP TEMP CHK File
Q: I get error message
035 on AP Temp Chk File when I try to print check from #
501235. My check printing worked properly at few hours ago.
A: The system creates a file name the same as check# 501235 for the laser check second stub. Unfortunately, there is folder name the same as the check# <501235> in the DATA folder. The system can't create the file because another file with the same name exists in the current folder.
Solution: Delete, Archive or Rename the duplicate name of folder then it will be working properly.
Related Articles
Credit Card Processing Error: Chk Viawarp For Dupl
Q - In A/R -> Processing -> Credit Card Trx Handle, at field "21. Approval No," I press F4 to interface with the credit card payment gateway server, then I receive the message "Credit: AP Error: Chk Viawarp For Dupl." See examples below: When I go to ...
Error 153 on BEXTFH During AP Check Printing
Release Date: 12/21/2020 Version: 7.0 & Up From time to time, users who are using Accounts Payable Check Printing encounter a message similar to the following: Object Code error: file 'EL850U.LBR\BEXTFH.gnt' error code: 153, pc=4900, call=23, seg=0 ...
Btrieve Error USE on COP Lock File
Q - Today, for whatever reason, we experienced a large amount of locking issues in the warehouse. Several times today we ran into the problem with printing invoices where we received a message "Btrieve Error USE on COP Lock File," and it stops ...
What Is Btrieve Error 010 on IMINVLOC Inv Location File?
Release Date: 08/23/2024 Version: 7.x & Above Q - I received an error message when trying to post PO warehouse receiving: EL860P: Btrieve Error 010 on IMINVLOC Inv Location File (32-Bit) 10: The key field is not modifiable See sample screen: A - If ...
EL850US: Btrieve Error 094 on USERS SY Users Lic. File
Release Date: 02/18/2019 Q - I just implemented Elliott on a Windows 2019 server, when I started up Elliott for the first time, I received the following message: EL850US: Btrieve Error 094 on USERS SY Users Lic. File 94: The application encountered a ...