User Tools

Site Tools


161_pervasive_error_terminal_services

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
161_pervasive_error_terminal_services [2018/10/05 16:20]
swind
161_pervasive_error_terminal_services [2018/10/05 16:23] (current)
swind
Line 16: Line 16:
 ==== In this scenario: ==== ==== In this scenario: ====
 The client had : The client had :
- ​- ​16 Terminal services sessions +  * 16 Terminal services sessions 
- 15 Pervasive Client licenses +  ​* ​15 Pervasive Client licenses 
- 15 System Five licenses. ​+  ​* ​15 System Five licenses. ​
  
  - 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. ​  - 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. ​
  
- ​- ​The Terminal Services server has the Pervasive Client installed. ​+  * The Terminal Services server has the Pervasive Client installed. ​
  
 Here is where it became interesting. ​ Here is where it became interesting. ​
  
- ​- ​The Pervasive Client was installed as a **service**. ​+  * The Pervasive Client was installed as a **service**. ​
  
- ​- ​This would mean that when each user opens a Terminal Services session, a client license will be taken. ​+  * This would mean that when each user opens a Terminal Services session, a client license will be taken. ​
  
- ​- ​The last person to log into a Terminal Services session would not be able to log into System Five, even if there was an available terminal. This is because the first 15 Terminal Services sessions have already taken the 15 Pervasive Client licenses. ​+  * The last person to log into a Terminal Services session would not be able to log into System Five, even if there was an available terminal. This is because the first 15 Terminal Services sessions have already taken the 15 Pervasive Client licenses. ​
  
- ​- ​If all 15 users that normally logged into System Five were the first to log into terminal Services, everything would appear to be ok. +  * If all 15 users that normally logged into System Five were the first to log into terminal Services, everything would appear to be ok. 
  
 So what this means is that two sessions would essentially be playing musical chairs to see who gets the last seat.  So what this means is that two sessions would essentially be playing musical chairs to see who gets the last seat. 
Line 50: Line 50:
  
 We further tested this theory by:\\ We further tested this theory by:\\
- ​- ​Logged out of System Five on one of the System Five sessions +  * Logged out of System Five on one of the System Five sessions 
- logged out of that Terminal Services session +  ​* ​logged out of that Terminal Services session 
- log into Terminal Services on the computer that doesn'​t have System Five installed.+  ​* ​log into Terminal Services on the computer that doesn'​t have System Five installed.
  
 At this point we had 15 terminals logged into Terminal Services, but only 14 terminals logged into System Five. 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. \\+  * 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** \\ **SUCCESS** \\
161_pervasive_error_terminal_services.txt · Last modified: 2018/10/05 16:23 by swind