Why does my Edit/Posting Report Says It's Locked?

Some errors may occur when running an edit/post report indicating files are locked.

Error: [User] is posting interfund gifts

Control File is locked, please try later

An error occurred while attempting to gain exclusive access to the gift module.
To clear the lock flags:

1.  Click on Tools > System Utilities > Clear Process Lock Flags.
2.   Delete the name/login of the person said to be locking.

It will not hurt anything to delete the entire row associated with the process you are running.  For instance, if you are having issues posting from item entry in AP, find the idcode column value of AP and remove either the entire line (use the delete button) or remove the name(s) in the user list column. If uncertain which line to remove, you can remove all the fields in the list without ramifications.  The system will re-build the list as the edit reports are run.

Frequently this issue is caused when more than one person is in the module editing and/or posting records.  When you run an error-free edit report, you set a flag to yes for your username and the particular report or process. When the posting report is run, it checks to see that you have authority to run it and also whether you have run an error-free edit report. If someone ran an edit report after you did, their name replaces yours in the list and you are locked out of the post.  This is to insure that records being posted are the ones associated with the edit report just reviewed.

If you close FIMS  under certain circumstances, the flags aren't cleared and you have difficulty running the edit and post.  So, removing your name in the Clear Process Lock Tool should allow you the ability to rerun the edit and complete a post.

If clearing the process lock flags does not resolve the error message do one of the following when all users are logged out of FIMS:
  1. Restart the admin service by following the below steps:
  2. Click Start > All Programs > OpenEdge > ProEnv
  3. Type the following command and press enter: proadsv -stop
  4. Type the following command and press enter: proadsv -start
  5. Make sure the databases are running by typing the following command then pressing enter: dbman -start -all
Reboot the server.



Was this article helpful?

Thanks for your feedback! Did this solve your issue?

Comments (optional):

Thanks for your feedback!
We're glad it was helpful but sorry it didn’t solve your issue. If you need assistance, click Chat with Support below.
We’re sorry to hear that. Please tell us why.

 I don't like how this works.

 The answer is confusing.

 The answer didn't match what I was searching for.

Additional Comments (optional):

Thanks for your feedback! If you need assistance, click Chat with Support below.
Thanks for your feedback. Help us make our products even better by sharing details in our Idea Banks or our online Community.
Thanks for letting us know. We'll work on clarifying the information in the article. If you need assistance, click Chat with Support below.
Thanks for letting us know. We'll work on updating the search engine to return more relevant results.