Select the product you need help with

Event 1005 or 1013 is logged when you try to start an HTTP resource in an Exchange Server 2003 cluster

Article ID: 2667815 - View products that this article applies to.

SYMPTOMS

When you try to start an HTTP resource on a Microsoft Exchange Server 2003 cluster, the resource may not start as expected or may fail over intermittently.

Additionally, one or more of the following events may be logged in the Application log in Event Viewer:

Event Type: Error
Event Source: MSExchangeCluster
Event Category: Services
Event ID: 1005
Description:
Exchange HTTP Virtual Server Instance 100 (Y12MAIL01): The IsAlive check for this resource failed.
For more information, click <http://www.microsoft.com/contentredirect.asp>.

Event Type: Error
Event Source: MSExchangeCluster
Event Category: Services
Event ID: 1013
Description:
Exchange HTTP Virtual Server Instance 100 (Y12MAIL01): Failed to get the protocol IP address and port bindings from the metabase.
For more information, click <http://www.microsoft.com/contentredirect.asp>.

And, the following event may be logged in the Cluster log:

EventLogging: Exchange HTTP Virtual Server Instance 100 (Y12MAIL01): Failed to get the protocol IP address and port bindings from the metabase. Error Code: 3.

Back to the top | Give Feedback

CAUSE

This issue can occur if one or more of the following conditions are true:

Both the Default Web Site website and the Exchange Virtual Server website are running in Microsoft Internet Information Server (IIS). And, the Default Web Site website and the Exchange Virtual Server website are configured to use the same IP address and port number.

Note By default, the Default Web Site website is disabled in IIS when you install Exchange Server in a cluster configuration.
A corrupted certificate is installed on one of the Exchange cluster nodes. For example, this issue can occur if the certificate is not configured by using a private key.
The server that is running Exchange Server 2003 runs out of nonpaged pool memory,

Back to the top | Give Feedback

RESOLUTION

To resolve this issue, use the following methods, as appropriate for your situations.

Method 1

To resolve this issue, stop the Default Web Site in IIS Manager. To stop the Default Web Site on a server that is running Windows Server 2008, follow these steps:

Click Start, click Administrative Tools, and then click Internet Information Services Manager.
In the navigation pane, expand the server name.
In the navigation pane, expand Sites.
Right-click Default Web Site, click Manage Web Site, and then click Stop.

Method 2

To resolve this issue, configure the Default Web Site website and the Exchange Virtual Server website to use unique IP addresses and port numbers for both the HTTP and HTTPS protocols. To verify the binding information for a website on a server that is running Windows Server 2008, follow these steps:

Click Start, click Administrative Tools, and then click Internet Information Services Manager.
In the navigation pane, expand the server name.
In the navigation pane, expand Sites.
Click the website that you want.
Under Actions, click Bindings.

Method 3

To resolve this issue, reissue the certificate, and then import the certificate.

Note You may also be able to resolve this issue by exporting the existing certificate from another node in the cluster.

Method 4

To resolve this issue, troubleshoot the excessive use of nonpaged pool memory on the server that is running Exchange Server 2003.

For more information about how to monitor and troubleshoot nonpaged pool memory on a server that is running Exchange Server 2003, visit the following TechNet website:

http://blogs.technet.com/b/mikelag/archive/2009/09/15/how-to-monitor-and-troubleshoot-the-use-of-nonpaged-pool-memory-in-exchange-server-2003-or-in-exchange-2000-server.aspx

(http://blogs.technet.com/b/mikelag/archive/2009/09/15/how-to-monitor-and-troubleshoot-the-use-of-nonpaged-pool-memory-in-exchange-server-2003-or-in-exchange-2000-server.aspx)

Back to the top | Give Feedback