--------------------
Thread-Topic: Windows 2000 Server hangs so frequently
thread-index: AcRDySLtL0PS+8viTpu2HL5LzBuRAg==
X-WN-Post: microsoft.public.win2000.general
From: "=?Utf-8?B?TGVvbg==?=" <
[email protected]>
Subject: Windows 2000 Server hangs so frequently
Date: Thu, 27 May 2004 02:01:02 -0700
I installed MS W2K Server on an IBM 205x Series with 2.4 GHz speed and
7600MB memory about two months ago. This server keeps hanging at least once
a week. When I check on running processes on Windows Task Manager screen, I
observe the following: DLLHOST.EXE process appear many times and one of
this process always has CPU 99 for all the hours the server has hanged e.g.
56:02:23hrs.
When you reboot, it normalises and hangs again after a few days. What is
the use of DLLHOST.EXE process and why does it engage the processor fully
making the machine hang. What can I do? Please help.------------------------
DLLHOST.EXE is a surrogate process provided by Windows. It is provided so
that a COM+ .dll file can run in it's own process space. If you are
familiar with COM+ (the concept of having an application composed of an
.exe and multiple .dll's), you will know that you cannot have a .dll in
it's own process, it must be loaded under an .exe. If an application is
written such that it requires a called .dll to run in it's own process,
then DLLHOST.EXE will be launched as the .exe for a COM+ .dll
There are a number of issues with COM+, including memory leak issues, that
have been fixed in KB article 822618: "INFO: Availability of Windows 2000
Post-Service Pack 4 COM+ Hotfix ".
Installing this hotfix should be your first troubleshootings step.
The next step, would be to find out what .dll is running in DLLHOST.EXE
that is causing the problem.
--
~~ JASON HALL ~~
~ Performance Support Specialist,
~ Microsoft Enterprise Platforms Support
~ This posting is provided "AS IS" with no warranties, and confers no
rights.
~ Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
~ Note: For the benefit of the community-at-large, all responses to this
message are best directed to the newsgroup/thread from which they
originated.
