Zero Hour Sleep
27Mar/108

Running into Public Folders problems after migration? Read this first…

After migrating your Exchange Public Folders from Exchange 2003 to Exchange 2007 / 2010 chances are you will start experiencing some problems.

These issues might show up under different symptoms however they all have one common solution.

It could be that you can use your public folders normally however sending emails to mail-enabled public folders fails with

#550 5.1.1 RESOLVER.ADR.ExRecipNotFound; not found ##

Or that public folder replication is not working between your Exchange servers and the following Event Log is registered on your Exchange HUB server

Log Name:      Application
Source:        MSExchange Store Driver
Date:          3/24/2010 10:03:27 AM
Event ID:      1020
Task Category: MSExchangeStoreDriver
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      Server.Domain.local
Description:
The store driver couldn't deliver the public folder replication message "Folder Content (PublicFolder@domain.local)" because the following error occurred: The Active Directory user wasn't found..

Note that the above two errors specify that the HUB server is not able to resolve the public folder's email address as a valid recipient.

I have only seen this error when public folder have been migrated from Exchange 2003 and that there are no longer any Exchange 2003 servers in the administrative group that was originally holding the Public Folder Hierarchy.

If the above applies to you then you can solve your problem by

  1. Run ADSIedit.msc
  2. Connect to the configuration partition
  3. Browse to CN=Servers,CN=First Administrative Group,CN=Administrative Groups,CN=Organization Name,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=domain,DC=local
    Of course replace domain,local,Organization Name and First Administrative Group by the appropriate settings of your organization.
  4. Make sure the Servers container specified above is EMPTY
  5. Delete it the Servers container
  6. Wait for Active Directory replication to occur
  7. Restart the Microsoft Exchange Active Directory Topology Service and the Microsoft Exchange Information Store

Voila this should solve your issue

Enjoyed the post, what is next?

Grab our FULL RSS feed! or Email Updates then share it

About Antoine Khater

I have been working in IT consultancy and solution integration since 1998 and I consider myself lucky to be, one in a few, making a living out of my passion. I am also member of the famous Experts Exchange (profile here) online community where I try my best to share what I have learned along the road.
Tagged as: , , , , , Leave a comment
  • WorkingHardinIT

    What if you have multiple Administrative Groups? We have 6, one was the original First Administrative Group which was renamed when still E2K, we migrated to E2K7 3 years ago, now are are moving to E2K10. In the lab we fixed the issue by deleting the empty Servers container in First Administrative Group but in our production environment we delete it from the First Administrative Group (that was renamed) with out success. Do we need to remove every servers container for all legacy Administrative routing groups?

  • http://whygoogle.me/ akhater

    Are all legacy administrative groups empty of all servers ?
    Did you move your Public Folder Hierarchy to the Exchange 2007/2010 Administrative group ?

  • WorkingHardInIt

    Yes & Yes. It all works fine. PF hierachy was in order as allready on E2K7. I've confirmed with MS Support. I did this now on 2 live occassions (ours and a partner site). In both cases I did not need to restart the Microsoft Exchange Active Directory Topology Service and the Microsoft Exchange Information StoreSee also http://workinghardinit.wordpress.com/2010/05/25…

  • WorkingHardInIt

    Yes & Yes. It all works fine. PF hierachy was in order as allready on E2K7. I've confirmed with MS Support. I did this now on 2 live occassions (ours and a partner site). In both cases I did not need to restart the Microsoft Exchange Active Directory Topology Service and the Microsoft Exchange Information StoreSee also http://workinghardinit.wordpress.com/2010/05/25…

  • http://whygoogle.me/ akhater

    Sorry you got me lost, is it working for you or not ?

  • http://whygoogle.me/ akhater

    Yes all the empty “servers” containers should be deleted from the legacy administrative groups

  • SpicyChili

    I know this post is old, but it helped me out a lot! i never thought to look in AD for the problem, but that was it. Thank you!

  • Dave

    Hi,

    We’re an organization with a single domain and a single Exchange server and a couple years ago we migrated from 2003 to 2007. Now we’re attempting to migrate from 2007 to 2010, and I wanted to configure public folder replication just as an easy way to get all the items in our public folders over to the new server and its brand new one day old installation of 2010. However, after trying this fix in adsiedit.msc the couple mailboxes I put on the new server for testing can no longer send mail to anybody except other mailboxes on the new server. They can receive mail from anybody (both within the organization and outside the organization), they just can’t send to anyone except those recipients with mailboxes that are also on the new server. It was working fine before this change, so this must have been what caused it. Any ideas what I could do to get it back to the way it was? I tried running some of the setup switches (like /PrepareAD), and when that didn’t work I tried uninstalling and reinstalling Exchange on the new server, but neither of these fixed it. Thank you for any help you can provide!

« You get “Iashlpr initialization failed” error after installing DHCP on Windows 2008R2 Changing password using Exchange 2010 OWA fails »

Latest Tweets

Follow @ZeroHourSleep (115 followers)

Recent Posts

Archives

Categories

Content Twitter

RSS Feed

RSS by email