Very Slow Logoff times

[Guest]

I have a terminal server running on windows server 2003 that on which it
takes around 10 minutes for a user to logoff. There is nothing reported in
the event log. I have set the server to have verbose messenging on logon and
logoff and it seems to hang at "Executing:
C"\windows\system32\wlnotify.dll..."

It then sits there for about 10 minutes, before it finishes logging off.

If you disconnect, and then reconnect later, it will still be in the process
of logging off.

I am rather stumped. Any help would be great.

Matt

 

[Vera Noest [MVP]]

How many printers do you redirect in the session? Check this:

828326 - It takes longer than you expect to log off from a Terminal
Services session in Windows 2000 or Windows Server 2003
http://support.microsoft.com/?kbid=828326

You can also turn on debug logging:

221833 - How to enable user environment debug logging in retail
builds of Windows
http://support.microsoft.com/?kbid=221833

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
___ please respond in newsgroup, NOT by private email ___

 

[Guest]

It doesn't seem to be related to the printers. Logoff times do not seem to
be affected if I diable printer mappings, or stop the spooler service.

I will try enabling the debug logging and see where I get with that next.
Thanks for that tip.

Matt

 

[Guest]

As suggested by Vera Noest, I enabled user enviroment debugging on the
terminal server. What I did specificlly is that I made the change in the
registry, and then logged on as myself. I then moved that log file, and
logged off.

what I noticed while it was logging off is that the userenv.log file was not
created until the very end of the 10 minute wait that it took to logoff from
the server. Below is what was included in the logfile after I was finished
logging off.

I am not finding anything usefull in this logfile, maybe someone else will.


USERENV(152c.10e8) 10:54:51:256 UnloadUserProfile: Entering, hProfile =
<0x2c8>
USERENV(152c.10e8) 10:54:51:256 UnloadUserProfile: no thread token found,
impersonating self.
USERENV(152c.10e8) 10:54:51:256 GetInterface: Returning rpc binding handle
USERENV(238.cc8) 10:54:51:256 IProfileSecurityCallBack: client authenticated.
USERENV(238.cc8) 10:54:51:256 DropClientContext: Got client token 000008DC,
sid = S-1-5-18
USERENV(238.cc8) 10:54:51:256 MIDL_user_allocate enter
USERENV(238.cc8) 10:54:51:256 DropClientContext: load profile object
successfully made
USERENV(238.cc8) 10:54:51:256 DropClientContext: Returning 0
USERENV(152c.10e8) 10:54:51:256 UnLoadUserProfile: Calling DropClientToken
(as self) succeeded
USERENV(238.1584) 10:54:51:256 IProfileSecurityCallBack: client authenticated.
USERENV(238.1584) 10:54:51:256 UnloadUserProfileP: Entering, hProfile =
<0x8cc>
USERENV(238.1584) 10:54:51:256 UnloadUserProfileP: ImpersonateUser
<000008dc>, old token is <00000000>
USERENV(238.1584) 10:54:51:256 GetExclusionListFromRegistry: Policy list is
empty, returning user list = <Local Settings;Temporary Internet
Files;History;Temp>
USERENV(238.1584) 10:54:51:256 CSyncManager::EnterLock
<S-1-5-21-746137067-1614895754-682003330-1164>
USERENV(238.1584) 10:54:51:256 CSyncManager::EnterLock: No existing entry
found
USERENV(238.1584) 10:54:51:256 CSyncManager::EnterLock: New entry created
USERENV(238.1584) 10:54:51:256 CHashTable::HashAdd:
S-1-5-21-746137067-1614895754-682003330-1164 added in bucket 9
USERENV(238.1584) 10:54:51:256 UnloadUserProfileP: Wait succeeded. In
critical section.
USERENV(238.1584) 10:54:51:256 UnloadUserProfileP: Didn't unload user
profile, Ref Count is 3
USERENV(238.1584) 10:54:51:256 UnloadUserProfileP: About Reverted back to
user <00000000>
USERENV(238.1584) 10:54:51:256 CSyncManager::LeaveLock
<S-1-5-21-746137067-1614895754-682003330-1164>
USERENV(238.1584) 10:54:51:256 CSyncManager::LeaveLock: Lock released
USERENV(238.1584) 10:54:51:256 CHashTable::HashDelete:
S-1-5-21-746137067-1614895754-682003330-1164 deleted
USERENV(238.1584) 10:54:51:256 CSyncManager::LeaveLock: Lock deleted
USERENV(238.1584) 10:54:51:256 UnloadUserProfileP: Leave critical section.
USERENV(238.1584) 10:54:51:256 UnloadUserProfileP: Leaving with a return
value of 1
USERENV(238.1584) 10:54:51:256 UnloadUserProfileI: returning 0
USERENV(152c.10e8) 10:54:51:256 UnloadUserProfile: Calling
UnloadUserProfileI succeeded
USERENV(238.11a4) 10:54:51:256 IProfileSecurityCallBack: client authenticated.
USERENV(238.11a4) 10:54:51:256 ReleaseClientContext: Releasing context
USERENV(238.11a4) 10:54:51:256 ReleaseClientContext_s: Releasing context
USERENV(238.11a4) 10:54:51:256 MIDL_user_free enter
USERENV(152c.10e8) 10:54:51:256 ReleaseInterface: Releasing rpc binding handle
USERENV(152c.10e8) 10:54:51:256 UnloadUserProfile: returning 1

 

[Guest]

The problem ended up being with the SMS client being installed. I am not
exactly sure on the details of what was wrong, but I know that removing the
sms client from the server fixed the problems with our logoff times.

FYI

ROllo