|
|
- check the EventLog on your server.
More often then not, there is useful information to be found there
- search one or more of the databases mentioned below for the EventID and Source of the events you found
- if at all possible, create a test system which demonstrates the same problem and do all of your troubleshooting there
- document the problem
- enable verbose logging of relevant services, if possible (see links below)
- if the server reboots, configure it to not automatically restart after a system failure. Document the STOP error code and all parameters when the system crashes
- try to narrow down the problem: does it happen all the time? to all users? with all workstations / applications / printers?
You will need to provide this information if you are going to post your problem to a newsgroup or phone a vendor's support
- document all changes that you make while troubleshooting
- make only one change at a time, evaluate the results, and reverse the change if it doesn't solve the problem
|
Troubleshooting tools
KnowledgeBase
Event Logging
Debugging tools
General TS related issues
- 956438 - A Windows Server 2003-based or Windows Server 2008-based terminal server stops accepting new connections, and existing connections stop responding
- 278657 - Terminal Services Cannot Be Manipulated applies to W2K and 2003, not to 2008
- 252330 - Toggling Terminal Services to Application Server Mode May Cause Programs Not to Work
- 828056 - A terminal server no longer runs in application mode after you upgrade the terminal server to Windows Small Business Server 2003
Windows 2008 specific issues
STOP errors
- 951954 - Error message when you run an application on a terminal server that is running Windows Server 2008 or Windows Vista with Service Pack 1: "Stop 0x0000008E"
- 951149 - Stop error on a Windows Server 2008-based terminal server when the server is running under a heavy load: "0x0000000A"
- 952610 - You cannot investigate a Stop error that occurs on an x64-based version of Windows Server 2008
- 953341 - A dump file may not be generated on a computer that is running Windows Server 2008 or Windows Vista if the dump file and the paging file reside on the same volume
- 958944 - A Windows Server 2008-based server that is running the Terminal Server role reports a Stop error when you control a session remotely from inside a session that is already being controlled remotely: "0x00000050"
- 966319 - During user logon or logoff, you receive stop error code 0x00000050, and the system restarts automatically on a computer that is running Windows Server 2008 or Windows Vista SP1
- 955076 - Stop error message on a Windows Vista or Windows Server 2008-based computer that has multiple processors installed: "STOP: 0x00000101 CLOCK_WATCHDOG_TIMEOUT"
- 979557 - Stop error on a terminal server that is running a 64-bit version of Windows Server 2008 when a user remotely controls another terminal server session: "STOP: 0x0000007E"
Misc. problems
- 969445 - Previous versions disappear after installing Terminal Services role
- 980568 - A terminal server that is running Windows Server 2008 stops responding when lots of clients make terminal sessions to the server
- 952664 - The Event Log service may stop responding because of a deadlock on a Windows Server 2008-based computer
- 946399 - The Terminal Services service may be unable to start on a server that is running Windows Server 2008
- 950086 - A memory leak may occur in the nonpaged pool memory on the Windows Server 2008-based terminal server when you log on to and log off from a Windows Server 2008-based terminal server through an RDP connection
- 949914 - Citrix ICA clients may crash when they are connecting to a Windows Server 2008-based terminal server that has Citrix Presentation Server installed
- 958652 - Some Citrix commands do not work correctly in Citrix XenApp 5.0 for Windows Server 2008
- 958092 - After the Terminal Services mirror driver is disconnected from a Windows Server 2008-based or Windows Vista-based remote computer, you receive a Stop error on the remote computer: "Stop 0x0000007E SYSTEM_THREAD_EXCEPTION_NOT_HANDLED"
Windows 2003 specific issues
STOP errors
- 959828 - Stop error on a Windows Server 2003 SP2-based terminal server when users print documents in terminal sessions: "0x0000008E" or "0x00000050"
- 960652 - Stop error when you copy a file from a redirected disk to a Windows Server 2003-based terminal server in a terminal server session: "0x0000007E"
- 909445 - Error message when you start a Terminal Services session on a Windows Server 2003-based computer: "STOP: 0x00000050 (0xffffffe8, 0x00000001, 0x8083fb88, 0x00000000)"
- 926128 - You receive a "STOP 0x50" error message that is related to win32k!HmgDecrementShareReferenceCount+0xb on a Windows Server 2003-based terminal server
- 982362 - "Stop 0x000000AB (SESSION_HAS_VALID_POOL_ON_EXIT)" error when a client logs off from a terminal server session in Windows Server 2003 SP1 or in Windows Server 2003 SP2 replaces all previous STOP 0xAB hotfixes
- 958820 - A Windows Server 2003-based computer restarts unexpectedly and you receive a Stop error message during the terminal session logoff process: "0x0000008E KERNEL_MODE_EXCEPTION_NOT_HANDLED"
- 961799 - A Stop error occurs on a Windows Server 2003-based server when a user accesses shared files on the server by using an SMB connection
- 978243 - A terminal server that is running Windows Server 2003 Service Pack 2 restarts unexpectedly with various stop codes after you install hotfix 971280 or newer Windows Kernel Binaries
Misc. problems
- 979522 - A Windows Server 2003-based terminal server stops responding after many users log on to it and log off from it system paged pool is empty
- 960092 - A Windows Server 2003-based terminal server that also runs Citrix MetaFrame Presentation Server may crash every few days, and you may receive a gray screen when you log on to the terminal server
- 910617 - When you try to restart or shut down a remote Windows XP-based or Windows Server 2003-based computer, the restart or shutdown process may stop responding (hang) if a screen saver is enabled on the remote computer
- 957492 - When you try to start a terminal session to a Windows Server 2003-based computer, the computer may be unresponsive
- 883670 - FIX: The Terminal Services service stops responding in Windows Server 2003 and you receive an "The RPC service is unavailable" error message when you try to connect to the terminal server by using the Remote Desktop Connection program
- 930045 - A Windows Server 2003-based computer stops responding when you shut down the computer in a remote console session
- 956341 - A Windows Server 2003-based computer becomes unresponsive because of a large memory allocation request
- 906510 - The logon screen turns black after you press CTRL+ALT+DELETE to log on to a Microsoft Windows Server 2003-based computer
- 932039 - Two taskbars are displayed, or the Language bar is displayed two or more times on the taskbar, on a computer that is running Windows Server 2003 or Windows XP
- 914052 - Event ID 10000 is logged in the Application log on a Windows Server 2003-based computer that has Terminal Server enabled
- 932813 - Event ID number 2003 is logged in the Application log after you install Windows Server 2003 Service Pack 2
- 891315 - You cannot see all the screen element text if you use the large size (120 DPI) display DPI setting on a Windows Server 2003 Terminal Server
- 967587 - The methods in the ISensLogon2 interface returns incorrect session IDs for sessions when an application uses this interface to handle logon events
- 942490 - When you connect to a Windows Server 2003-based computer in a terminal server session, the remote computer may stop responding if it has East Asian languages installed
Windows 2000 specific issues
STOP errors
- 839429 - You receive a "STOP: 0x0000001E" error message on a Windows 2000-based computer that is running Terminal Services
- 899268 - You may receive error messages and you may receive frequent Stop error messages that indicate that the Srv.sys or the Netbt.sys driver has failed when you use Terminal Services to connect to a computer that is running Windows 2000 Server
- 901198 - Error message when you use the Terminal Server application on a computer that is running Windows 2000: “Stop 1E, {c0000005, a0109ba0, 0, a0cd3584}”
- 894388 - Error message on a Windows 2000 Server-based computer that has Terminal Services enabled: "Stop 0x0000001E"
- 820767 - Your computer automatically restarts or a stop error or another error occurs when you have Terminal Services enabled
Misc. problems
- 817446 - Terminal Services Stops Responding
- 323148 - Windows 2000 Server or Windows 2000 Advanced Server Computer That Is Running Terminal Services Stops Responding Immediately After You Start the Computer
- 899330 - A Windows 2000-based terminal server stops responding under a heavy load, and all users lose their terminal server sessions
- 823747 - Windows 2000 Terminal Server Stops Responding and a Black Screen Appears
- 837439 - Windows 2000 Terminal Server stops responding after you experience access violations in a Terminal Server session
- 832821 - Error 161 occurs when you use the runas command in a Terminal Services session
- 830268 - NUM LOCK and CAPS LOCK keys are out of sync when you shadow another RDP session in Windows 2000
- 893368 - Terminal services and remote desktop session events are not logged in Windows 2000 Server
- 891503 - FIX: You may receive a "Permission Denied" error message when you try to use the ls or cd command from a Terminal Services session
- 837810 - When you use Remote Desktop Connection (RDC) to connect to a Windows 2000-based terminal server, you cannot minimize a program that has stopped responding in the RDC window
Citrix specific issues
- CTX122827 - Critical Tool Matrix for XenApp Environments
- CTX106727 - Brief Troubleshooting Guide
- CTX113035 - Microsoft Windows Server 2003 Service Pack 2 Known Issues
- CTX102026 - STOP 0x1E in Ntkrnlmp.exe when running the Citrix Management Console from FR3 with an ATI display driver
- CTX103253 - IMA service failed to start with error 2147483649 and failed to load plug-ins MF XP 1.0
- CTX122690 - Discovery Does Not Run Successfully after Restarting the Server
- 816134 - Citrix Terminal Server Sessions Are Not Disconnected and Cause the Server to Stop Responding
- 951032 - You may receive an error message on a Windows Server 2003-based computer that has Citrix Presentation Server 4.0 installed with Windows Installer
- 951033 - Stop error message on a Windows Server 2003-based computer that has Citrix Presentation Server 4.5 installed: "0x00000076" or "0x000000CB"
|
