Article ID: 814762
Article Last Modified on 10/26/2006
APPLIES TO
- Microsoft Exchange 2000 Server Standard Edition
SYMPTOMS
Some public folders in your Microsoft Exchange 2000 Server organization may not replicate correctly. When you troubleshoot this issue, you may notice the following symptoms:
- When you increase diagnostic logging on the public information store, outgoing replication event messages that list the problem public folders appear in Event Viewer. When you review the message tracking log, you see that replication messages have been sent to the servers in the replica list of the problem public folders. However, one or more of the receiving servers does not generate an incoming replication event in response to these messages, even though the message tracking log on the receiving server indicates that the messages were received.
- When you run the isinteg command against the public information store of the server that does not log the incoming replication events, you notice entries in the Isinteg.pub log file that are similar to the following entries:
Starting test 14 of 17, 'Replication' Warning: Repl 565: This folder should have an entry in the Folders table. Warning: Repl 566: This folder should have an entry in the Folders table. Warning: Repl 567: This folder should have an entry in the Folders table. Warning: Repl 568: This folder should have an entry in the Folders table. Warning: Repl 590: This folder should have an entry in the Folders table. Warning: Repl 591: This folder should have an entry in the Folders table. Warning: Repl 592: This folder should have an entry in the Folders table. ...... Warning: Repl 16212: This folder should have an entry in the Folders table. Warning: Repl 16213: This folder should have an entry in the Folders table. Warning: Repl 16214: This folder should have an entry in the Folders table. Warning: Repl 16370: This folder should have an entry in the Folders table. , number of rows = 17395. Time: 0h:0m:4s, number of warnings = 405
CAUSE
These behaviors may occur if a row has been created in the replication state table, but the corresponding public folder was not successfully created, or if the public folder was subsequently removed without the replication state table being automatically updated. This problem occurs because of one or more of the following reasons:
- The public information store on the server that is experiencing this problem (the server that contains unsynchronized copies of the public folders) may not be processing the incoming replication messages from other servers.
- Replication messages that are sent from the server that is experiencing this problem (the server that contains unsynchronized copies of the public folders) are not sent successfully.
- Replication backfill requests that are sent to the server that is experiencing this problem are not successfully processed by that server.
RESOLUTION
Cumulative Rollup Information
To resolve this problem, obtain the September 2003 Exchange 2000 Server Post-Service Pack 3 (SP3) Rollup. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
824282 September 2003 Exchange 2000 Server post-Service Pack 3 rollup
Hotfix Information
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Exchange 2000 Server service pack that contains this hotfix.
To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:
Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
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 -------------------------------------------------------------- 04-Jun-2003 00:46 6.0.6472.0 3,915,776 Cdoex.dll 04-Jun-2003 00:40 6.0.6472.0 827,392 Davex.dll 04-Jun-2003 00:38 6.0.6472.0 577,536 Dsaccess.dll 03-Jun-2003 23:47 6.0.6472.0 184,320 Dscmsg.dll 04-Jun-2003 00:46 6.0.6472.0 3,575,808 Excdo.dll 04-Jun-2003 00:38 6.0.6472.0 258,048 Exmime.dll 04-Jun-2003 00:40 6.0.6472.0 2,138,112 Exoledb.dll 04-Jun-2003 00:36 6.0.6472.0 81,920 Exosal.dll 04-Jun-2003 00:40 6.0.6472.0 307,200 Exprox.dll 03-Jun-2003 23:39 6.0.6472.0 49,152 Mdbevent.dll 04-Jun-2003 00:08 6.0.6472.0 2,285,568 Mdbmsg.dll 03-Jun-2003 23:41 6.0.6472.0 32,768 Mdbrole.dll 04-Jun-2003 00:38 6.0.6472.0 24,576 Mdbtask.dll 04-Jun-2003 00:37 6.0.6472.0 4,648,960 Store.exe
Note Because of file dependencies, this update requires Microsoft Exchange 2000 Server Service Pack 3 (SP3). For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
301378 How to obtain the latest Exchange 2000 Server service pack
STATUS
Microsoft has confirmed that this is a bug in the Microsoft products that are listed in the "Applies to" section.
Additional query words: kbExchange2000preSP4septbarFix 0x46c XADM
Keywords: kbhotfixserver kbqfe kbqfe kbfix kbexchange2000presp4fix kbbug KB814762
