Want to win a PS4? Go Premium and enter to win our High-Tech Treats giveaway. Enter to Win


session stack in Terminal server when logginh off

Posted on 2011-03-06
Medium Priority
Last Modified: 2012-05-11

recetly sometimes the users session in terminal is stack in the loggng-off proccess.

only force dissconecting the session clearing up the session, what can be the cause(win 2003 R2)?

Question by:ymg800
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 4
  • 3
  • 2
  • +2
LVL 10

Expert Comment

ID: 35046568
can you post the event logs, and also check the processor and memory usage,
LVL 10

Expert Comment

ID: 35046583
Also make sure that there are extra startup applications or services, normally it hangs because when windows is unable to close an application which in turn is accessed by system but initiated by terminal user.
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.


Author Comment

ID: 35056152

here are the even logs, nothing suspicuse there:(the event occures at 3 pm)

memory and cpu are ok as well..
there user didnt opened any program in the session just tested log-in and off and it stucked...

about the artical, it's saying to "obtain the latest service pack for Windows NT Server version 4.0"

but i have win 2003 r2 so not relevant...

what can i check more?

LVL 18

Accepted Solution

John Gates, CISSP earned 2000 total points
ID: 35171817
This will give you the reason for the issue:

You may want to turn on debug logging to troubleshoot - 221833 - How to enable user environment debug logging in retail builds of Windows
LVL 80

Expert Comment

ID: 35171848
If you do not have User Profile hive cleanup, get it and it should resolve your issue on the win2k3.
LVL 18

Expert Comment

by:John Gates, CISSP
ID: 35171859
That needs to be installed on the server.  I would still also recommend turning on the logging in case you have an application that is having trouble closing that is not involved in a user profile.


Author Comment

ID: 35224993
dimante, u mean to turn on logg-ng debugging?
LVL 18

Expert Comment

by:John Gates, CISSP
ID: 35226198
From the article:

Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
322756  How to back up and restore the registry in Windows

Use Registry Editor to add or to modify the following registry entry:
Subkey: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Winlogon
Entry: UserEnvDebugLevel
Value data: 10002 (Hexadecimal)
UserEnvDebugLevel can have the following values:
NONE 0x00000000
NORMAL 0x00000001
VERBOSE 0x00000002
LOGFILE 0x00010000
DEBUGGER 0x00020000
The default value is NORMAL|LOGFILE (0x00010001).

Note To disable logging, select NONE (0x00000000).

You can combine these values. For example, you can combine VERBOSE 0x00000002 and LOGFILE 0x00010000 to get 0x00010002. Therefore, if UserEnvDebugLevel is given a value of 0x00010002, LOGFILE and VERBOSE are both turned on. Combining these values is the same as using an OR statement.
0x00010000 OR 0x00000002 = 0x00010002
Note If you set UserEnvDebugLevel to 0x00030002, the most verbose details are logged in the Userenv.log file.

The log file is written to the %Systemroot%\Debug\UserMode\Userenv.log file. If the Userenv.log file is larger than 300 KB, the file is renamed Userenv.bak, and a new Userenv.log file is created. This action occurs when a user logs on locally or by using Terminal Services, and the Winlogon process starts. However, because the size check only occurs when a user logs on, the Userenv.log file may grow beyond the 300 KB limit.

Although the 300-KB limit cannot be modified, you can set the read-only attribute on the Userenv.bak file, and the Userenv.log file will grow indefinitely. You must only use this method temporarily, remove the read-only attribute on the Userenv.bak file as soon as you are finished troubleshooting.
Back to the top
Note This is a "FAST PUBLISH" article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use for other considerations.

Author Comment

ID: 35238766
is there a simpler way?

nothing can be writen in the system logs?

thanks a head.
LVL 18

Expert Comment

by:John Gates, CISSP
ID: 35240476
Unfortunately it is not a simple problem.  There are so many things it could be there is no way without logging the interactions to see where the problem is.


Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Background Information Recently I have fixed file server permission issues for one of my client. The client has 1800 users and one Windows Server 2008 R2 domain joined file server with 12 TB of data, 250+ shared folders and the folder structure i…
During and after that shift to cloud, one area that still poses a struggle for many organizations is what to do with their department file shares.
In this tutorial you'll learn about bandwidth monitoring with flows and packet sniffing with our network monitoring solution PRTG Network Monitor (https://www.paessler.com/prtg). If you're interested in additional methods for monitoring bandwidt…
In this brief tutorial Pawel from AdRem Software explains how you can quickly find out which services are running on your network, or what are the IP addresses of servers responsible for each service. Software used is freeware NetCrunch Tools (https…

609 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question