Microsoft KB Archive/843226

= CPU usage increases, and poor performance occurs when Outlook Web Access uses SSL to connect to an Exchange 2003 computer in a cluster =

Article ID: 843226

Article Last Modified on 10/25/2007

-

APPLIES TO


 * Microsoft Exchange Server 2003 Standard Edition
 * Microsoft Exchange Server 2003 Enterprise Edition

-





SYMPTOMS
When you configure Microsoft Outlook Web Access to use a Secure Sockets Layer (SSL) connection to a Microsoft Exchange Server 2003 computer, you may notice a dramatic increase in CPU usage by the Lsass.exe process and by the Resrcmon.exe process. This problem occurs on an Exchange 2003 computer that is running in a Microsoft Windows Server 2003-based cluster.

Additionally, an Error event that is similar to the following is logged in the Application log: Event Type: Error

Event Source: MSExchangeCluster

Event Category: Services

Event ID: 1014

Date:

Time:

User: N/A

Computer:

Description: Exchange HTTP Virtual Server Instance - (GENESIS): IsAlive checking for this resource failed due to timeout



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

836993 How to obtain the latest updates and service packs for Exchange Server 2003

Hotfix information
A supported hotfix is now 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 service pack that contains this hotfix.

To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:

http://go.microsoft.com/?linkid=6294451

Note If additional issues occur or 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. To create a separate service request, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

Prerequisites
No prerequisites are required.

Restart requirement
You must restart your computer after you apply this hotfix.

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 tool in Control Panel.

Date        Time   Version            Size    File name -- 09-Apr-2004 03:05  6.5.6980.80        18,432  Exhotfix.dll 28-May-2004 19:33  6.5.6980.90       132,096  Exres.dll 03-Jun-2004 22:31                      1,690  Exhotfix.cdf 09-Apr-2004 03:05  6.5.6980.80        18,432  Exhotfix.dll



WORKAROUND
To work around this problem, disable the SSL connection, and then restart the server.



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 corrected in Exchange Server 2003 Service Pack 1 (SP1).



MORE INFORMATION
For additional information, click the following article numbers to view the articles in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates

817903 New naming schema for Exchange Server software update packages

Keywords: kbqfe kbfix kbbug kbexchange2003presp1fix kbhotfixserver KB843226

-

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

© Microsoft Corporation. All rights reserved.