"FRx GL index is currently locked by <username> since <00:00:00>" when connecting to an FRx company
Entry Type: Informational
Product: FRx
Application: FRx Desktop
Version Reported: 6.7
Subject:
"FRx GL index is currently locked by <username> since <00:00:00>".
Possible Resolution:
Note: Support for FRx has changed. Please see the following notice:
FRx Updates Notice By Microsoft
FRx attempts to avoid conflicts when multiple users build a GL index by creating a lock file for the company. When the index build is completed, the lock file is deleted. If another user sets the company as default while the index is being built, the above message displays to inform them that the index is currently being built. FRx then attempts to reconnect to the database 30 times. If FRx cannot connect to he GL index file after 30 attempts, the user is asked to select a different company or try again later.
If the message shows after a lengthy time frame, the .LCK file has failed in its attempt to self-delete. The cause is an abnormal termination or a ungraceful exit.
To resolve the error, manually deleting files is required. Verify all users have logged off from FRx, delete the .LCK and .G32 files, and open the company again.
- Open Windows Explorer, and browse to the \SysData directory.
- Delete all files with the extensions .LCK and .G32.
- Open FRx.
If the error persists, send the Frxsys32.mdb file to the appropriate support team for your product line for editing.
- Sage MAS 90 and 200 ERP - [email protected]
- Sage MAS 500 ERP - [email protected]
- Sage PFW ERP - [email protected]
Include the following in the subject line of the e-mail:
- A valid Sage Software account number.
- The case number for this issue (if a case has been created).
Include the error text in the body of the e-mail.