Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

Event IDs 9582, 9665, and 9175 may occur on a server that is running Exchange Server 2003


View products that this article applies to.

Symptoms

On a server that is running Microsoft Exchange Server 2003, the following error is logged regularly when message transfer agent (MTA) usage is high. This problem may occur when Exchange 2003 and Exchange 5.5 coexist or when a third-party application that uses MTA is installed.
Event Type: Error
Event Source: MSExchangeIS
Event Category: Performance
Event ID: 9582
Description:
The virtual memory necessary to run your Exchange server is fragmented in such a way that normal operation may begin to fail. It is highly recommended that you restart all Exchange services to correct this issue.
Event ID 9582 is a common error that occurs because of virtual memory fragmentation issues. When this error occurs, the performance of the Exchange Server decreases. For example, clients have to wait for a longer time to receive responses from the server. Additionally, the following errors may be logged in the Application log:
Event Type: Warning
Event Source: MSExchangeIS
Event Category: General
Event ID: 9665
Description:
The memory settings for this server are not optimal for Exchange. For more information, click http://support.microsoft.com?kbid=815372
Event Type: Error
Event Source: MSExchangeSA
Event Category: MAPI Session
Event ID: 9175
Description:
The MAPI call 'OpenMsgStore' failed with the following error: The Microsoft Exchange Server computer is not available. Either there are network problems or the Microsoft Exchange Server computer is down for maintenance. The MAPI provider failed. Microsoft Exchange Server Information Store ID no: 8004011d-0526-00000000

↑ Back to the top


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: 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

You must have Microsoft Exchange Server 2003 SP2 installed to apply this hotfix.

Restart requirement

You do not have to restart the computer after you apply this software update.

Hotfix replacement information

This hotfix does not replace any other software updates.

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.
File nameFile versionFile sizeDateTime
X400omv1.dll6.5.7653.2931,23229-Feb-200817:28

↑ Back to the top


Status

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

↑ Back to the top


More information

For more information, click the following article numbers to view the articles in the Microsoft Knowledge Base:
817903 New naming schema for Exchange Server software update packages
824684 Description of the standard terminology that is used to describe Microsoft software updates

↑ Back to the top


Keywords: KB947484, kbbug, kbfix, kbqfe, kbHotfixServer, kbexpertiseinter, kbautohotfix

↑ Back to the top

Article Info
Article ID : 947484
Revision : 2
Created on : 10/8/2011
Published on : 10/8/2011
Exists online : False
Views : 215