Microsoft KB Archive/913644

= FIX: The W3wp.exe process may frequently stop responding when you run an out-of-process COM+ application on a Windows Server 2003 SP1-based computer =

Article ID: 913644

Article Last Modified on 12/3/2007

-

APPLIES TO


 * Microsoft Internet Information Services 6.0

-





SYMPTOMS
When you run an out-of-process Microsoft COM+ application on a Microsoft Windows Server 2003 Service Pack 1 (SP1)-based computer, the W3wp.exe process may frequently stop responding (hang). For example, this problem occurs when the COM+ application runs DLLs that were created by using Microsoft Visual Basic 6. Additionally, you may receive &quot;Out of memory&quot; error messages.



CAUSE
This problem occurs because of a deadlock condition in the Iisext.dll file.



Service pack information
To resolve this problem, obtain the latest service pack for Windows Server 2003. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

889100 How to obtain the latest service pack for Windows Server 2003

Hotfix information
To resolve this problem, apply the hotfix that is described in the following article in the Microsoft Knowledge Base:

913441 FIX: The list of extension files that the IisWebService.ListExtensionFiles method returns may be incomplete in IIS 6.0



WORKAROUND
To work around this problem, revert to the version of the Iisext.dll file that is included in Windows Server 2003.

Note If you revert to the version of Iisext.dll that is included in Windows Server 2003, you may experience increased memory usage on the computer. For more information about this issue, click the following article number to view the article in the Microsoft Knowledge Base:

823700 FIX: Your computer may run slowly when you use Active Directory Service Interfaces scripts in a program to administer IIS on a computer that is running Windows Server 2003, Windows 2000, or Windows XP



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section. This problem was first corrected in Windows Server 2003 Service Pack 2.

