Resolving Pervasive status 161 'maximum number of users reached'

Article ID: 030516101117 - Last Review: 20 October 2015 by chrisn - Revision: 6 - Views: 25105


Symptom
This error will occur if you try to access your database with more users than you have Pervasive.SQL licenses.


Cause
Common causes

  • Having more Service Accent licenses than Pervasive.SQL licenses (for example, failing to install additional Pervasive.SQL licenses)
  • Open network connections keeping a user connection live, thus using up a Pervasive.SQL license
  • Having installed Pervasive.SQL with a temporary license key and failing to apply a permanent license key




Solution
If you have installed all of your Pervasive.SQL licenses:

On the server or PC that hosts your Service Accent database, run the Pervasive Monitor (from Start, Programs, Pervasive, PSQL, Utilities), click MicroKernel and then click Active Users/Sessions. Delete any erroneous users. It will be easier to identify such users if you log all users out of Service Accent first.

For Actian Pervasive.V12:
On the server or PC that hosts your Service Accent database, run the PSQL Monitor (from Start, Programs, Actian PSQL12, Utilities), Press “Ok” on the Server it shows, go to the tab “Microkernel Sessions”, select an Active User. Delete any erroneous users by right clicking on the mouse and select “Delete MKDE session”. It will be easier to identify such users if you log all users out of Service Accent first.

If you have not installed all of your Pervasive.SQL licenses, or are not sure about this:

  • On your server or PC that hosts your Service Accent database, click Start, Programs, Pervasive, PSQL, Utilities, License Administrator)
  • Under User Count, check the total number of licenses installed. If the total is correct, follow the instructions above. If not, you need to install additional licenses.

    For Pervasive.V8 and later:

    1. Enter the License Key in the boxes
    2. Click Apply Licence Key

    Ensure that your user count is correct



 
 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

 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-2018 Vantage Computing Ltd. All rights reserved. The information contained on this web site is correct as of its publication date.