Users unable to create or delete folders in migrated public folders using Outlook RRS feed

  • Question

  • We have an Exchange 2013 CU3 environment migrated from Exchange 2007.

    The public folder migration was completed over the weekend.

    The environment has several public folder mailboxes.

    Post migration users are unable to create/delete new sub folders,  or modify permissions using Outlook on any of the migrated public folders.  Users can however create new top level folders using outlook. They can also create and delete new posts in migrated public folders.

    Admins are able to create folders and set permissions on migrated folders using the EAC.

    Test User accounts used for testing are set to use the Primary Hierarchy mailbox as their default public folder mailbox.

    Test Users have been given Owner permissions from the root down on the folders we are testing with.

    We have tested with Outlook 2010 and 2013 getting the same "Cannot create the folder" error.

    Monday, February 3, 2014 7:48 PM

All replies

  • Further testing

    We moved a top level folder from a secondary PF mailbox to the primary PF mailbox using the New-PublicFolderMoveRequest command in powershell.

    After the move completed we could create new folders under the moved top level folder.

    The top level folder that was moved had it's own sub-folders that we did not move to the primary mailbox. (We didn't move the whole branch.. Just the top level folder)

    We still cannot create or modify the existing sub-folders after moving the top level folder.

    We then moved the newly created sub-folder to a secondary PF mailbox.

    At that point we could no longer create sub-folders in the folder form outlook.

    From what I can tell you can only create new sub-folders in folders homed to the primary PF mailbox when using outlook.

    Is this a bug or as designed?

    According to this Tech ed presentation Clients connecting to a secondary PF mailbox should have folder changes proxy to the primary PF mailbox.. (See slide 10)


    Update : 2-5-2014

    Not much new to report other than it appears that users need to be homed to the primary PF mailbox to delete calendar meetings.

    Opened a ticket with Premier support.

    Update 2-11-2014

    Premier support continues to look into the issue. No ideas as to the cause yet.


    Still no resolution from support or even a clue what is causing this.

    Monday, February 3, 2014 8:21 PM
  • The cause of this issue is that our public folder hierarchy is to large. Almost 20,000 folders.

    Exchange 2013 Public folder has a supported limit of 10,000 folders but it will let you go beyond that at your own risk.

    The reason for the limit is the requests from the secondary to primary mailbox are timing out due to the size of the hierarchy.

    Thursday, March 6, 2014 5:00 PM
  • This is the exact same problem we got Scott.

    But our foldercount is just around 5000 - and the issues are identical.

    Did Premier give you any other workarounds or tips?

    Wednesday, March 19, 2014 11:52 AM
  • Scott,

    Did you ever receive any resolution from Premier support? We have encountered the same problem migrating PF and connecting with Office 2010 and Office 2013. We are able to add and delete items in existing folders; but are unable to create new folders. Currently, our only viable option is moving away from PF to shared mailboxes. 

    Thanks in advance.

    Tuesday, March 3, 2015 11:06 PM