Getting PO Lock File Problem During PO Printing

Getting PO Lock File Problem During PO Printing

           Q - I was attempting to print a Purchase Order and received the following message:

    Btrieve Error USE on PO Lock File - 065 File Locked


A - The message implies you have two users trying to use "Print Purchase Order" function at the same time and that caused a conflict. Depend on the version of your Elliott Business software, you may receive a different kind of message like following:

    Another Station Is Printing Purchase Orders, Print Not Allowed


 You need to find out which other users are opening POLCKFIL.DAT. This is not a Btrieve file under PSQL's control. You will need to go to the server console and use the shared folders open file utility to see who opened this file. 

You can do this by right clicking "Computer" and choosing "Manage." Then, in Server Manager, find "Share and Storage Manager" and choose "Manage Open Files ...."  Find the user who opened POLCKFIL.DAT in the corresponding DATA folder.  If that user is still using Elliott, and probably in the middle of printing a PO, simply ask that user to exit or wait. If that user is not in Elliott or has lost connection already, then you can manually close this open file or choose to close the entire user session.  See sample screen below:



The above procedure applies to Windows 2008 server.  For a different server environment, your procedure may be different. 

In the similar way, you may also getting the following lock file error:
  • CPLCKFIL.DAT- COP Lock File. This is due to someone else being  in the middle of printing a COP invoice. Our system currently allows only one user to print a batch of invoices (a range of invoices) at a time.
You can resolve this issue by applying the same procedure above.


    • Related Articles

    • 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 ...

    • 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 ...

    • System Lock File Requirements

      Lock files are used in Elliott to prevent users from entering transactions when other users are posting, to prevent users from entering transactions when invoices are printed, or to prevent multiple people from printing purchase orders at the same ...

    • Create PO Receiving Event to Trap Negative Qty on Hand Problem

      Q - Sometimes our receiving department is behind with their tasks in updating received quantities in the Elliott inventory. As a result, it creates a negative quantity on hand in Elliott. The items sold during the period use the old average cost. ...

    • How to Fix COP Lock File Error When Printing Invoice

      Release Date: 08/21/2018 Q - Every time we try to print invoices or credit memos, we get this Btrieve error: Btrieve Error USE on CPFRMFIL COP Lock File See sample screen below: I don’t see anyone locking this file in the PSQL Monitor utility. Do you ...