Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Rhinorhino on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

"Ghost" objects in Public folders

Status
Not open for further replies.

dmandell

MIS
Sep 26, 2002
342
US
Exchange 5.5 SP4 Public folders
There are two items not visible to Outlook users that can be seen in Exchange Administrator under "Public Folder Resources".
They are 0k, 0 items, and are over two years old. They are not used, and need to be deleted before setting up replication to a new server.

Unfortunately, if one tries to access properties of one item, the following error is seen.
"The Object is no longer available". Press F5 to refresh the disply, and then try again.
Microsoft Exchange Administrator
ID no: c1030745

The other object gives the following error on access.
"The object cannot be found in the directory. This may be because replication has not completed.
Microsoft Exchange Administrator
ID no: c1010aae

This server is not replicating with any other server.
(Objects are not available in RAW mode either)

DS/IS consistancy adjustor comes up clean (except for the same errors seen above)

I'm holding off replication to a Exch. 2k server as part on a migration until I can clean this up.
(No point in hauling old trash to your new motorhome:)

Using the PFinfo tool (from the resource kit) does not show these objects as items on which permissions can be set.
i.e. they do not show in the output file. (pfinfo.txt)

So I can't use PFAdmin to set permissions on these objects.
(Assuming that they were orphaned objects with lost permissions from some unknown replication before my time)

Any Ideas?
thanks,
Dana
 
I tried the info in Q323732 and it did not solve the problem. Even after waiting the proper interval, the public folder objects were not accessable or deletable.

Dana
 
Please use Consustency Adjuster --- it works on mine.

Then assign the orphaned mailbox to the real users.

Regards
Agus
 
Thanks for offering suggestions.
Please be sure to read the whole thread before responding.

The consistancy adjuster has already been tried, and the orphaned PUBLIC FOLDERS cannot be assigned to anyone since the properties cannot be accessed.

Thanks for taking the time to look through the forum and respond to issues.

Dana
 
Dana,

I had nearly the same problem.

There were some ghost entries in the mailbox resources in the private information store without any corresponding mailbox.

When I tried to view the properties with the MS Exchange Admin-program (even in raw mode) of these ghost entries in the view mailbox resources I got the error message "The object cannot be found in the directory. This may because replication has not completed. c1010aae"

Because of the missing Object I was not able to delete these entires.

But I found a solution, it worked for me:

-I know it is a problem, but you need to know where the original object (connector or mailbox or other object) was stored.

In my case the entries were stored under path "o=ORG/ou=SITE/cn=Configuration/cn=Connections/cn=NAME".

I've seen that path in a message in the event log after I started a DS/IS consistency check. The system tried to create the object automatically, but failed.

See also
-ok, after you know where the original object was stored you re-create this object in that directory.

Just follow this description:


Don't care about the location which is mentioned in the article, just create the object where it was originally - this is important.

What is also important is to type in the HOME-MDB value as described, otherwise it won't work!

-After you've created the object you can double-click on the object in the mailbox resources to see if the entry in the directory is linked now to your new created object.

-Then delete the object (not from the mailbox resources, this is still not possible) you've just created.

Now the ghost entry in the mailbox resources should be also deleted.

This worked fine for me, I've deleted all old entries!

Regards
Rolf
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top