The complete error as in the eventviewer is: (PID 2148, Thread 59) Task Get-PublicFolder throwing terminating exception when processing record of index 0. Exception: System.InvalidOperationException: Couldn't find a MAPI public folder tree. I used the next solution which i found on this forum: • BY Sonny1 Open adsiedit.msc. Select Configuration-Configuration-Services-Microsoft Exchange-Orgname-Administrative Groups-Exchange Administrative Group. Now we were missing the 'Folder Hierarchies' folder - how I still am unsure of. All we had to do was recreate it as follows: Create the "Folder Hierarchies" under the Exchange Administrative Group 1. Right click on Exchange Administrative Group 2. Select New Object 3. Select msExchPublicFolderTreeContainer for the class and click Next 4. Enter the following for the value: Folder Hierarchies, click Next 5. Click Finish Create Public Folder Tree Object 1. Right click CN=Folder Hierarchies -> New Object 2. Selected msExchPFTree for the class 3. For the value we entered, "Public Folders" and clicked next 4. Clicked on the "More Attributes" button, selected msExchPFTreeType and set the value to 1. Note: This is very important that this value is set to a value of 1 as this tells Exchange that this is a MAPI Tree 5. Click Ok and then finish Populate msExchOwningPFTreeBL attribute object of the PF Stores in the organization (Since this attribute is not directly editable, you have to follow the below steps to do this for each PF store) 1. Get properties of the newly created "Public Folders" Tree object in ADSIEdit. 2. Copy the distinguishedname value to the clipboard and then click cancel. 3. Navigate to the Storage group that contains the Public Folder Store for this server and get properties of the server. 4. Locate the msExchOwningPFTree attribute and paste in the value that was copied to the clipboard in step 2. Click OK. 5. Restart the Information Store Service 6. Now try to mount the PF store and see if we can access it fine now. After recreating 'Folder Hierarchies' PF working fine. Thanks, Milind and Mike for quick respond. and special thanks for Sonny1. The only difficulty i had was finding the 'msExchOwningPFTree attribute'. I think i found it underConfiguration-Configuration-Services-Microsoft Exchange-Orgname-Administrative Groups-Exchange Administrative Group > and then the container from the public folders. On this object I was able to add the distinguishedname into the attribute. I am stil not sure this is the correct place. Strange thing is that the Outlook 2003 clients are able to connect again, but when I open Public Folder Management Console under Toolbox i still get the error 'Couldn't fin a public folder MAPI tree'. Hope anyone can help me out on this. Thank you in advance.Mark

After compared the setting in the lab, I found that the class of “Folder Hierarchies” shall be “msExchclassContainer” instead of “msExchPublicFolderTreeContainer”James Luo TechNet Subscriber Support (http://technet.microsoft.com/en-us/subscriptions/ms788697.aspx) If you have any feedback on our support, please contact tngfb@microsoft.com

Hello James, So the conclusion is to reperform the adjustments, replacing 'msExchPublicFolderTreeContainer' with 'msExchclassContainer'? Mark

Please ensure that value is correct, or you can recreate the public folder database. The answers in the threads below may help: Need to recreate public folders due to broken permissions Public Folder Permissions Broken James Luo TechNet Subscriber Support (http://technet.microsoft.com/en-us/subscriptions/ms788697.aspx) If you have any feedback on our support, please contact tngfb@microsoft.com

How's the issue currently?James Luo TechNet Subscriber Support (http://technet.microsoft.com/en-us/subscriptions/ms788697.aspx) If you have any feedback on our support, please contact tngfb@microsoft.com

Hello James-Luo, I apologize for the late reply. At the end we finally found the reason why replication of pulic folders was not succeeding. It was a flaw in a third party software package, which (we thought succesfully) disabled during transition. After this we were able to migrate the pulic folders. Durng 3 transitions from Exchange 2003 to Exchange 2010 it went wrong. The first went completely wrong and due to time restrictions we decided at one moment to start over :( from scratch. Luckily it was a smaller site. During the third transition we found out the issue and managed to complete the transition succesfully. The second we managed to get the whole system working again, but it has still problems. I will start a new thread for this and hope I manage to solve the problem. Thank you for your assistance in this case! I hope you can assist me in my next thread as wel :). Mark