corrupt system folder database in Exchange 2003
Hello,
for exchange 2003 in mixed environment (Exchange 2010 implemented, but not active) replication of system folders fails (e.g. Free/busy, offline address book,
organizational forms library, etc..) - we see:
Type Warning
Source MSExchangeIS Public St
Category Replication Errors
Event ID 3092
Description Error 0x8004010f occurred while processing a replication event.
Type Warning
Source MSExchangeIS Public St
Category Replication Errors
Event ID 3085
Description Error 0x8004010f occurred while generating an
outgoing replication message.
Also event 3092 we see,
Run an isinteg against the public folder stores on each
of the servers, the only error is the replication test fails
We tested following:
New content created in a new public folder will successfully
replicate to other Exchange servers.
Old content moved into a new public folder will successfully
replicate to other Exchange servers.
So we believe, owning Folders table in the public
folder store has become corrupt.
What is best way to proceed?
Because this are system folders, it is impossible to move then to another PF (tree).
Thanks - Katrin
Katrin
August 15th, 2012 6:14am
have you seen this article?
http://support.microsoft.com/kb/822444
Free Windows Admin Tool Kit Click here and download it now
August 15th, 2012 7:00am
Hello Ishmael,
Thanks for the answer - but I have some additional questions about this article:
What will this do to users free/busy information that is already published? It will be deleted and they will need to re-publish this information?
What would be the best way of re-publishing this information?
thanks - KatrinKatrin
August 15th, 2012 8:54am
Hello Ishmael,
The actions were applied - it made no difference, it was double checked that the instruction was followed correctly.
The process did not remove any of the old system folders from the Exchange servers. Replication is still not occurring.
sorry for delay - KatrinKatrin
Free Windows Admin Tool Kit Click here and download it now
September 5th, 2012 6:06am
hmmm. interesting. do you have another public folder server in the same administrative group? if so you could make sure that all your non-system folder data is replicated, and then delete the public folder store on the troublesome server.
if the store won't delete you *could* remove it using adsiedit, and then follow the article given previously to create the system folders on one of the other replicas in the same admin group.
September 6th, 2012 3:51am