Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

System Profile: IBM Server hardware Windows Ent Server 2003 running terminal services. No Citrix. Max user load: 30


While in the course of normal operation our terminal server will hang up. As far as I can tell there isn't any trigger that's plainly visible yet. The way in witch it hangs may give a clue though. The hang presents its self by users not being able to initiate any new processes. All processes currently loaded into memory work just fine. Example: outlook 2007. You may continue to read email, operate the client and such. Some people don't even realize the hang has occurred for a bit of time.

My attempts to troubleshoot have been futile. Reacting to the hang does no good because I can't start any new processes to investigate. After I reboot the server my next instinct would be to begin logging to catch the hang occurring but I'm not sure what to log.

Right now I'm attempting to keep process explorer running in case the issue occurs again. Sometimes it happens twice a day, other times, once a week.

Anyone have any ideas on how I could set myself up for better success in tracking this problem down?

Thanks, Donovan

share|improve this question

Look at Desktop Heap exhaustion. Let this baby run and see what you find.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.