Windows NT Curious Problem, Terminal server hangs at random, and then takes d

  • Thread starter Thread starter Mordekai
  • Start date Start date
M

Mordekai

Hi All,

I run a domain with 3 DC's, 2 TS servers, 2 Exchange servers and a host of
DB servers.

One site in particular has a reoccurring issue with the Terminal services
Server. All will run fine for some time, sometimes a day sometimes a week,
then all of a sudden I will get a call from one of the terminal services
users mentioning that one program or another that they are using is stalled
with an hourglass... I then reattach my own TS session to check the problem
(which opens fine so long as I was already logged in), however as soon as I
try to open a new application it hangs on load.
Not even task manager will display.
At this point the only option is to power-cycle the TS server.
After power-cycling the TS the DC is found to be hard locked (It is not
locked until this point, however no apps will open in the same manner as the
TS). So the DC gets rebooted also.

This happens only to the DC and TS at one site in the domain. None of the
other servers in the organization behave this way. The DB and Exchange
servers at this location never have an issue.

The DC is a Dual Quad Core system running 2003 x64 R2 Standard while the TS
is a Dual dual core running 2003 x32 Standard SP2. Both have all the latest
service packs and updates installed.

We have User Profiles and Folder Redirection configured, but this seems to
function well.

The event viewer is always spectacularly unhelpful. (empty for the time
period)
This last time the DC had only one error near the time of the incident.

“A process serving application pool 'DefaultAppPool' exceeded time limits
during start up. The process id was '3924'.â€

This is not an error that recoccurs before each time this issue presents
though …

There is no event or error recorded consistently each time this occurs.
Believe me… I’ve looked.

All switching equipment between the servers has been replaced, just in case,
but this was no help also.

All hardware has been checked, including both the RAID and RAM consistency.

Any ideas?
 
have you cleaned out and fully tested your print drivers? yes they can
cause issues exactly like this. I'm not saying it is the problem but if
you've never tested them, then this would be the first place I'd look.

--
Jeff Pitsch
Microsoft MVP - Terminal Services

"Mordekai" <Mordekai@discussions.microsoft.com> wrote in message
news:76A7E014-CA20-4482-8078-5E3DB2EBAEC4@microsoft.com...
> Hi All,
>
> I run a domain with 3 DC's, 2 TS servers, 2 Exchange servers and a host of
> DB servers.
>
> One site in particular has a reoccurring issue with the Terminal services
> Server. All will run fine for some time, sometimes a day sometimes a week,
> then all of a sudden I will get a call from one of the terminal services
> users mentioning that one program or another that they are using is
> stalled
> with an hourglass... I then reattach my own TS session to check the
> problem
> (which opens fine so long as I was already logged in), however as soon as
> I
> try to open a new application it hangs on load.
> Not even task manager will display.
> At this point the only option is to power-cycle the TS server.
> After power-cycling the TS the DC is found to be hard locked (It is not
> locked until this point, however no apps will open in the same manner as
> the
> TS). So the DC gets rebooted also.
>
> This happens only to the DC and TS at one site in the domain. None of the
> other servers in the organization behave this way. The DB and Exchange
> servers at this location never have an issue.
>
> The DC is a Dual Quad Core system running 2003 x64 R2 Standard while the
> TS
> is a Dual dual core running 2003 x32 Standard SP2. Both have all the
> latest
> service packs and updates installed.
>
> We have User Profiles and Folder Redirection configured, but this seems to
> function well.
>
> The event viewer is always spectacularly unhelpful. (empty for the time
> period)
> This last time the DC had only one error near the time of the incident.
>
> "A process serving application pool 'DefaultAppPool' exceeded time limits
> during start up. The process id was '3924'."
>
> This is not an error that recoccurs before each time this issue presents
> though .
>
> There is no event or error recorded consistently each time this occurs.
> Believe me. I've looked.
>
> All switching equipment between the servers has been replaced, just in
> case,
> but this was no help also.
>
> All hardware has been checked, including both the RAID and RAM
> consistency.
>
> Any ideas?
 
Re: Curious Problem, Terminal server hangs at random, and then tak

Thanks for the reply.

I will check this out tonight and post back the results.


"Jeff Pitsch" wrote:

> have you cleaned out and fully tested your print drivers? yes they can
> cause issues exactly like this. I'm not saying it is the problem but if
> you've never tested them, then this would be the first place I'd look.
>
> --
> Jeff Pitsch
> Microsoft MVP - Terminal Services
>
> "Mordekai" <Mordekai@discussions.microsoft.com> wrote in message
> news:76A7E014-CA20-4482-8078-5E3DB2EBAEC4@microsoft.com...
> > Hi All,
> >
> > I run a domain with 3 DC's, 2 TS servers, 2 Exchange servers and a host of
> > DB servers.
> >
> > One site in particular has a reoccurring issue with the Terminal services
> > Server. All will run fine for some time, sometimes a day sometimes a week,
> > then all of a sudden I will get a call from one of the terminal services
> > users mentioning that one program or another that they are using is
> > stalled
> > with an hourglass... I then reattach my own TS session to check the
> > problem
> > (which opens fine so long as I was already logged in), however as soon as
> > I
> > try to open a new application it hangs on load.
> > Not even task manager will display.
> > At this point the only option is to power-cycle the TS server.
> > After power-cycling the TS the DC is found to be hard locked (It is not
> > locked until this point, however no apps will open in the same manner as
> > the
> > TS). So the DC gets rebooted also.
> >
> > This happens only to the DC and TS at one site in the domain. None of the
> > other servers in the organization behave this way. The DB and Exchange
> > servers at this location never have an issue.
> >
> > The DC is a Dual Quad Core system running 2003 x64 R2 Standard while the
> > TS
> > is a Dual dual core running 2003 x32 Standard SP2. Both have all the
> > latest
> > service packs and updates installed.
> >
> > We have User Profiles and Folder Redirection configured, but this seems to
> > function well.
> >
> > The event viewer is always spectacularly unhelpful. (empty for the time
> > period)
> > This last time the DC had only one error near the time of the incident.
> >
> > "A process serving application pool 'DefaultAppPool' exceeded time limits
> > during start up. The process id was '3924'."
> >
> > This is not an error that recoccurs before each time this issue presents
> > though .
> >
> > There is no event or error recorded consistently each time this occurs.
> > Believe me. I've looked.
> >
> > All switching equipment between the servers has been replaced, just in
> > case,
> > but this was no help also.
> >
> > All hardware has been checked, including both the RAID and RAM
> > consistency.
> >
> > Any ideas?
>
>
>
 
Back
Top