Article ID: 892485 - View products that this article applies to.
This article has been archived. It is offered "as is" and will no longer be updated.
Backfill requests for some public folders are never completed on the Microsoft Exchange 2000 Server or Microsoft Exchange Server 2003 computer. The server continues to generate backfill requests. Eventually, the backfill requests may saturate the network.
This problem occurs if the local Exchange computer replica list for a public folder is out of sync with the information in the remote server rows in the replication state table.
In Exchange, each public folder store maintains a replication state table to track the status of every replica in the store. The replication state table contains a list of replicating servers for each folder in the public folder store. Each row in the table contains the GUID and the replication ID (ReplID) for the server. The local Exchange computer also maintains a replica list that lists the replicating servers that are known to the local server for each public folder.
The replica list on the local server becomes out of sync with the remote server rows in the replication state table in either of the following scenarios:
Exchange Server 2003
Service pack informationTo resolve this problem, obtain the latest service pack for Exchange Server 2003. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/836993/EN-US/ )How to obtain the latest service packs for Exchange Server 2003
Exchange 2000 Server
Hotfix informationA 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.
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, submit a request to 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=supportNote 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.
PrerequisitesBecause of file dependencies, this software update requires both the following packages:
Restart requirementYou do not have to restart the computer after you apply this hotfix. However, the following Exchange 2000 services are automatically stopped and then restarted during the hotfix installation:
Hotfix replacement informationThis hotfix does not replace any other hotfixes.
File informationThe 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 -------------------------------------------------------------- 03-Feb-2005 10:52 6.0.6617.43 299,008 Isinteg.exe 03-Feb-2005 10:58 6.0.6617.43 2,338,816 Mdbmsg.dll 03-Feb-2005 11:54 6.0.6617.43 4,710,400 Store.exe
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
This problem was first corrected in Microsoft Exchange Server 2003 Service Pack 2.
After you install this hotfix, you must run the updated isinteg command to clean up any replica lists that are out of sync and to remove any unreferenced remote server rows from the replication state table. To do this, follow these steps:
(http://support.microsoft.com/kb/182081/ )Description of the Isinteg utility
301460For more information about how to troubleshoot public folder replication problems, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/301460/ )Exchange command-line parameters for the Isinteg.exe tool
842273For more information about Microsoft software updates, click the following article numbers to view the articles in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/842273/ )How to troubleshoot public folder replication problems in Exchange 2000 Server and in Exchange Server 2003
(http://support.microsoft.com/kb/824684/ )Description of the standard terminology that is used to describe Microsoft software updates
(http://support.microsoft.com/kb/817903/ )New naming schema for Exchange Server software update packages
Article ID: 892485 - Last Review: October 27, 2013 - Revision: 3.2
Contact us for more help
Connect with Answer Desk for expert help.