Microsoft KB Archive/895983

= Event ID: 1011 and Event ID: 1009 occur when you use an ISA Server cluster in front of an Application Center 2000 cluster =

Article ID: 895983

Article Last Modified on 9/22/2006

-

APPLIES TO


 * Microsoft Application Center 2000 Standard Edition

-





Important This article contains information about editing the metabase. Before you edit the metabase, verify that you have a backup copy that you can restore if a problem occurs. For information about how to do this, see the &quot;Configuration Backup/Restore&quot; Help topic in Microsoft Management Console (MMC).



SYMPTOMS
When you use a Microsoft Internet Security and Acceleration (ISA) Server cluster in front of a Microsoft Application Center 2000 cluster, the W3wp.exe process may stop responding. When this problem occurs, the following two events are logged in the System log on the computer that is running Microsoft Application Center 2000:

Event 1 Event Type: Warning

Event Source: W3SVC

Event Category: None

Event ID: 1011

Date: 28/04/2004

Time: 13:36:35

User: N/A

Computer:

Description:

A process serving application pool  suffered a fatal communication error with the World Wide Web Publishing Service. The process id was '3808'.

The data field contains the error number.

For more information, see Help and Support Center at http://support.microsoft.com.

Event 2 Event Type: Warning

Event Source: W3SVC

Event Category: None

Event ID: 1009

Date: 28/04/2004

Time: 12:10:56

User: N/A

Computer:

Description:

A process serving application pool  terminated unexpectedly.

The process id was '2084'. The process exit code was '0xff'.

For more information, see Help and Support Center at http://support.microsoft.com.



CAUSE
This problem occurs when the Application Center Request Forwarder Filter (fFiltExt.dll) incorrectly processes incoming HTTP 1.0 requests. The filter may incorrectly process these requests when the servers that are running Application Center 2000 communicate through a server that is running ISA Server.

In this case, the filter processes all forwarded requests as HTTP 1.1 protocol requests that have keep-alive connections enabled.

For example, when the filter processes incoming HTTP 1.0 protocol requests, it treats the HTTP 1.0 protocol requests as HTTP 1.1 protocol requests. It uses &quot;keep alive&quot; connections to try to maintain a connection to another server that is running Application Center on the other side of the server that is running ISA Server. Therefore, the HTTP 1.1 protocol keep-alive connection request times out.



RESOLUTION
Warning If you edit the metabase incorrectly, you can cause serious problems that may require you to reinstall any product that uses the metabase. Microsoft cannot guarantee that problems that result if you incorrectly edit the metabase can be solved. Edit the metabase at your own risk.

Note Always back up the metabase before you edit it.

To resolve this problem, you must apply the hotfix that is mentioned in the following Microsoft Knowledge Base article: For more information, click the following article number to view the article in the Microsoft Knowledge Base:

815931 FrontPage publishing on Application Center through ISA is not successful

After you apply the hotfix, you must create the following key in the Microsoft Internet Information Services (IIIS) metabase. To do this, use the Mdutil.exe command-line tool. The Mdutil.exe command-line tool is located in the Support folder on the Application Center 2000 installation CD.

To create the metabase key, follow these steps:  Click Start, click Run, type cmd, and then click OK. At the command prompt, type the following command, and then press ENTER:

mdutil.exe set AppCenter/Cluster -prop 57624 -dtype DWORD -utype 200 -value 0





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 Application Center 2000 Service Pack 2.

Keywords: kbtshoot kbprb KB895983

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.