Hi there! I have googled a lot about this subject but not success This incorrect data in the attibute makes a lot of problems with Public folders with OWA. according to the article http://technet.microsoft.com/en-us/library/bb727370.aspxthe attribute msExchOwningRFTheeBL can be updated via changes in msExchOwningPFTree so I did but with no success. Any ideas how can be cleaned out non exist servers in there ? Thanks,Ilya

Could you please tell us the issue in detail? we need more detail as what are you trying to achieve? Vinod |CCNA|MCSE 2003 +Messaging|MCTS|ITIL V3|

Hi Vinod,The problem is that one of exchange servers inmy exchange org has crashed andthe recordstill exists in attributemsExchOwningRFTheeBL the powershell command shows :[PS] U:\>Get-PublicFolderDatabase Name Server StorageGroup---- ------ ------------Public Folder Database MAILSRV1 Second Storage GroupPublic Folder MAILSRV2 First Storage GroupGet-PublicFolderDatabase : The Exchange server for the database object "MAIL3\First Storage Group\Public Folder" was not found in Active Directory. The object may be corrupted.At line:1 char:24+ Get-PublicFolderDatabase <<<<

-==-==-==--==-==-==-Public Folder Routing-==-==-==--==-==-==- Editing themsExchOwningPFTreeBLattribute directly is not possible, because it is a back link. However, you can delete themsExchOwningPFTreeattribute on a specific public store object. If you delete themsExchOwningPFTreeattribute on the public store object that is unavailable, themsExchOwningPFTreeBLback link attribute will be automatically removed from the back link list. By changing themsExchOwningPFTreeattribute, you change the list in themsExchOwningPFTreeBLlist, and thus alter the public folder routing decision. -==-==-==-==-==-==-==-==-==-==-==-==-==-==-==-==-==-==- This is same in Exchange 2007 also... Amit Tank | MVP Exchange Server | MCITP: EMA | MCSA: M | http://ExchangeShare.WordPress.com

Amit,msExchOwningRFThee isplaced in CN=Servers, CN=Servername,CN=Information store,CN=Public folder storage group,CN=Public foldersbut there is no CN=Server,CN=Servername that hascrashed. And the second question how to return an existservervalue if its needed to msExchOwningPFTreeBL? with a view of clearing out the values msExchOwningPFTreeBL Ihad recreated CN=Folder Hierarchies now the broken server still exist in msExchOwningPFTreeBL but live servers didn't appear in the list probably that was my mistate to recreate CN=Folder Hierarchies:(.

I understood this, but I still having trouble with [PS] U:\>Get-PublicFolderDatabase Name Server StorageGroup ---- ------ ------------ Public Folder Database MAILSRV1 Second Storage Group Public Folder MAILSRV2 First Storage Group Get-PublicFolderDatabase : The Exchange server for the database object "MAI L3\First Storage Group\Public Folder" was not found in Active Directory. The obj ect may be corrupted. At line:1 char:24 + Get-PublicFolderDatabase <<<< How can I solve this issue?

I had a similar issue a few weeks ago with a system I was trying to upgrade. I had 2 MAPI public folder trees in the directory. One was an orphaned object that should not have been there. From the EMS prompt, try this cmdlet:Get-PublicFolder \ -recurseDo you get a listing of public folders? If so, then you are probably not seeing the issue that I was seeing.Jim McBee - Blog - http://mostlyexchange.blogspot.com

[PS] U:\>Get-PublicFolder \ -RecurseGet-PublicFolder : There is no existing PublicFolder that matches the followingIdentity: '\'. Please make sure that you specified the correct PublicFolder Identity and that you have the necessary permissions to view PublicFolder.At line:1 char:17+ Get-PublicFolder <<<< \ -Recurseis there a chance to clean out the schema from non exist exchange 2007 server ?MCSE2003(Messaging&Security),CCNA,CCA,ITILv2

Did you try running ExBPA? It may find the exact cluprit of this mess. Something like... Multiple MAPI public folder trees detected http://technet.microsoft.com/en-us/library/dd535370.aspx Well, about crashed server removal from AD, it is recommended to remove Exchange 2007 server properly by uninstallation. So in your case you can recover the crashed server on a temporary box (may be virtual server or a workstation) with RecoverServerswitch and uninstall it from Add/Remove program so Exchange setup removes stale object of recovered crash server perfectly from AD...Amit Tank | MVP Exchange Server | MCITP: EMA | MCSA: M | http://ExchangeShare.WordPress.com

Amit,I did run ExBPA and didn't help. http://technet.microsoft.com/en-us/library/dd535370.aspxalready tried didn't helpOK,now I will try to reinstallexchange on a temporarybox.MCSE2003(Messaging&Security),CCNA,CCA,ITILv2

Also make sure that you are following below article while uninstalling it after recovering with RecoverServer switch. How to Remove the First Exchange 2007 Server in a Coexistence Scenario http://technet.microsoft.com/en-us/library/bb310767.aspx Before that, if you didn't check, can you verify PF and OAB generation point set to correct Exchange 2007 server PF database in Client Settings tab of all Mailbox database...? Mailbox Database Properties > Client Settings Tab http://technet.microsoft.com/en-us/library/aa997902.aspxAmit Tank | MVP Exchange Server | MCITP: EMA | MCSA: M | http://ExchangeShare.WordPress.com

Hi Amit, The duplicate MAPI trees problem was the one that I was experiencing. It drove me crazy for about 4 days. However, when I tried to enumerate the public folders using Get-PublicFolder, I got the "duplicate MAPI public folder trees" error. I eventually found the duplicate tree object by navigating through the Microsoft Exchange configuration container using ADSIEDIT. It was a "conflict" object and was near the root of the Microsoft Exchange portion of the tree just sitting out there smiling at me and mocking me. :-) I suspectthis probably got created years ago when the E2K3 organization was migrated from Ex 5.5 because their org still had some 5.5 objects that needed to be cleaned out, also. Anyway, it was a weird issue and I have been meaning to blog about it, but I no longer have the exact text from the error either. Jim McBee - Blog - http://mostlyexchange.blogspot.com

Hi,In order to troubleshoot on this issue, I would like to confirm a few things first, regarding this issue and your Exchange environment:1. Please let me know if you are using Exchange 2007 with Service Pack 1. If you have installed service pack 1, please use the method below to check the public folder replica setting:a. Start the Exchange Management Console. In the console tree, click Toolbox. In the result pane, click Public Folder Management Console, and then in the action pane, click Open Tool. The Public Folder Management Console appears.b. In the public folder tree, click or expand Default Public Folders, and then select the parent public folder of the public folder that you want to configure. I suggest you check the folders one by one. To configure replication for the offline address book (OAB) or for Schedule+ free and busy information, expand System Public Folders, and then click OFFLINE ADDRESS BOOK or SCHEDULE+ FREE BUSY.c. In the result pane, select the public folder for which you want to configure replication. In the action pane, click Properties. In <Public Folder> Properties, click the Replication tab. Please check if the removed Exchange 2003 server is holding any replica for any public folder/system folder. If there is, please remove it.2. If there is no public folder replication issue in your environment, I suggest you consider resetting the system folders. Please follow the steps in the this article:How to Reset System Foldershttp://technet.microsoft.com/en-us/library/bb331972(EXCHG.80).aspxRegards,Xiu

Hi Jim,Please try to use ADSIedit to check if you have two Public Folder hierarchies.Please checkvalue on msExchPFTreeType for these Public Folder hierarchies to see if they al set to 1.If yes,then that indicates that there are two MAPI trees.1. We first made sure that all Exchange servers are associated with the correct MAPI tree by checking the attribute msExchOwningPFTreeBL.2. Then we changed the second tree to NON-MAPI tree by setting msExchPFTreeType to 0.3. I recommend you to monitor some days and then confirmthat public folder works fine, thus wecan delete the second tree using ADSIEdit.Regards,Xiu

Hey Jim, That sounds messy and I understand how the situation would have been going those 4 days but glad that you figured out the duplicateculpritobject... :)Amit Tank | MVP Exchange Server | MCITP: EMA | MCSA: M | http://ExchangeShare.WordPress.com

Hey Guys,I am trying to figure out what this attribute is >> "msExchOwningRFTheeBL" I have never seen any attribute like this in entire tenure.Milind Naphade | MCTS:M | http://www.msexchangegeek.com

I guess it was a typo and corrected by Ilya this response...http://social.technet.microsoft.com/Forums/en-US/exchangesvradmin/thread/90347583-91ca-4a37-9834-9c0455c8974e#9add4834-3bd0-46da-9d79-dca61d919a14 Amit Tank | MVP Exchange Server | MCITP: EMA | MCSA: M | http://ExchangeShare.WordPress.com

Oh Okay. Thanks for that Amit.Ilya,I have a couple of suggestions if you want to check few settings:Can you make sure that you have Exchange Server security group added on the PF database and the PF hirarchy in ADSIEDIT?If the group seems to be in place, make sure you see explicit allow permissions for the group on both objects. I am not sure if ExBPA detects this but this group should have Allowpermissions to Store Constrained Delegation Store Read and Write Access Store Read only Access Store Transport Access Hopefuly that helps.MMilind Naphade | MCTS:M | http://www.msexchangegeek.com

To all, I have managed a few hours to get back to the issue so I've solved the issue. I'd like to share my thoughts about the troubleshooting. via ADSI I went to CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=domain,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=domain,DC=CORP and found there a strange entry of the broken exchange server that cannot be modified and was come up a error like shown here http://reidablog.blogspot.com/2005/10/unable-to-delete-active-directory.htm according to the article I reseted the permissions on the exchange 2007 server entry and then deleted that entry so the problem disappear. Thanks all. MCSE2003(Messaging&Security),CCNA,CCA,ITILv2

Thanks for your feedback. :)