Resolving Pervasive status 84

Article ID: 0411191535059 - Last Review: 06 January 2009 by jasonl - Revision: 2 - Views: 6705


Symptom
You receive a Pervasive status code of 84 when attempting to use Service Accent.



Cause
A record or page in the table specified is locked by a client, preventing you from amending the record.


Solution
  1. Log any users out of Service Accent
  2. On the server or PC that hosts your Service Accent database, click Start | Programs | Pervasive | Pervasive.SQL Version | Utilities | Monitor to run the Pervasive Monitor
  3. Click MicroKernel
  4. Click Active Users
    On the basis that all users have been logged out of Service Accent, any users still showing as being active must be erroneous.
  5. Click Delete All Users
    This will terminate the connections between the clients and the server, thus releasing the lock.





 
 Related articles

3103, 3012 or 3014 error when trying to access a Pervasive database
Can not link to the WORK table using Pervasive.SQL ODBC
Can't start Pervasive Server Engine, Error 1069, login failure
Configuring Pervasive.SQL ODBC
Connecting to your Service Accent database via ODBC with Pervasive.V8 and later
Error message "1607:Unable to install InstallShield Scripting runtime" when trying to install Pervasive.SQL
Error message "DBU - Access Denied" when entering Pervasive.SQL license key
How to close Pervasive.SQL tables manually
How to configure Pervasive Backup Agent
How to disable the Local MicroKernel Engine under Pervasive.SQL V9
Installing Pervasive.SQL results in an 'Installation was interrupted' message
Message 'Setup has detected that unInstallShield is in use' when installing Pervasive.SQL 2000i
Pervasive.SQL error 2 using Windows Server 2003 and Pervasive.SQL Server Edition
Pervasive.SQL returns a status of 46 when starting Service Accent
Pervasive.SQL V8 compatibility
Resolving Pervasive.SQL status 3012 and 3014 (Part 2)
Running Pervasive.SQL V8 Server Edition on a Windows XP Professional platform
Running the Pervasive.SQL server engine under Windows Server 2003
Status 94 with Pervasive.SQL Server on Windows NT, 2000, 2003
Unable to configure Pervasive.SQL ODBC via Remote Desktop
Unable to connect to Pervasive.SQL Monitor remotely
Using Pervasive.SQL on a 64 bit CPU
Windows NT 4 Server with Windows 2000 clients and Pervasive.SQL 2000 Server

 Additional articles from the white papers

Pervasive Backup Agent v3
Service Accent - Installing Pervasive. SQL
Installing and configuring Pervasive. SQL 2000



For additional resources and information, you can go to the Service Accent Support Centre

Click here to go to the Service Accent Support Centre



Copyright © 2003-2019 Vantage Computing Ltd. All rights reserved. The information contained on this web site is correct as of its publication date.