Error: Requested record is locked (error=84) comment: btrieve_status (Thread5392) (Thread 0)

Error:

When accessing the FOS Login Window if a user receives an error: Requested record is locked (error=84) comment: btrieve_status (Thread5392) (Thread 0)

Solution:

Access the Pervasive Control Center from the FOS Server and clear all Pervasive connections.

Select the server in the next window.

First, try clearing the specific user session from the 'MicroKernel Sessions' tab.

Right click on the session and select 'Delete SQL session' to clear that session, and any others. It's best to delete the associated session for that user within that section. Just deleting one may cause other errors as well.

​

If problem persists, you can also delete all sessions found in the 'SQL Active Sessions' tab.

• Related Articles

• Btrieve Error: I/O error during disk read/write (error=2) audtrail: btrieve_status(Thread10428) (Thread 0)

  Error: Btrieve Error: I/O error during disk read/write (error=2) audtrail: btrieve_status(Thread10428) (Thread 0) Solution: Error message is received upon login to FOS for all users. Clear all Pervasive Sessions and/or reboot the FOS server.

• Btrieve Error: Btrieve error 3006 userinfo: btrieve_status(Thread3524) (Thread 0)

  Error: Btrieve error 3006 userinfo: btrieve_status(Thread3524) (Thread 0) Solution: Btrieve error 3006 generally means the client machine and FOS server are not communicating. It is possible that there are hung sessions in Pervasive which may be ...

• Btrieve Error: Requested key not found (error=4) tripdata_setup: tripinfo_get (Thread 0)

  Error: Requested key not found (error=4) tripdata_setup: tripinfo_get (Thread 0) This error message may be received when a trip has been deleted, however, still appears on the FOS Schedule Board. Users may receive the above Btrieve error message ...

• Btrieve Error: Btrieve Status 2 - The Application encountered an I/O error DBIERR_READER

  Error: Btrieve Status 2 - The Application encountered an I/O error Key = [chklist.btr] DBIERR_READER Solution: If only a few users are seeing this error message and the users are on Pervasive version 12, the Collins Engineering Team can try ...

• Common Btrieve Errors

  1 – Normally the temp directory is set to another location besides the data server. The path may be changed in the ‘Utilities’ menu at the login window. 2 – The file is corrupted. The error message should indicate which file. The file must be sent to ...