LabMice.net - The Windows 2000\XP\.NET Resource Index
Home | About Us | Search

Last Updated December 10, 2003

Terminal Services
  Where to Start
  Book Reviews
  How to Articles
  Install & Configure
  License Server
  Misc. Articles
  Troubleshooting
  Web Resources

 

 

 

 

 

 

 

windows 2000 terminal services icon

Troubleshooting Terminal Services: 
Known Bugs and Issues

This is by no means a comprehensive list of all known bugs and issues, but rather a collection of some the most common issues we've come across. For additional information, please see the Microsoft Support Search page at http://support.microsoft.com 

 

Windows 2000 Terminal Services Issues in an Active Directory Domain Environment
Microsoft Knowledge Base Article: 250776 - Windows 2000 Terminal Services provides increased functionality for Windows 2000 domain environments, and affects all aspects of the domain environment. This article describes the affected areas, and provides links to Microsoft Knowledge Base articles that contain specific troubleshooting steps for those areas. 

Best Practices for Installing and Using Printer Drivers With Windows 2000 Terminal Services
Microsoft Knowledge Base Article: 331055 - This article describes best practices for installing and using printer drivers with Windows 2000 Terminal Services. In Windows 2000 and later, the architecture of printer drivers was changed to unify the interface and add reliability to the server.

Issues When Windows 2000 Loads and Unloads Profile
Microsoft Knowledge Base Article: 289564 - The following issues may occur when a profile is loaded or unloaded on a computer that is running Windows 2000 Terminal Services: 


Access Violation May Occur in Termsrv.exe When You Are Using Time-Outs
Microsoft Knowledge Base Article: 256843 - An access violation may occur in Termsrv.exe when you are using idle connection and disconnected session time-outs. 

Access Violation in win32k!DesktopAlloc with Null Heap Pointer
Microsoft Knowledge Base Article: 273632 - You may receive the following error message on a blue screen on a Windows 2000 Server-based computer that is running Terminal Services: 

Adobe Acrobat .pdf Documents May Not Print Correctly in a Terminal Services Session
Microsoft Knowledge Base Article: 267896 - When you try to print Adobe Acrobat .pdf documents inside of a Terminal Services session, the general page layout may print correctly, the fonts may not print correctly. Instead of characters, you may receive squares in the output. 

A Dr. Watson Error Occurs in Terminal Services Manager
Microsoft Knowledge Base Article: 300228 - An access violation may occur in Terminal Services Manager (Tsadmin.exe). This problem may occur when: You join a Windows 2000-based server to Windows 2000 Active Directory. You start Terminal Services Manager, and permit the computers in the domain. You click various places in the window, and you expand nodes. This problem is caused by an incorrect time string in Tsaadmin.exe

Blank Terminal Services Session After Typing Screen Saver Password
Microsoft Knowledge Base Article: 240060 - Password-protected screen savers in Terminal Services sessions can cause the session to be lost. When the screen saver is activated, you may have to log back on to continue working in the session.

Cannot Automatically Log on Remotely to Terminal Server with Long User Name or Password
Microsoft Knowledge Base Article: 290706 - When you are attempting to automatically log on to a Windows 2000-based computer that is running Terminal Services with an RDP client, the preconfigured user name and password do not allow you to log on. 

Cannot Change File Type Associations at the Terminal Services Console
Microsoft Knowledge Base Article: 250374 - Users (including administrators) at a Terminal Services console are prevented from making any changes to file type associations from within the graphical user interface (GUI). 

Cannot Disconnect Active RAS Connection with Terminal Services Enabled
Microsoft Knowledge Base Article: 237288 - RAS connections are shared by all Terminal Services users who are connected to a Windows 2000 server with Terminal Services enabled. When a user attempts to disconnect a RAS connection that was created in another session, the following error: It is not possible to disconnect at this time. Most likely, this connection is using one or more protocols that do not support Plug-and-Play.  

Cannot Import the Drmapclt.reg File While Installing Drive Share Utility for Terminal Server Client 4.0
Microsoft Knowledge Base Article: 268774 - When you install the Drive Share tool included in the Microsoft Windows 2000 Server Resource Kit on Terminal Server Client 4.0, you may receive the following error message: 

Client Connection Manager for Terminal Services Causes Access Violation in Explorer.exe
Microsoft Knowledge Base Article: 262137 - When you create a connection with Connection Manager for the Terminal Services client and then copy and paste the icon to the desktop, an access violation may occur in Explorer.exe 

Client-Side Caching Shares Not Available for Offline Use Through a Terminal Services Session
Microsoft Knowledge Base Article: 238089 - On a computer running Windows 2000 Server with Terminal Services enabled, files and folders marked for offline use (client-side caching) are not available from within a Terminal Services session or from the server console. 

Closing Terminal Server Client Software Is Treated As A Broken Connection On The Server
Microsoft Knowledge Base Article: 229723 - When you close a Terminal Server client session window, the computer running Terminal Server interprets this as a broken connection instead of a disconnected session.

COM+ and DCOM Errors Using Windows 2000 Terminal Services and Citrix Metaframe 1.8
Microsoft Knowledge Base Article: 263900 - After installing Citrix Metaframe 1.8 on Microsoft Windows 2000, the following error messages appear in the event log.

Console and Terminal Services Access to Dfs Share Ignores Site Preference
Microsoft Knowledge Base Article: 274411 - When you are connected to the console, or in a Terminal Services session, you may be referred to a distributed file system (Dfs) replicant even though the local Dfs share is a closer resource and a better choice. 

Desktop Does Not Load for Any User
Microsoft Knowledge Base Article: 287654 - When any user, including the administrator, attempts to log on at the console of a server running Terminal Services, only the blue background is displayed. The mouse is active, but not the keyboard. 

Error Message: Windows 2000 Is Installed on a Drive Formatted with the OS/2 File System (HPFS)
Microsoft Knowledge Base Article: 270070 - When you upgrade a system running Windows NT 4.0 Terminal Server to Windows 2000, you may receive the following error message after you enter the alphanumeric product key: Windows 2000 is installed on a drive formatted with the OS/2 File System (HPFS). Windows 2000 does not support this file system. You must convert this drive to the Windows 2000 File System (NTFS) before upgrading. This error message occurs even though you do not have any (unsupported) HPFS volumes on the system. 

Error Message: Your Interactive Logon Privilege Has Been Disabled. Please Contact Your System Administrator
Microsoft Knowledge Base Article: 265382 - When you try to establish a terminal server session to a Windows 2000 Terminal Server, you may receive the following error message: 

Event 52 When Starting Terminal Services
Microsoft Knowledge Base Article: 258021 - Clients may not be able to connect to a Windows 2000-based server running Terminal Services, even after you reset the client license registry key as described in following Microsoft Knowledge Base Article:

Event ID 1100 Occurs with Windows 2000 Terminal Services
Microsoft Knowledge Base Article: 268065 - An event ID 1100 may be listed in the system log in Windows NT Event Viewer. This behavior occurs because the spooler service on the server has stopped. 

Event ID 13507, 13552, and 13555 Messages Occur in the Domain Controller
Microsoft Knowledge Base Article: 264607 - In a Microsoft Windows 2000 domain controller with Microsoft Terminal Services installed in application server mode, errors may be displayed in the System event log. Cause: When you install Citrix MetaFrame Server version 1.8 on a Windows 2000 domain controller, you are prompted to re-map the server's drive letters (C-M), so that clients do not confuse their drive C with the server's drive C. When the drive is remapped, File Replication service (FRS) does not work correctly; FRS looks for drive letters that no longer exist. 

Imported Terminal Server Connections Are Put in the Wrong Menu
Microsoft Knowledge Base Article: 228240 - When you import a Terminal Server client connection file using the following command, the connection may be placed in Terminal Server Client menu instead of the Terminal Services Client menu: 

Internal Error 2755 Installing Windows 2000 Resource Kit on a Terminal Server
Microsoft Knowledge Base Article: 255591 - If you install the Windows 2000 Resource Kit on a Windows 2000 Server-based computer running Terminal Services, you may receive the following error message: 

Interix Does Not Work with Windows NT Terminal Server or Windows 2000 Terminal Services
Microsoft Knowledge Base Article: 246442 - When you attempt to use Interix with Windows NT Server 4.0, Terminal Server Edition; Windows NT Server 4.0, Enterprise Edition; or Windows 2000 with Terminal Services installed, the Interix services may not work correctly or may seem to stopped 

Issues When Windows 2000 Loads and Unloads Profile
Microsoft Knowledge Base Article: 289564 - The following issues may occur when a profile is loaded or unloaded on a computer that is running Windows 2000 Terminal Services: 

Local Printer Added to Terminal Services Session Using the RDP Client
Microsoft Knowledge Base Article: 238841 - In Windows 2000, a local printer is automatically added to a Terminal Services client for a Terminal Session. 

Logon Expiration Warning Appears to All Users Currently Logged On
If you log on to Terminal Server and have expired logon-hour restrictions, the logon expiration warning appears to all users who are currently logged on to the Terminal Server whether they are logged on at the console or through a session. 

Logoff Process May Not Be Completed Because Time-Out Is Too Slow 
Microsoft Knowledge Base Article: 299386 - If you configure your Terminal Services server to end (reset) any idle or disconnected sessions after a certain amount of time, you may experience one or more of the following symptoms: 

Narrator Reads Password Aloud in Terminal Services Client
Microsoft Knowledge Base Article: 243243 - Microsoft Narrator is a synthesized text-to-speech utility for users who have low vision. When you are using Narrator, keystrokes that you type are read aloud. When you log on to a Terminal Services server in a Terminal Services client session 

OEM Print Drivers Are Overwritten by Microsoft Drivers That Use Terminal Services Redirect Printing
Microsoft Knowledge Base Article: 270005 - If you have a Windows 2000-based server with Terminal Services enabled that also has the OEM printer drivers, the spooler may stop responding. When the drivers are overwritten, print jobs in the queue become garbled, and must be printed. 

Password Field Has a 14 Character Length Limitation When You Use Connection Manager
Microsoft Knowledge Base Article: 244448 - When you attempt to log on to a Windows 2000-based computer running Terminal Services using automatic log on settings configured in Client Connection Manager, you may receive the following error message: 

Per-Session <Temp> Folders Are Not Available to GPO Logon Scripts While the Logon Scripts Are Running Synchronously
Microsoft Knowledge Base Article: 285138 - By default, a computer that is running Terminal Services creates a separate temporary folder for each new session on the server. If a user has multiple Terminal Services sessions running, each session has a separate temporary folder based on the session identification.

Remote Desktop Protocol Clients Cannot Connect to Terminal Services Server
Microsoft Knowledge Base Article: 270588 - Terminal Services clients may not be able to connect to a Windows 2000-based computer that is running Terminal Services. 

Roaming Profiles and Internet Printing Are Incompatible Because Profiles Are Not Saved
Microsoft Knowledge Base Article: 247574 - When you log off of a Terminal Services session, changes to your roaming profile may not be saved. Also, print jobs that are queued to an Internet printer may not be printed if you log off before the job has been completely spooled to the Internet printer. Print jobs may appear to be hung in the queue on the Terminal Services server. You may also notice a memory leak in the Internet printer port (specifically, Wininet.dll). 

Several Terminal Services CALs Appear to Have the Same Computer Name
Microsoft Knowledge Base Article: 251386 - When you view Terminal Services Licensing Manager, a client computer may appear to have several Terminal Services Client Access Licenses (CALs).

Stop 0x0000001e Error Message in Win32k.sys When Users Log Off Terminal Server 
Microsoft Knowledge Base Article: 302510 - When you log off a Windows 2000-based Terminal Server, you may receive a Stop 0x0000001e error message that references the Win32k.sys file.
 

Stop 0x0000001E Error Message When You Print from a Windows 2000 Terminal Services Client 
Microsoft Knowledge Base Article: 261322 - When you try to print from an RDP client in a Windows 2000 Terminal Services session, you may receive the following error message on a blue screen on the server:
Stop 0x0000001e (0xc0000005, 0xa00372aa, 0x00000000, 0x00000034) 

"Stop 0x1E" or "Stop 0x50" with Terminal Services Client Print Session
Microsoft Knowledge Base Article: 279343 - A Windows 2000-based Terminal Services server may generate a "Stop 0x1E" or "Stop 0x50" error message during a Terminal Services client print session. This may be caused by selecting a particular font in the document that is being printed.

"Stop 0x50 in Win32k.sys" Error Message
Microsoft Knowledge Base Article: 281132 - When you are running Terminal Services with multiple clients (for example, you may have Citrix clients with Citrix Serverfarm), you may receive multiple error messages on blue screens that are related to Win32k.sys. The following error message may be displayed: STOP: 0x00000050 (0xf7f7f7fb, 0x00000000, 0xa0033dd0, 0x00000000) PAGE_FAULT_IN_NONPAGED_AREA address 0xa0033dd0 in Win32K.sys  

Terminal Services Client Disconnected Immediately
Microsoft Knowledge Base Article: 237792 - When a Terminal Services client attempts to connect, the client may be disconnected immediately with the following error message:

Terminal Services Client Is Not Updated When Service Pack 1 Is Installed
Microsoft Knowledge Base Article: 296721 - The Windows 2000 Terminal Services client computer is not updated when you install Windows 2000 Service Pack 1 (SP1) 

Terminal Services Clients Always Prompted for Password
Microsoft Knowledge Base Article: 247174 - You can use the Terminal Services Client Connection Manager software to specify a user name, password, and domain name that are used whenever a user starts a specific connection. This feature eliminates the need for the user to type his or her credentials at each connection attempt. 

Terminal Services Client Cannot Connect to a Server Running 128-bit Encryption
Microsoft Knowledge Base Article: 257894 - You may be unable to connect to a Terminal Services computer that is running 128-bit encryption and has its Remote Desktop Protocol (RDP) encryption level set to High. 

Terminal Services Performance Problem Because of Contention on CmpRegistryLock 
Microsoft Knowledge Base Article: 317357 - When 50-100 interactive Terminal Services users are logged on, and other Terminal Services users are logging on or off at the same time, your computer may become irresponsive for about 10-30 seconds. The frequency of this symptom is variable, but can occur 10-20 times a day. When this problem occurs, the mouse and keyboard do not respond, but the computer is responsive on the network (to ping and net use commands), and on the console. 

Terminal Services Server Does Not Restart with Restart Command from a Client Session
Microsoft Knowledge Base Article: 265419 - When you attempt to restart a Windows 2000-based Terminal Services server from a client session by clicking Shut Down, and then clicking Restart, the server may not restart. Instead, it may shut down. 

Terminal Services Client Roaming Profile Is Inconsistent or Overwritten
Microsoft Knowledge Base Article: 243535 - When you are using the same roaming profile for a Windows client and a Terminal Services client, the profile may be inconsistent or overwritten. Configuration changes made on the local Windows desktop can overwrite changes made in the Terminal Services. 

Terminal Services Fields Are Not Duplicated When Copying an Existing User
Microsoft Knowledge Base Article: 243551 - When you select and copy an existing user in the Active Directory Users and Computers snap-in, Terminal Services fields (such as the Terminal Services profile path and home directory) are not copied to the new user account.

Terminal Services Home Folder Has Incorrect Permissions for Windows NT 4.0 Target Server
Microsoft Knowledge Base Article: 289677 - When you specify a Terminal Services home folder by using the Active Directory Users and Computers snap-in, Windows automatically creates the home folder for you. If the server that contains the folder is a Microsoft Windows NT 4.0-based server, the user does not have access to the folder. This works correctly for a Windows 2000 target server. 

Terminal Server Printer Redirection Not Signaled on Printer Device Settings Change Notification
Microsoft Knowledge Base Article: 243942 - When you connect to a Windows 2000 computer with Terminal Services installed, any locally-attached client printers are automatically created for each Terminal session. Also, the printer configuration information is cached on the Terminal Server computer during logon so that the server does not have to obtain the settings from the client each time the printer is used. 

Terminal Server Profile Path and Home Directory Are Ignored When You Log On to a Kerberos Realm
Microsoft Knowledge Base Article: 299968 - When you log on to a Kerberos realm, the terminal server profile path and home directory may be ignored. Instead, the terminal server logon may use the regular roaming profile, and this may cause problems with profile consistency. 

Terminal Services Server Does Not Restart with Restart Command from a Client Session
Microsoft Knowledge Base Article: 265419 - When you attempt to restart a Windows 2000-based Terminal Services server from a client session by clicking.. 

Terminal Services Server Switches to Install Mode for Users When Running RunOnce Entries
Microsoft Knowledge Base Article: 266783 - When you are running Terminal Services in Application Server mode, users may sporadically lose settings, or settings from one user may appear in another user's profile. 

Terminal Services Sessions Are Disconnected Because of a Decryption Error 
Microsoft Knowledge Base Article: 311371 - If you are running Windows 2000 as a Terminal Services server and the client sessions are encrypted, clients may intermittently lose their connection. When this occurs, entries similar to the following entry are recorded in the System event log. 

Terminal Services Temporary Folder Configuration Is Stored in Multiple Registry Locations
Microsoft Knowledge Base Article: 243555 - A Windows 2000-based computer running Terminal Services creates, by default, a temporary folder under the %TEMP% folder for each client session. The name of this temporary folder is based on the hexadecimal representation of the session ID.

Tsadmin.exe May Hang After Connecting to Multiple Servers 
Microsoft Knowledge Base Article: 291041 - When SMB signing is enabled on all of your servers that are running Terminal Services and you are using the Terminal Services Manager utility (Tsadmin.exe) to run administrative tasks on these servers, Tsadmin.exe may stop responding (hang) 

TsInternetUser Password Is Changed Daily
Microsoft Knowledge Base Article: 244057 - The following event may be logged daily on a Windows 2000-based server with Terminal Services and auditing for successful account management enabled: 

Unable to Completely Disconnect a Terminal Server Connection
Microsoft Knowledge Base Article: 216783 -
After a Terminal Server client loses the connection to a Terminal Server, the session on the Terminal Server may not transition to a disconnected state, instead, it may remain active even though the client is physically disconnected from the Terminal.If the client logs back in to the same Terminal Server, a totally new session may be established, and the original session may still remain active.

Uninstalling Windows 2000 Service Pack 1 Does Not Replace Terminal Services Files
Microsoft Knowledge Base Article: 265820 - After you install Terminal Services from Windows 2000 Service Pack 1 (SP1) on a computer that is running Windows 2000 Server SP1 without Terminal Services and Terminal Services Licensing installed, and then uninstall Windows 2000 SP1, the the following Terminal Services files are not replaced: Conman.exe, Mstsce.exe, Tsctrc.dll, Iserver.exe 

Users Unable to Log On Locally to Terminal Services Computer
Microsoft Knowledge Base Article: 258067 - Users may be unable to log on locally to a Windows 2000-based server with Terminal Services installed, even though they have Log On Locally permissions. In addition, the following error message may be displayed: 

User Is Able to Remote Control a Terminal Services Session After Removing the Permission
Microsoft Knowledge Base Article: 235484 - After an administrator removes the Remote Control permission for a user and/or group on an RDP-TCP connection on a Windows 2000 Terminal Server computer, the user and/or group continues to have the ability to remote control sessions that were established prior to the change. The inverse of this is true as well. After an administrator adds the Remote Control permission for a user and/or group on an RDP-TCP connection on a Windows 2000 Terminal Server computer, the user and/or group is not able to remote control sessions that were established prior to the change. 

Userinit.exe May Stop Working in Windows 2000
Microsoft Knowledge Base Article: 331490 - When users log on from a terminal session, Userinit.exe may stop working. 

VBScript Error Message Occurs When You Use Terminal Services Advanced Client
Microsoft Knowledge Base Article: 282128 - When you connect to a server that is running Windows 2000 Terminal Services by using Terminal Services Advanced Client (TSAC), you may receive the following error message: VBScript: Error connecting to terminal server: Servername 

Version Information in Registry Does Not Reflect Slipstreamed Upgrade to Windows 2000 Server SP1
Microsoft Knowledge Base Article: 289215 - After you use a slipstreamed installation to upgrade a computer from Windows NT 4.0, Terminal Server Edition, to Windows 2000 Server Service Pack 1 (SP1), the version information in the registry may not show that SP1 is installed. This behavior raises issues for programs that require installation of SP1. 

Windows 2000 Terminal Services Does Not Redirect Network Printers
Microsoft Knowledge Base Article: 264039 - In Windows 2000 Terminal Services you can redirect clients' local printers when they log on to a Terminal Services session with the Microsoft RDP 5 Terminal Services client. The redirection of local printers is a default behavior. 

Windows 2000 Terminal Services Does Not Support Outlook Offline Storage 
Microsoft Knowledge Base Article: 242195 - When you add a Microsoft Exchange server to a Microsoft Outlook profile, you are not prompted as to whether or not you travel with the computer. When you view or modify the properties for the Microsoft Exchange Server service, the Offline settings on the Advanced tab are not present. 

Windows 2000 Terminal Services Server Hangs with the Novell Client 
Microsoft Knowledge Base Article: 327350 - A Windows 2000-based server may stop responding (hang) if a process creates a new process and creates or closes a desktop at the same time. This problem has occured when Novell's client and Citrix Metaframe are running on the same server. This problem also occurs with Telnetd.exe. Other software may also trigger this problem.

Windows 2000 Terminal Services Incorrectly Closes Files on Remote Shares 
Microsoft Knowledge Base Article: 272582 - You may receive one or more of the following error messages when multiple users on a Terminal Server work with the same files that are located on a network share: 

Windows 2000 Terminal Services Server Logs Events 1111, 1105, and 1106
Microsoft Knowledge Base Article: 239088 - Windows 2000 Terminal Services supports the automatic redirection of printers that are configured to use local ports (such as LPT1, LPT2, or LPT3) on computers that have open client sessions through the Remote Desktop Protocol (RDP) 5 client 

Windows XP Clients Cannot Connect to a Windows 2000 Terminal Services Server
Microsoft Knowledge Base Article 323597 - When you try to connect from a Windows XP-based client to a Windows 2000-based Terminal Services server, the connection may not succeed and you may receive the following error message: Because of a security error, the client could not connect to the terminal server. After making sure that you are logged on to the network, try connecting to the server again. This error message may occur when you try to connect from a Windows XP-based client to some or all of the Windows 2000-based Terminal Services servers in your organization, or the error message may not occur at all.

 

Entire contents
© 1999-2003 LabMice.net and TechTarget
All rights reserved

This site and its contents are Copyright 1999-2003 by LabMice.net. Microsoft, NT, BackOffice, MCSE, and Windows are registered trademarks of Microsoft Corporation. Microsoft Corporation in no way endorses or is affiliated with LabMice.net. The products referenced in this site are provided by parties other than LabMice.net. LabMice.net makes no representations regarding either the products or any information about the products. Any questions, complaints, or claims regarding the products must be directed to the appropriate manufacturer or vendor.