Select the product you need help with

XADM: Information Store Stops Responding When Processing a Public Folder Replication Message

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

This article was previously published under Q242201

SYMPTOMS

If you receive a public folder replication message from another site while you are adding a new site to your Exchange Server organization, the information store may stop responding. The replication message is from a system public folder, such as the Free/Busy or Organization Forms folders.

Back to the top | Give Feedback

CAUSE

The replication message contains invalid information that causes the information store to stop responding.

Back to the top | Give Feedback

RESOLUTION

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

191014

(http://support.microsoft.com/kb/191014/EN-US/ )

XGEN: How to Obtain the latest Exchange Server 5.5 Service Pack

The following files are available for download from the Microsoft Download Center:

x86:

Collapse this imageExpand this image

Download Q248838engi.exe now

(http://www.microsoft.com/downloads/release.asp?ReleaseID=25443)

Alpha:

Collapse this imageExpand this image

Download Q248838enga.exe now

(http://www.microsoft.com/downloads/release.asp?ReleaseID=25444)

For additional information about how to download Microsoft Support files, click the following article number to view the article in the Microsoft Knowledge Base:

119591

(http://support.microsoft.com/kb/119591/EN-US/ )

How to Obtain Microsoft Support Files from Online Services

Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help to prevent any unauthorized changes to the file.

Back to the top | Give Feedback

STATUS

Microsoft has confirmed that this is a problem in Microsoft Exchange Server version 5.5. This problem was first corrected in Exchange Server 5.5 Service Pack 4.

Back to the top | Give Feedback

Properties

Article ID: 242201 - Last Review: October 26, 2006 - Revision: 4.2

APPLIES TO

Microsoft Exchange Server 5.5 Standard Edition

kbhotfixserver kbqfe kbbug kbexchange550presp4fix kbexchange550sp4fix kbfix kbgraphxlinkcritical kbqfe KB242201

Retired KB Content Disclaimer

This article was written about products for which Microsoft no longer offers support. Therefore, this article is offered "as is" and will no longer be updated.

Back to the top | Give Feedback