"Ghost" objects in Public folders

[dmandell]

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

 

[chester27]

Are you using the IISLockdown tool?

 

[dmandell]

No, I am not using the IISLockdown tool, thanks, -Dana

 

[NeillR]

Dana,

Did you get anywhere with this? I have exactly the same problem, and I can't replicate myfolders to Exchange 2k as a result...

 

[dmandell]

No, I am in exactly the same position. I was ready to replicate to exch 2k but did not want to bring the trash along. In my case, it has been put aside for the moment, since the upgrade was not a priority project.

If you get an answer before I do, let me know. I'm just about ready to spend the $250

Dana

 

[dmandell]

By the way, taking the server off line and running isinteg (with fix option) did not fix it. But it could work for you.

Here is another user with a similar problem.

http://www.tek-tips.com/gviewthread.cfm/lev2/3/lev3/15/pid/10/qid/302122

 

[sjjnks]

hey, dmandell:

It's been nearly 4 months since your last post in this thread. Any chance you've found a resolution to this?

I'm having the exact same problem: Trying to get at the properties of a Public Folder through Exchange Admin generates:

The object cannot be found in the directory. This may be because replication has not completed. Microsoft Exchange Directory ID no: c1010aae

Microsoft's KB Article 264317 identifies it perfectly, but no real resolution is given! Pretty much just tells me what happened to get us into this mess!

Essentially, we had a server crash and had to rebuild from scratch with the same server name, IP, OS, SPs, etc and bring the priv.edb and pub.edb back from tape. While this worked (after eseutil'ing it a few times) everything seemed fine, except for our public folders. Some of them came back (calendars, I think) but the others didn't.

We've never had replication with another server, nor do we now. I don't think we ran isinteg at all (much less with the fix option) but it seems from your posts that that didn't work for you anyway? So I think that might be futile as well.

Also, based on your experience, PFinfo and PFAdmin would be a waste of my time as well....

Any suggestions?

 

[dmandell]

No, this was never resolved.
I put it on the back burner when we had to shelve our exchange 2000 upgrade project due to lack of funds.
The problem still exists without resolution.

I have not looked into it further.
If you ever find anything, let me know,

thanks,
Dana

 

[kovacsa]

Hello All .. I have the solution to this problem ... at least one that worked for me. I have 5 orphaned public folders and it worked for all.

Its simple. All you have to do is re-create the folder owner's user account in Windows NT and create a mailbox for them in Exchange. Re-create the user with the exact same username.
Log in as that individual, set them up in Outlook, ... right click on the orphaned public folder and delete. Nothing to it!

Worked for me. Good Luck ... let me know the results.

Kovacsa

 

[dmandell]

I'm not sure how I could pull this off, since the properties of these folders are not available for viewing as mentioned above. So the owner cannot be known.

Nice idea though.
thanks,
Dana

 

[kovacsa]

Dana .. usually if you right click on the folder and go to properties >> Summary it will tell you? If not, the permissions tab?

kovacsa

 

[dmandell]

Thank you for spending the time to respond to this issue with potential solutions. I appreciate your efforts in proposing options.

Again, the properties, and permissions are NOT available for these objects as indicated in previous posts.

Thank you.

 

[devastator]

Dana,
have you stopped and restarted the Exchange services? I had the same issue and was resolved with stopping all the Exchange Services and restarting.
The other option would to be reboot the server. That should definately clean out the ghost items.


Dev

 

[dmandell]

Thanks for the thought.
The server was taken offline to run isinteg (as stated above on Nov. 21st) and restarted after that.

Dana

 

[Horror]

Have you tried to start Exchange Admin program in raw mode and delete the object through here?

 

[dmandell]

Yes, I have. The objects are unfortunately not available in RAW mode either.

Thanks,
Dana

 

[dis1167]

I came across a similiar issue and found an article on google.com that explains how to change the registry value to change the age limits on orphaned or ghost public folders.
As per the article follow these steps:
1. In the registry editor (regedt32) go to:
HKEY LOCAL MACHINE\System\CurrentControlSet\Services\MSExchangeIS\ParametersPublic.
2. On the edit menu, click add value and add the following information:
Value Name: Automatic Folder Move Age Limit
Data Type: REG DWORD
Data: 600 (set to decimal)
This value forces the retention time to 5 minutes instead of 6 months.
3. You need to restart the IS service for this to take effect.
4. Once normal online maintenance is performed, the ghost folders will be deleted from the public folders.
5. After the public folder has been removed, delete the registry key.

Hope this helps.

 

[dmandell]

Sounds like it's worth a try, Thanks!

BTW is the value name:
Automatic Folder Move Age Limit
or
AutomaticFolderMoveAgeLimit

Dana

 

[dmandell]

I found the Microsoft Q article, Thanks, Q323732

http://support.microsoft.com/default.aspx?scid=kb;en-us;Q323732

 

[jenny30534]

Works great for public folder removal but what about mailboxes? Also, found this article that brushes the subject

http://support.microsoft.com/default.aspx?scid=kb;en-us;264159

If anybody figures it out please post what they did, I have tried everything.