User Tools

Site Tools


faq:bad_behaviour_no_terminals_available

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
faq:bad_behaviour_no_terminals_available [2007/01/31 15:16 (17 years ago)] clifffaq:bad_behaviour_no_terminals_available [2007/02/01 19:41 (17 years ago)] (current) – Fixed pervasive 116 link lawrence
Line 1: Line 1:
-====== Status 116 ====== +====== No Terminals Available for selection ====== 
-===== Definition ===== + 
-116: The file is owned by another Microkernel engine acting as a Gateway + 
 +===== Information / Common Issues ===== 
 +There are a few reasons that terminals might not show in the list. 
 +  * The most obvious is that they are in use 
 +  * The terminal is hung in Pervasive 
 +  * Insufficient permissions to access that network resource 
 +  * Firewall software blocking the connection 
 + 
 + 
 +===== No Terminals Available for selection #1 ===== 
  
-The MicroKernel cannot contact the engine running on the gateway computer even though it can read the locator file. This might occur the following reasons: ... (Continued within the Pervasive Help File) 
  
-===== No Terminals Available for selection ===== 
 ==== Problem ==== ==== Problem ====
-Customer could not open System Five from 1 client terminal. The original issue was a [[:faq:Status 116 error on Master.btr]]+Customer could not open System Five from 1 client terminal. The original issue was a [[faq:pvsw-errors:status_116|Status 116 error on Master.btr]] 
 ==== Troubleshooting steps ==== ==== Troubleshooting steps ====
   - Looked at security, but the station had only had windows updates done recently and been connected to the internet   - Looked at security, but the station had only had windows updates done recently and been connected to the internet
Line 17: Line 26:
 ==== Cause ==== ==== Cause ====
   * The error was caused by the firewall on the server having been configured to block TCP/IP traffic from the client PC   * The error was caused by the firewall on the server having been configured to block TCP/IP traffic from the client PC
 +
  
  
 ==== Resolution ==== ==== Resolution ====
 We turned off the Firewall and everything worked. We turned off the Firewall and everything worked.
 +  - Ordered List Item
 +  - Enable NetBios over TCP/IP
 +  - Remove any bad hosts file entrys in c:\windows\system32\drivers\etc\hosts
 +  - Set TCP/IP timeouts to avoid the two hour delay (see article...)
 +  - Ensure that Name Resolution (DNS) is working properly by pinging Pervasive server by DNS name and correct IP is returned
 +  - Ensure System has R/W access to data files
  
  
  
faq/bad_behaviour_no_terminals_available.1170285383.txt.gz · Last modified: 2007/01/31 15:16 (17 years ago) by cliff