Article ID: 152433 - Last Review: October 28, 2006 - Revision: 3.3 XADM: How to Remove Orphaned Public FoldersThis article was previously published under Q152433 SYMPTOMS
After you stop replication between two or more sites, folders are still
shown in the Public Folder Hierarchy but they are not accessible from
Microsoft Exchange clients or the Microsoft Exchange Administrator program.
For Exchange Server 4.0, from the Microsoft Exchange Administrator program, the following message will be encountered:
The object cannot be found in the directory. This may be because
replication has not completed. Microsoft Exchange Directory. c1010aae."
The folder could not be opened. The contents of this public folder
are currently unavailable. Either the MS Exchange server computer
servicing this public folder is down or the public folder has not
been replicated to this site.
The object in the information store could not be found. Microsoft Exchange Information Store ID no: c1040af2 RESOLUTION
To remove these orphaned folders, follow these steps:
Warning: The orphaned folders should not be deleted if site replication is ever going to be re-established. This is because once a folder is removed from a site, and replications is re-established, the remove action will be backfiled to the server were the folder belonged to originally. This means that if a folder that used to belong to site A is removed while on site B, and sites A and B are rejoined through replication, the folder will eventually be also deleted on site A.
MORE INFORMATION
If you plan on setting replication back up again, DO NOT take ownership of
the public folders and delete them in the manner described in this article,
as this will cause the public folders in the original site to be deleted
once the replication connector is re-established. Only take ownership of these orphaned public folders if you NEVER want to setup replication again with the site that actually contains the public folders. APPLIES TO
| Article Translations
|


Back to the top
