Pervasive 161 error when logging into System Five in a Terminal Services Environment where the clients log into a TS Server and the data resides on a Data Server.
Pervasive Server is installed on the Data Server and Pervasive Client is installed on the TS Server.
If there are 15 Terminal Services sessions, 15 workstations that access System Five and 15 pervasive client licenses, then there shouldn't be any issues.
However… If the Terminal Server has 16 or more user licenses, but there are only 15 Pervasive Licenses you will likely experience 161 errors.
The client had :
- The Pervasive Server license was installed on the Data Server as a service, which is correct. Nobody would normally be logged into the server, but it will be running and sitting at the log in screen.
Here is where it became interesting.
So what this means is that two sessions would essentially be playing musical chairs to see who gets the last seat.
We uninstalled the Pervasive Client on the TS, then re-installed it making sure that we installed it as an Application.
This was because logically, if it is installed as a service, the Terminal Services session would take the Pervasive license when the user logs into it.
But If it is installed as an application, System Five is the one that would take the Pervasive license.
I Tested this theory on the customer having the issue, and it worked. All 16 TS sessions are open and System Five is up and running in all 15 System Five sessions.
We further tested this theory by:
At this point we had 15 terminals logged into Terminal Services, but only 14 terminals logged into System Five.
So to prevent these type of issues in an environment where there are separate Data and TS Servers, Pervasive MUST be installed as an Application .
Created by Steve Wind October 5 2018