[THIN] Re: Down Sessions W2k3Sp2 + CPS4.5fr01
- From: "Joe Shonk" <joe.shonk@xxxxxxxxx>
- To: thin@xxxxxxxxxxxxx
- Date: Fri, 29 Feb 2008 13:16:44 -0700
A bad print monitor would cause this... Do you have a document imaging
products running on these servers?
Joe
On Fri, Feb 29, 2008 at 9:44 AM, Andrew Wood <andrew.wood@xxxxxxxxxxxxxxxx>
wrote:
> Hi,
>
> I've got a w2k3sp2 terminal server build with CPS 4.5FR01. All users
> connect to published applications – typically simple Office apps –normally
> just Outlook.
>
> Occasionally sessions are locking up … new sessions won't start – users
> see 'authenticating' in the windows logon dialogue. Existing sessionssimply
> lock up as if there is some processing going on, or the connection
> has dropped. Lots of 'down' sessions start appearing.
>
> CPU low, memory use low, redirector not reporting any issues; Disk i/o
> fine; redirector fine; doesn't appear to be a 'lack of resource' issue.
>
> Edgesight SP2 is running, there is AV (f-secure 5.55), they've got the MS
> Profile Unloader running and they're running hybrid profiles with
> Appsense.
>
> I've been able to get the issue to happen on a ZDC that only had an admin
> on. On disconnecting with the Admin Console running, the console session
> stayed at "disconnected"; when attempting to reconnect there was an error
> message on the new RDP console session with 'Error: The requested
> operation cannot be completed because the terminal connection is currently
> busy'. New RDP terminal sessions would start for a period after that – but
> then they started to hang on 'authenticating', locking up etc. etc.
>
> The down/disconnected session steadfastly refused to be anything other
> than that. After a while the Admin console running from another machine
> would happily taunt me with showing the 'disconnected' and down sessions
> on the server, but refused to show processes. Then it stopped playing
> altogether.
>
> So….
>
> Has anyone else had a similar problem with that particular error message? (
> "The requested operation cannot be completed because the terminal
> connection is currently busy")
>
> Or, has anyone any additional ideas for investigating the 'down' sessions
> – looks to be that a process is refusing to die and that in itself locks
> up the creation of new sessions - it even impacts on existing sessions to
> the extent of the sessions locking up completely (which in turn go to
> disconnected, then 'down' and stay there) but finding which process it
> isproving quite character building.
>
> Tia.
>
> a.
>
> Andrew
>
> Gilwood CS Ltd
>
> Registered Office : Mount Ashbrooke, Holmland Buildings, Tunstall Road,
> Sunderland, UK, SR2 7RR. No. 6099397 England
>
>
Other related posts:
