161_pervasive_error_terminal_services
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revision | Last revisionBoth sides next revision | ||
161_pervasive_error_terminal_services [2018/10/05 16:09 (6 years ago)] – swind | 161_pervasive_error_terminal_services [2018/10/05 16:20 (6 years ago)] – swind | ||
---|---|---|---|
Line 47: | Line 47: | ||
But If it is installed as an **application**, | But If it is installed as an **application**, | ||
- | I Tested this theory on the customer having the issue, and it worked. All 16 TS sessions are open and all 15 System Five Terminals are logged in. | + | 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 also tested by Logging | + | We further |
+ | - Logged | ||
+ | - logged out of that Terminal Services session | ||
+ | - log into Terminal Services on the computer that doesn' | ||
- | We then logged into Terminal Services on the computer that doesn' | + | At this point we had 15 terminals logged into Terminal Services, but only 14 terminals logged into System Five. |
+ | |||
+ | - We then had a System Five user log into the 16th Terminal Services session, and we were able to log them into System Five without getting a 161 error. \\ | ||
+ | \\ | ||
+ | **SUCCESS** \\ | ||
+ | \\ | ||
- | Then we had a System Five user log into the 16th Terminal Services session, and we were able to log them into System Five without getting a 161 error. | ||
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**__ . | 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**__ . |
161_pervasive_error_terminal_services.txt · Last modified: 2018/10/05 16:23 (6 years ago) by swind