[THIN] Re: Session disconnects not removing
- From: Mark Cook <mc@xxxxxxxxxx>
- To: "'thin@xxxxxxxxxxxxx'" <thin@xxxxxxxxxxxxx>
- Date: Thu, 5 Aug 2004 08:59:38 +0100
Jennifer,
Sorry, I slightly confused myself with the first question so fired the
second just to be sure. Anyway, if you look at the state of the session
(eg. QUSER) what state is the session reporting once it's hung ? Does it
still report DISC or is it something else like DOWN ???
Mark
-----Original Message-----
From: Henske, Jennifer [mailto:Jennifer.Henske@xxxxxxxxxxxxx]
Sent: 04 August 2004 18:23
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: Session disconnects not removing
I understood what you were asking.
I just spent the last 30 minutes running Sysinternals Process Explorer. If
I close all processes running for a user, except winlogon, the disconnect
still sticks and all the threads under that process are in a wait state. I
not real clear what I'm looking at in this tool, but nothing jump out as
the culprit.
Jennifer Henske
From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx]
Sent: Wednesday, August 04, 2004 10:39 AM
To: 'thin@xxxxxxxxxxxxx'
Subject: [THIN] Re: Session disconnects not removing
I'll rephrase the question, is the process under WinLogon always the same
(just a random EXE name you don't know of) or is it a different EXE each
time (ie. Depending on what the user was doing?)
-----Original Message-----
From: Henske, Jennifer [mailto:Jennifer.Henske@xxxxxxxxxxxxx]
Sent: 04 August 2004 15:58
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Session disconnects not removing
Interesting problem with Terminal Server 2003. We have an 2003 AD group
policy set to remove disconnects after 15 minutes. Sporadically, we have
sessions hang that are not removed via the policy. We noticed the problem
on our 2003 XP FR3 servers, but have duplicated the problem on a plain 2003
TS server via RDP. Looking at the processes, it looks like there is some
thread (random executable) under the winlogon process that is stuck in a
wait state.
To replicate the issue, set a group policy to remove the disconnect at 1
minute, log on to a session and disconnect. Log on again, pick up the same
session, and disconnect. Now, that session will be hung in a disconnected
state till manually removed. Sometimes it will even leave a roaming profile
remnant (cashed profiles are supposed to delete on logout). Microsoft has a
hotfix that is for resetting the time when you have a disconnect and an
active on the same server (kb832088) but that doesn't fix it.
Microsoft has asked us to add UHPCLEAN and I'm seeing a few events, but the
disconnects aren't throwing them. They also asked us to add the policy "Do
not check for user Ownership of roaming profile folder" (kb327259) but it
didn't fix it either.
Any ideas? TIA!
Jennifer Henske
A.G. Edwards Technology Group
----------------------------------------------------------------------------
---------
A.G. Edwards & Sons' outgoing and incoming e-mails are electronically
archived and subject to review and/or disclosure to someone other
than the recipient.
----------------------------------------------------------------------------
---------
Other related posts:
