Microsoft Knowledge Base Email Alertz

KBAlertz.com: Event ID 1014 and Event 1005 are logged in the Application log after you use an SSL certificate for Exchange virtual server on an Exchange Server 2003-based cluster

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.

Click here to create a
FREE account
Already have an account?
[Click here to Login]

Search KbAlertz

Advanced Search

Webmasters
Put kbAlertz on your website.
[ Click Here for more! ]





ASP.NET 3.5 Web Hosting with Windows 2008 and SQL 2008: Click Here!
Discount ASP.NET Hosting
ASP.NET 2.0 and 3.5
Windows2008 and SQL2008
US and UK Hosting
The ad says 3 - but KBAlertz referrals get
** SIX MONTHS FREE **


Bug Tracking Software
For bug tracking software or defect tracking software or issue tracking software, visit Axosoft.


Community Site



We Send hundreds of thousands of emails using ASP.NET Email



Expert Web Design & Graphic Design
Design44.com

ASP.NET 3.5 Web Hosting with Windows 2008 and SQL 2008: Click Here!
Discount ASP.NET Hosting
ASP.NET 2.0 and 3.5
Windows2008 and SQL2008
US and UK Hosting
The ad says 3 - but KBAlertz referrals get
** SIX MONTHS FREE **




Mentioned In








Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks




Article ID: 949412 - Last Review: June 5, 2008 - Revision: 1.1

Event ID 1014 and Event 1005 are logged in the Application log after you use an SSL certificate for Exchange virtual server on an Exchange Server 2003-based cluster

Hotfix ImageHotfix Download Available
View and request hotfix downloads

On This Page

SYMPTOMS

When you install and use a Secure Socket Layer (SSL) certificate on the Exchange Virtual Server Web site that is hosted on a clustered Exchange 2003 mailbox server, the Resrcmon.exe process and the Lsass.exe process may encounter high CPU usage issue on the server. This high CPU usage issue will eventually lead to cluster failover. Additionally, the following events are logged in the Application log:


Event Type: Error
Event Source: MSExchangeCluster
Event Category: None
Event ID: 1014
Description: Exchange HTTP Virtual Server Instance xx (<computer name>): IsAlive checking for this resource failed due to timeout.

Event Type: Error
Event Source: MSExchangeCluster
Event Category: None
Event ID: 1005
Description: Exchange HTTP Virtual Server Instance xx (<computer name>): IsAlive checking for this resource failed due to timeout.

CAUSE

This issue occurs when the SSL certificate is larger than the maximum packet size for the network. This maximum packet size for the network is known as the MTU (Maximum Transmission Unit). In this situation, if the Resrcmon.exe process or the Lsass.exe process calls the Exres.dll file to perform the IsAlive check over the SSL protocol, an infinite loop occurs in the Exres.dll file. This infinite loop results in the high CPU usage issue for corresponding processes.

RESOLUTION

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=support (http://support.microsoft.com/contactus/?ws=support)
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

This hotfix requires Microsoft Exchange Server 2003 Service Pack 2 to be installed on the server because of file dependencies. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
836993   (http://kbalertz.com/Feedback.aspx?kbNumber=836993/ ) How to obtain the latest service packs for Exchange Server 2003

Restart requirement

You do not have to restart the computer after you apply this hotfix. However, you want to stop Cluster service before you apply this hotfix on the passive node.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
Collapse this tableExpand this table
File nameFile versionFile sizeDateTime
Exres.dll6.5.7653.36134,65623-May-200816:34

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

APPLIES TO
  • Microsoft Exchange Server 2003 Standard Edition
  • Microsoft Exchange Server 2003 Enterprise Edition
Keywords: 
kbautohotfix kbexchcluster kbexpertiseinter kbhotfixserver kbqfe KB949412
       

Community Feedback System

Very often, it takes hours to solve a problem. Very often, you've looked high and low, and have tried a lot of solutions. When you finally found it, chances are, it was because someone else helped you. Here's your chance to give back. Use our community feedback tool to let others know what worked for you and what didn't.

Please also understand that the community feedback system is not warranted to be correct, it's simply a system that we've built to let people try and help each other. If something in a feedback response doesn't make sense to you, or you're not comfortable making changes that the feedback talks about (like registry edits), please consult a professional.

Thank you for using kbAlertz.com Feedback System.

-- Scott Cate

Be the first to leave feedback, to help others about this knowledge base article.

(Optional) Name

(Optional) Public URL Or Email

Comments
No HTML -- Text Only Please