This is a collection of calls that were made to the Tech Support Center. These were posted to help show some of the problems and solutions people have faced when deploying ThinManager Ready thin client systems.
The problems have been summarized and the names have been deleted to protect the innocent.
| 7/11/2007 | Problem: Shadowing won't connect, often shows a "Client may already be shadowed" message, and ThinManager is slow. Solution: Check the size of the thinserver service in the Task Manager Processes list. The thinserver service should be 15,000 - 50,000 K in size, depending on the number of clients. In this case the thinserver had grown to over 200,000 K and was growing hourly. This was because of a memory leak in the Microsoft RPC (Remote Procedure Call) service. Since the thinserver service relies on the RPC, the memory leak is reflected in the size of thinserver. The customer patched their terminal servers as described in Microsoft's Knowledge Base article KB911262 and the problem was resolved. This issue is fixed in Windows 2003 Service Pack 2. |
| 5/21/2007 | Problem: Terminal won't connect to the terminal server. The message window in the upper left corner of the terminal's splash screen says "Connecting to server X. Unable to connect to Server X". Solution: The issue is with Microsoft licensing. Either the terminal server cannot contact the Terminal Server Licensing Server or there are no Terminal Server Client Access Licenses (TS CALs) available. It you check the event log/event viewer on the terminal server it will list an error like "Error 1004: The terminal server cannot issue a client license." |
| 5/17/2007 | Problem: Terminal logs off on a regular basis. Solution: Each Windows 2003 user account has a default secure screen saver that locks the session after 10 minutes and requires a re-login. This can be turned off for each individual account on the Screen Saver tab of the Display Properties. |
| 5/16/2007 | Problem: Terminal is in a different time zone than the terminal server. The Time Zone Redirection module was used to set the terminal time zone but it isn't working. Solution: The Time Zone Redirection module requires a change in the Local Group Policy to work. Type gpedit.msc at a command prompt. Enable the Allow Time Zone Redirection setting under Computer Configuration| Administrative Templates| Windows Components| Terminal Services| Client/Server data redirection|Allow Time Zone Redirection. |
| 5/3/2007 | Problem: New NTA-6020 terminal doesn't show up in ThinManager 2.6 Solution: As new hardware is added to the ThinManager Ready list, the TermCap Database is updated to add the new units. Updating the TermCap database will add the unit to the list. |
| 5/3/2007 | Problem: The video settings of a terminal were grayed out and couldn't be changed. Solution: The terminal was in a group and the video settings had the Group Setting checked, making that setting the default setting for all members of the group. To change the terminal setting one would have to change the group setting. |
| 5/2/2007 | Problem: Terminal locked up and quit displaying data. It doesn't failover even though it quit working. Solution: The application in the session lost connection to the PLC and locked up. The terminal will only display what the terminal server is producing. If the session has turned to mud, the terminal will display mud. Leave the terminal alone and kill the session on the terminal server. The terminal will reconnect, start a new session, and the session should be working properly. |
| 4/19/2007 | Problem: User wants to move a terminal but it keeps coming up as its original configuration. Solution: In ThinManager 3.0, a terminal can have its Terminal ID cleared so that it can be re-assigned another identity. Turn off the unit and open the Terminal Configuration Wizard. Select the Clear button next to the Terminal ID on the Terminal Hardware page of the configuration wizard. |
| 3/1/2007 | Problem: ThinManager doesn't show the properties of two terminals. Solution: The system was set up with 2 ThinManager Servers. While first installing the system, 2 terminals booted from the secondary ThinManager Server instead of the primary ThinManager Server so the properties were displayed on the secondary ThinManager Server and not the primary ThinManager Server. They needed to reboot the terminals, get them defined on the primary ThinManager Server with the others, then synchronize the configurations to the secondary ThinManager Server. |
| 2/10/2007 | Problem: While testing a pilot project the terminals keep losing and regaining their session. Solution: All the terminals were using a single login. Windows 2003 terminal server allows a single login per user so one session was getting passed back and forth between all the terminals. Once each terminal logged in with a unique login the problem stopped. |