Support Home Sales Website Technology Contact Us
RDP Support  

RDPWin KB Booking Engine - IRM.Net RDPWin4 & PCI Compliance Search

Article ID: KWin0094
Added:  9/04/2009 SS/EL

Status 84 or 85 Accessing RDP Data

Issue: Pervasive Status 84 or Status 85 is displayed accessing data in an RDP system.  These status codes indicate that the data being accessed is locked in the Pervasive engine by another user in RDPWin or another RDP product.  This can happen if an RDP workstation is powered off while in the middle of a Pervasive transaction.  A Pervasive transaction occurs whenever data is filed to disk by an RDP system.


  1. RDP systems also set semaphore locks in the LockFile.dat.  These usually correspond with the Pervasive locking system.  Use System - Locks and Users in RDPWin to find which records are locked.  The locked records are displayed in the lower half of the screen.

  2. There could be multiple locks showing, so check each user name to make sure it is not a legitimate lock.  After finding the orphan lock, right-click on the lock in the grid and select Delete Lock.
  3. Remove the user in the Pervasive engine using one of these two scenarios.  An administrator login might be necessary unless it is run from the server console already logged in as Administrator. 

      1. Select the Users Tab.
      2. Find the user with the lock and highlight.
      3. Click the Disconnect Selected User button.
    • Access the Pervasive Monitor at Start - Programs - Pervasive - PSQL10 - Utilities - Monitor.
      1. Select Active Users from the MicroKernel menu.
      2. Find the user with the lock and highlight.
      3. Click the Delete Current User button.
  4. If the issue is still not resolved, logout all RDPWin workstations and reboot the data server with the advice of RDP support or your IT person.

Status Definitions from Pervasive

Status 84:  An Insert, Update, or Delete operation attempted to lock an index page to insert or delete a key value. Have your application check for this status code and retry the operation if the status code is returned.

The application tried one of the following:
  1. Applied a no-wait lock on a record that is currently locked by another application.
  2. Tried to access a file in a no-wait transaction while another application holds one or more active record locks in that file.
  3. Tried to update or delete a record locked by another application.
The application can use either of the following recovery methods:

  1. Retry the operation until it is successful. This can be the simplest and quickest solution for a network with light to moderate use.
  2. Note:  Applications should limit the number of retry attempts when Status 84 is received inside a concurrent transaction. Otherwise, the application might enter a deadlock situation with another transaction. If Status 84 is still received after a few retries, abort the transaction and then attempt the transaction again.

  3. Use the wait option (+100/+300) instead of the no-wait option (in versions that support the wait option).

Status 85:  The MicroKernel returns this status code in one of the following situations:

  1. While one user has a file locked in an exclusive transaction, another user attempts to lock all or part of that file.
  2. The workstation MicroKernel has a file open, and a client machine that has the Requester loaded tries to open the same file via the server MicroKernel. The server MicroKernel cannot open the file because it cannot obtain exclusive access. The client machine that has the Requester loaded receives this status code.
  3. When opened by a MicroKernel, two data files have the same filename but different extensions (for example, INVOICE.HDR and INVOICE.DET). One file is open and in Continuous Operation mode, causing the MicroKernel to generate a delta file (for example, INVOICE.^^^). The MicroKernel returns this status code when you attempt to open the second file. For this reason, we recommend naming your files with completely different names, not just reusing the same name with different extensions.
  4. Without any pattern of occurrence, you may receive a status 85 when the file is closed because Anti-Virus software opens and locks the file to scan causing the next database operation to fail. To resolve, set the Anti-Virus software to not scan Pervasive SQL data files. Consult your Anti-Virus software manual for instructions on how to exclude files.
  5. A delete action was attempted on a data file that is in continuous operations. A data file put into continuous operations is locked from deletion through the relational interface and the transactional interface. In addition, the file is locked from any attempts to change the file structure, such as modifying keys and so forth.
Support Home  RDPWin4 & PCI Compliance Enhancement Requests Open A Web Support Ticket
Training New Sales Website Old Sales Website Contact Us

 Facebook     Twitter      LinkedIn   TODF