>There is no Q195995. I've tried searching for it on support.microsoft.com
>and I still can't find it.
You might want to think about subscribing to TechNet.
Quote:>Wait 60 days for what?? I am having the same exact problems.. unfortunately
>my problem was caused by Microsoft Technical Support. They told me to enter
>Exchange Admin in raw mode, and delete the public folder's raw object. Well
>although I deleted them.. they are still showing up. Basically they are
>nothing buy a ghost image of what should be there.
XADM: Removing 'Ghosted' Public Folders
PSS ID Number: Q195995
Article last modified on 11-19-1998
The information in this article applies to:
- Microsoft Exchange Server version 5.5
After an Exchange Server 5.5 computer or site is removed from an
organization without breaking all connections to it first, Public
from that site may still be displayed in the hierarchy of other
the organization. These folders will not rehome by running the DS/IS
consistency checker and will not display any properties in the
Exchange Server Administrator program. Highlighting the Public Folder
clicking Properties on the File menu will display the following error
The object cannot be found in the directory. This may be because
replication has not completed.
Microsoft Exchange Directory
From the Outlook client, the following error message would appear:
Unable to display the folder. The contents of this folder are
unavailable. Either the Microsoft Exchange Server servicing this
folder is down or the public folder has not been replicated to this
site. See your administrator.
After a Public Folder is created, the hierarchy is replicated to all
servers in the organization. This hierarchy is stored in the Pub.edb
and an entry is created in the Automoves table for the folder. If an
Exchange Server 5.5 server computer is shutdown without properly
all the connections first, the folders will never be marked for
from the Public Folder hierarchy or the Automoves table. If the folder
not have a replica on any other Exchange Server computer in your
organization, instead of becoming an orphan, it will 'ghost'. The
servers in the organization will retain an entry for the object in
Pub.edb files (on the Automoves table) to prevent the object name from
being used by another server and to allow it to be moved back
on its home server. This object will remain in place for a default
WARNING: Using Registry Editor incorrectly can cause serious problems
may require you to reinstall your operating system. Microsoft cannot
guarantee that problems resulting from the incorrect use of Registry
can be solved. Use Registry Editor at your own risk.
For information about how to edit the registry, view the "Changing
Values" Help topic in Registry Editor (Regedit.exe) or the "Add and
Information in the Registry" and "Edit Registry Data" Help topics in
Regedt32.exe. Note that you should back up the registry before you
To work around this problem, perform the following steps:
1. Start Registry Editor (REGEDT32.exe), and go to the following
NOTE: The above registry key is one path; it has been wrapped
2. On the Edit menu, click Add Value and add the following
Value Name: Automatic Folder Move Age Limit
Data Type: REG_DWORD
Data: 600 (set to decimal)
This value is in seconds and forces the retention time to 5 minutes
instead of the original 6 months. This is not recommended as a long
3. Wait for the normal Information Store Maintenance cycle to take
(Default 12:00 A.M. - 6:00 A.M. nightly) Information Store
can be set to Always, but make sure to set it back to the previous
settings after the "ghosted" objects have been removed.
All 'ghost' folders will be deleted from the public folders.
4. After the objects have been removed, delete the above registry
return the settings to the default.
NOTE: The registry changes will not take affect until you stop and
the Information store (MSExchangeIS) service.
Version : WinNT:5.5
Platform : winnt
Issue type : kbprb
Copyright Microsoft Corporation 1998.