Public Folder Replication Fails Due To Empty Legacy Administrative Group

re: Public Folder Replication Fails Due To Empty Legacy Administrative Group

Gary Enticott — Tue, 13 Jul 2010 18:48:16 GMT

This is poor, Very poor.

why was this not tested before releasing this to RTM.

re: Public Folder Replication Fails Due To Empty Legacy Administrative Group

Chris — Sun, 11 Jul 2010 20:41:55 GMT

Decided to open a case with PSS on this issue. No fix as such but the issue was resolved by exporting the PF to a PST file, deleting the PF and recreating/importing the PST.

The PSS rep said he'd had the issue before as well so seems likely to be a bug.

re: Public Folder Replication Fails Due To Empty Legacy Administrative Group

Chris — Sun, 04 Jul 2010 23:35:32 GMT

I'm having the same issue at B.M and JH after a migration from 2003 to 2010 having deleted the emtpy servers container, sending to a migrated mail enabled public folder results in the following NDR:
550 5.2.0 STOREDRV.Deliver: The Microsoft Exchange Information Store service reported an error. The following information should help identify the cause of this error: "MapiExceptionNotFound:16.18969:B4000000, 17.27161:0000000054000000000000000000000000000000, 255.23226:00000000, 255.27962:44000000, 255.17082:BFF9FFFF, 0.25697:00000000, 4.21921:BFF9FFFF, 255.27962:FA000000, 255.1494:00000000, 255.26426:96000000, 4.18236:BFF9FFFF, 4.7974:BFF9FFFF, 255.1750:C0010000, 0.26849:35000000, 255.21817:BFF9FFFF". ##
Is there a fix yet?

re: Public Folder Replication Fails Due To Empty Legacy Administrative Group

Tricks — Tue, 25 May 2010 17:33:32 GMT

I have a frustrating issue with replication failures of PF Hierarchy and Content from a single exch 2003 to a single exch 2010 (CAS,HT,MB roles), I have trawled through a lot of postings with similar problems but NO answers to help my situation (this is the simplest topology one can wish for). I have increased the logging level and can see the source server sending the repl messages but they get stuck with the categoriser. MSExchnage transport event id 6015 followed by 9013, are logged on the exch 2003 application log. I have seen some posts that answer these errors but they relate to pre -exchange 2010. Can any one point me in the right direction please.

re: Public Folder Replication Fails Due To Empty Legacy Administrative Group

Darko — Fri, 14 May 2010 17:29:57 GMT

Ok, so this is a critical step in removing the last 03 server. I can't imagine there is an alternate step other than to recreate the PF in 2010, possible export the items out of the existing PF, reimport to new PF and then re-replicate. As far as recreating the legacy Admin Group, if you have a backup you could possibly complete an Authoritative Restore, but normally this also causes other corky problems. Here is a good thread that talks to a similar case in technet land. Hopefully some of these steps can help you.

http://social.technet.microsoft.com/Forums/sv-SE/exchangesvradmin/thread/c1ea6019-f6bb-4b72-a4ad-2bfaf6abec78

re: Public Folder Replication Fails Due To Empty Legacy Administrative Group

Sean — Tue, 11 May 2010 04:38:07 GMT

My issue is I did not "Move" the Public Folder hirearchy from Exchange 2003 to the 2010 admin group/server prior to removing the last 2003 server. How can I do this after the fact? Also could you link to how to re-create legacy Admin Group via ADSI Edit?

Thanks

re: Public Folder Replication Fails Due To Empty Legacy Administrative Group

Robert — Fri, 07 May 2010 22:48:58 GMT

This is one of those "how did this not get caught in testing bugs" IMHO. Many of of wasted hours and hours of time tring to fix this assuming it was "our" fault...

re: Public Folder Replication Fails Due To Empty Legacy Administrative Group

Darko — Fri, 07 May 2010 18:39:18 GMT

Exchange 2003 to 2007 or 2010 generates the BFF9FFFF when it cannot understand the translation between an Bridgehead and CAS. If you manually telnet to the SMTP of the old 2003 Front-End try emailing the mail-enabled PF, it will work. This is due to the CAS being excluded. You should be able to get around this issue by replicating the 2003 folder to the 07/10 server. Once if fully replicates the CAS server will no longer create the error. Hopefully this helps with some of the discussion.

For the other part of the discussion on the TO line, you need to create a hub transport rule to remove the To header from the emails. It may be a pain, but I believe I read somewhere that this is a known bug.

re: Public Folder Replication Fails Due To Empty Legacy Administrative Group

Dave Stork — Thu, 06 May 2010 23:35:15 GMT

It's not only the PF replication that has this issue, also mail enabled public folders generate a similar message.
I had it after a Exchange 2003 transition to 2010. See my blog posting about it:
http://blogs.dirteam.com/blogs/davestork/archive/2010/03/16/mail-enabled-public-folder-recipient-not-found.aspx

re: Public Folder Replication Fails Due To Empty Legacy Administrative Group

bilong — Thu, 06 May 2010 23:34:04 GMT

JohnB, yes the legacyExchangeDN will still point to the non-existent admin group. But no, nothing should break. Ever since Exchange 2000, you've been able to move mailboxes to a new admin group and delete the old one. That was a feature of Native Mode move mailbox, and it doesn't change the legacyExchangeDN. Because of that, it's actually quite common and normal to have legacyExchangeDNs on mailboxes that point to an admin group which no longer exists.

B.M, that's a different problem with a few causes. One cause is simply not having permissions. You must have at least Contributor rights to the public folder. Another cause is an improperly formatted P2 header (the "To:" line) when the email is coming from an external sender. For instance, if the To: line contains just a display name and no actual email address, this happens. Yet another cause is hierarchy replication failing so that we don't see the folder on certain stores. If you can't track down the problem, get a case open so we can find out what's going on.

JH, I'm trying to find your open case so I can review it, but I'm not having much luck. If you click on my name to go to my TechNet blog and then click on the Email link there to contact me, I'll look into it.