Received Message "Must Run COP Setup First"

Received Message "Must Run COP Setup First"

Q - Elliot froze up for about 90 seconds with this message: 

 Must run COP Set Up First 


After 2-3 minutes everyone could get back in. Is this something we should be concerned about?

A - Someone locked the COP Setup File to cause this problem. This could happen if someone goes into COP Setup. While that user stays in the COP Setup, everyone else who tries to get into COP and launch any task will get the message "Must Run COP Setup First."  The fact that this clears up after 2-3 minutes means the user who was in COP Setup exited the screen.

You should be somewhat concerned about this. At least, you should educate your users who has the right to access COP Setup about the locking condition he/she could create.

If this particular lockup extended for a long period of time and you didn't know who the offending user was, you could go to your PSQL server console and enter into either "Computer Management" or "Server Management," then choose "Open Files" under the "Shared Folders" to see who opened the CPCTLFIL.DAT file in your DATA folder. See sample screen below. 



In a similar way, if you are in the following modules' setup screen it may cause the setup file to be locked, and other users could receive similar message.  The following is a list of 3 columns.  The first column is the setup areas when someone get into.  The 2nd column indicates which file in the DATA folder will be locked.  The 3rd column shows the message other users will receive when try to access the corresponding module.

  • A/R Setup - ARCTLFIL.DAT - Must Run A/R Set Up first
  • A/P Setup - APCTLFIL.DAT - Run A/R Control File Maintenance First
  • P/R Setup - PRCTLFIL.DAT - Btrieve Error 065  File Locked on Payroll Control File
  • BOMP Setup - BMCTLFIL.DAT - Btrieve Error 065 File Locked on BOMP Control File

Please also refer to the following related Knowledge Base article:

          https://support.netcellent.com/portal/en/kb/articles/getting-po-lock-file-problem-during-po-printing-2-10-2024




    • Related Articles

    • Error 199 Operating System Error Code Lies Outside Expected Range

      Release Date: Version: 7.x & Up An Elliott reseller reported one of his users received an IO error message: Btrieve Error 199 on CPORDHDR AR Control File (32-Bit) 199 Operating System Error Code Lies Outside Expected Range with the following file IO ...
    • Elliott V7.4 Release Notes: What's New Since Elliott V7.3

      What’s New Since Elliott V7.3 Use ATP as MRP The ATP (Available to Promise) feature has been in Elliott since V6.7. Initially, ATP only supported parent items and was mainly used by importers to view scheduled sales orders and purchase orders ...
    • Feature - Utility to Re-Calculate Item First Received and Last Received Date

      Release Date - 5/5/16 The purpose of this utility is to recalculate an item's first and last received date. The application will prompt for an item first received cut-off date. For any item with a first received date on or after this date, the ...
    • Feature: Send an Email to the User Locking a Record

      Release Date: 1/26/2023 Versions: Elliott V8.5 and Above Background Some Elliott tasks, like COP Order Entry / Change Order, will cause a record to be locked while the task is executing. Subsequently, another user will start a task, like COP Order ...
    • Run Time Error 166 in Deferred Processing

      Release Date: 2/16/2022 Version: 7.5 & Up Q - I couldn't find documentation about error 166. Our deferred processes locked and had this error. Can you provide any information about what this message means? EL850RP.EXE - COBOL Text Window Execution ...