Terminal Server 2003 full CPU usage
- From: "Reinder Gerritsen" <VDSG@xxxxxxxxxxxxxxxx>
- Date: Tue, 12 Dec 2006 15:27:15 +0100
Hello,
As of yesterday morning, one of our terminal servers started to behave
rather odd. CPU Usage is maxed at 100% cycle usage, any given moment,
slowing the system to a terible slow response causing RDP logons to hang -
if any connection at all, and logons to the server console will take ages.
This almost regardles to the time the server is running. (i.e. a login
directly after rebooting is possible, but any time after that performace
will drain completely.
When monitoring the processes, one process is maxing out at 80% to 99% CPU
time. Closing down this particular process only makes space for another
process to max out. On the server, also RES Powerfuse has been installed.
When active, Powerfuse CPU Guard squeezes on processes that run over 85% cpu
usage for more then 10 seconds. Once this kicks in, the same happens as when
one would end that process: another process will take over full CPU usage.
Processes that I have seen acting this way include, amongst others,
svchost.exe, explorer.exe, iexplore.exe, the System process, taskmgr.exe,
etc.
The issue pops up, regardless of sessions through RDP or console logons. As
long only one user is connected, usage is high, but the system remains
somewhat responsive. As soon as a second account joins the system is
unbearable slow, and response to mouse input may take even up to 5 minute
before something actually happens.
System: HP ML370 with PIIII 1400 CPU and 1 GB of memory.
OS: Windows 2003 SP1, all current security fixes applied up to November.
Applications: Office XP, RES Powerfuse 7.01b, Symantec Antivirus 10.1 and,
on this particular server MPC 7.
(I know, it's an old and slow machine, but it's twin system can still host
about 15 users without significant performance loss, so we'd rather keep
running as the financials specific software is rather badly documented on
the part of installing it.)
Particularly interesting is that the other machine was showing roughly the
same behaviour last week, but that was solved by a clean reboot. This time
reboots do not appear to solve anything. Since the maintenance window 3
weeks ago, the machines have run perfectly and flawlessly untill now. I find
it a little unlikely the november patches are causing this.
Apart from the high CPU usage, nothing desturbing shows in the performance
monitor
Hopefully someone may know a solution to tracking this down.
.
- Follow-Ups:
- RE: Terminal Server 2003 full CPU usage
- From: Vincent Xu [MSFT]
- RE: Terminal Server 2003 full CPU usage
- Prev by Date: Re: 120 days grace period or purchased licenses ?
- Next by Date: Re: 120 days grace period or purchased licenses ?
- Previous by thread: WTSSendMessage timeout Vs. minimized session window
- Next by thread: RE: Terminal Server 2003 full CPU usage
- Index(es):
Relevant Pages
|
