Public Folder Mailbox- Missing Primary Hierarchy Exchange 2013

Hi guys,
I was attempting to create a Public Folder using the Exchange Admin Center but when i tried it came up with the error "Couldn't find the public folder mailbox."
When I went back to check on the Public Folder Mailbox that I had created I noticed that there was no Primary Hierarchy even though Secondary Hierarchy where visible.
Is it Possible to recreate the Primary or change one of the existing Secondaries.
Thanks
A K richardson

Hello,
Is there any update?
Cara Chen
TechNet Community Support

Similar Messages

Public Folder Mailbox causes database failover Exchange 2013

Hi , we are completing a migration from Exchange 2007 to Exchange 2013. All was going swimmingly until we migrated our legacy public folders. Now every now and again ( once a day generally ) the Exchange Database hosting the Public Folder Mailbox
crashes and fails over to another DAG member.
We are using CU5 and our old 2007 server is offline but not removed from the organization yet.
The error message is as follows :
Event ID 1013
The mailbox with mailboxguid "xxxxxxxxxxxx" caused crash or resource outage on database (GUID="xxxxxxxxxxx")
along with :
Event ID 1001
Microsoft Exchange Server Information Store has encountered an internal logic error. Internal error text is (Unable to apply maintenance GetNonKeyColumnValuesForPrimaryKey-norow, index corruption?) with a call stack of ( at Microsoft.Exchange.Server.Storage.Common.ErrorHelper.AssertRetail(Boolean
assertCondition, String message)
and :
Event ID 1002
Unhandled exception (Microsoft.Exchange.Diagnostics.ExAssertException: ASSERT: Unable to apply maintenance GetNonKeyColumnValuesForPrimaryKey-norow, index corruption?
The Mailbox Guild matches the Public Folder Mailbox GUID and the Database GUID matches the Database where the mailbox is mounted.
The error seems to be the same as this question :
https://social.technet.microsoft.com/Forums/office/en-US/7e823810-29f4-48f2-ad60-37e6ac147d3e/exchange-2013-database-dismounts-unexpectedly
However I'm after a bit more concrete information as to what actually causes this and if an upgrade to CU6 is required. This link appears to suggest moving the mailbox will help. Has anyone else come across this with CU5 and will a mailbox move
correct it ?
http://blogs.technet.com/b/exchange/archive/2014/10/03/those-pesky-lazy-indices.aspx

Hello,
Thank you for your post.
This is a quick note to let you know that we are performing research on this issue.
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Simon Wu
TechNet Community Support

Object-Owner missing in Public Folder Calenders after Transition to Exchange 2013 SP1

Hi there,
we transfered all Public Folders from Exchange 2003 to 2010 to 2013 SP1. We have some Calendars with PublicFolderClientPermission Author witch includes EditOwnedItems and DeleteOwnedItems
Unfortunately the Author Rights wont work after migration. it seems like the creator of the object got lost.
since i never notices that in transitions from exchange 2003 to 2010, i think that should be related to the exchange 2013 transition.
Can anybody approve or disprove that behavior?
thanks alot

Noticed now in the Exchange 2013 Event Logs that we're getting quite a few of these warnings:
"Process <Select one exchange releated process>.exe (PID=<whatever>). Object [CN=Public Folder Database,CN=Databases,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=Contoso,CN=Microsoft
Exchange,CN=Services,CN=Configuration,DC=contoso,DC=local]. Property [PublicFolderDatabase] is set to value [contoso.local/Configuration/Deleted Objects/Public Folder Database
DEL:ca62a715-05b2-4b08-ae0f-7f7c4b7e4cc3], it is pointing to the Deleted Objects container in Active Directory. This property should be fixed as soon as possible."
If i take a look at that mailbox database it's obvious that it's pointing towards the old Public Folder Database, which is quite interesting as Exchange 2013 isn't supposed to used that value at all (according to http://technet.microsoft.com/en-us/library/bb123971(v=exchg.150).aspx):
[PS] C:\Windows\system32>Get-MailboxDatabase -Identity "Mailbox database" | fl
PublicFolderDatabase : contoso.local/Configuration/Deleted Objects/Public Folder Database
DEL:ca62a715-05b2-4b08-ae0f-7f7c4b7e4cc3
I'm assuming this is what happens when messing around with ADSIEdit :) So, further ADSIEdits to set that value to null on the existing Mailboxdatabases, or anyone have any other suggestions?

Outlook 2007 on Terminal Server cannot manage Public Folder Favorites after Migration to Exchange 2013

Hi,
we are running a Server 2008 R2 as a Terminal Server with Outlook 2007 SP3 (incl Nov 2012 Update 12.0.6665.5000) which is known as fully supported with Exchange 2013.
With Exchange Server 2007 we did not have any issues. But after having successfully migrated to Exchange 2013 we cannot manage our public folders favorites from these clients anymore.
As we are running Outlook 2007 on a WTS we can not use Exchange Cache Mode and so we can also not download Public-Folders-Favorites as an option. Whenever we try to delete existing favorites or when we try to delete public folders with content or subfolders
there will be an error msg that says that it cannot be deleted and that there may be no sufficient permissions. But this IS NOT the issue NOR the solution as I have full admin rights and am owner of the public folders.
On single fat clients with Outlook 2007 with Exchange Cache Mode enabled we can manage the favorites and the public folders without problem.
We need to be able to manage the favorites of all users (circa 50-60 users) from the WTS with Outlookm 2007. I have no more ideas right now. Does anyone know how to get this settled?
Thanks, Paula

Hi,
Based on the description, users could access public folders successfully, but when they tried to manage public folder favorites or wanted to remove specified folders, they got error message of no sufficient permissions.
Is it right?
You mentioned on single fat clients with Outlook 2007 with Exchange Cache Mode enabled, user can operate normally. Is this a WTS with Outlook 2007 installed?
If possible, please switch this Outlook client from cached mode to online mode to check result.
Best regards,
Belinda Ma
TechNet Community Support

Exchange 2013 - Public Folder Mailbox and Single Item Recovery

Hello,
I recently had a request to recover some messages that an ex-employee deleted from the "recover deleted items" folder in their public folder. Since this resides on a public folder mailbox and it does have the option for
"Single Item Recovery" to be enabled on the box (which I enabled not knowing if this really works or not), is there a way I can still recovery these items or do I have to go to a backup to obtain those messages. Since ExFolders does not work that
is not an option. I've seen commands to restore a public folder that was deleted but not items that were deleted directly from a public folder. I checked using MFCMAPI and I do see the dumper root and the public folder dumpster for each folder but it
looks to be only the "deletions" folder and don't see anything similar to a "purges" type folder. Any ideas or am I stuck recovering from backup? Thanks in advance!

So I think you are stuck and will need to restore the EDB to a Recovery Database to restore the items because when the end user purged the items from the "Recover Deleted Items" it removes them from the Recoverable Items/Deletions folder.
Check out this article
http://blogs.technet.com/b/exchange/archive/2013/08/23/recovering-public-folder-information-in-exchange-2013.aspx
I have not played with the recoverable items settings on the 2013 public folder enabled mailbox EDB but you might try checking out Litigation or In Place Hold to use as a safety mechanism moving forward. That said this will also increase the
DB size so consider all the options before implementing
Search, Recover, & Extract Mailboxes, Folders, & Email Items from Offline Exchange Mailbox and Public Folder EDB's and Live Exchange Servers or Import/Migrate direct from Offline EDB to Any Production Exchange Server, even cross version i.e. 2003 -->
2007 --> 2010 --> 2013 with Lucid8's
DigiScope

Exchange Public Folder Migration - Public Folder Mailbox "LockedforMigration"

I've recently started a SBS2008 (Exchange 2007 - Latest SP3) migration to Exchange 2013CU6.
Most of the Migration has gone to plan however I've been following a few guides on the Public Folder migration and have seen more errors and time spent than what it is worth.
I've now decided to abandon the Public folder migration as there wasn't really anything of importance in the old 2007 Public Folders, and just setup a new Public Folder Mailbox and PF Folder on the 2013 environment, however... as I started with the migration
the 2013 Server is stuck in "LockedforMigration" mode and will not allow me to create a new Public Folder.
Is there anyway to forcibly 'unstuck/release' the "LockedforMigration = True value.
Or can I just start decommissioning the old 2007 Box and that will force the unlocking of Migration flag
By no means is this the only guide, but here is what I've been following if that will help
http://technet.microsoft.com/en-us/library/jj150486(v=exchg.150).aspx
Thanks Ian

Hi Ian,
According to the error message above, please make sure you are running the command as Administrator, and make sure the Administrator is a member of Organization Management Group and Server Management Group. Then try to run command to release "LockedforMigration
$True".
Since Public Folders on Exchange server 2013 can't be coexisted with legacy Public Folders within an Org, you should delete Public Folder Database from legacy Exchange server 2007 first, then create a new Public Folder Mailbox on Exchange server 2013.
Thanks
Mavis
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Mavis Huang
TechNet Community Support

How do public folder mailboxes across multiple DAGs work?

I have three Exchange 2013 DAGs in three different sites. The three DAGs can communicate with each other fine but not necessarily the users in the sites. Users in Site A can communicate with the Dags in Site B and Site C. Users in Site
B can only communicate with the DAG in Site A and Site B. Users in Site C can only communicate with the DAG in Site A and Site C.
I want the site specific public folders to live in a public folder mailbox on their local DAG. My questions are as follows:
1. If a user in Site A had rights to every public folder in all public folder mailboxes would all of the Public Folders show in Outlook for them?
2. What's the best method of migrating from Exchange 2007 PFs to this? Can I map certain Public Folders to certain PF Mailboxes?
Thanks.

1. They should, yes.
2. Yes, you can. There are migration scripts you download, and after you run the script, you can change the folder-to-mailbox mapping to suit your needs. The process is pretty intuitive.
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

What is the best practice on mailbox database size in exchange 2013

Hi,
does anybody have any links to good sites that gives some pros/cons when it comes to the mailbox database sizes in exchange 2013? I've tried to google it - but hasn't found any good answers. I would like to know if I really need more than 5 mailbox databases
or not on my exchange environment.

Hi
As far as I know, 2TB is recommended maximum database size for Exchange 2013 databases.
If you have any feedback on our support, please click
here
Terence Yu
TechNet Community Support

Remove Last Public Folder Database / Impact on Outlook 2007 - 2013 Clients ?? / Exchange 2010

Hello together,
we have an Exchange 2010 SP3 UR5 Infrastructure. Now the end is in sight for Public Folders :)
We want to Remove our Last Public Folder Database on our Organization.
How can i get this managed and what is the Outlook 2007+++ Client Impact on this Action ?
The Plan is:
Remove all Public Folder Content
Set the OAB to Web Distribution Only
Clear the “msExchHomePublicMDB” attribute on Exchange Databases
Clear the “siteFolderServer” attribute on CN=Exchange Administrative Group (FYDIBOHF23SPDLT)
Remove the Public Folder Database with ADSI
Is there anything else to do ?
Is there any Outlook Client Impact on this ? Does the Users get a Outlook Error like "your exchange administrator did some changes please restart" or is it transparent for the users ?
thanks for Feedback,
Best,
Martin

Hello,
Please follow the Naren.Neelam's suggestion.
Besides, I recommend you remove database via EMC or EMS. If you can't remove the database via EMC or EMS, and then you can use ADSIEDIT to remove the public folder database from the organization.
When you remove a public folder database, the Exchange database (.edb) file for the database and other files associated with the database aren't automatically deleted. You must delete the public folder database files manually.
Here are some articles for your reference.
http://technet.microsoft.com/en-us/library/dd876883(v=exchg.141).aspx
http://exchangeserverpro.com/exchange-2010-remove-public-folder-database/ (Note: Microsoft
is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please make sure that you
completely understand the risk before retrieving any suggestions from the above link.)
Cara Chen
TechNet Community Support

Resources and public folder database - migration from 2007 to 2013

We migrated our resource mailboxes thru the move mailboxes in 2013 EAC but now we're at the point of decommissioning our 2007 servers. Before the actual decommission we stopped all 2007 services and dismounted all 2007 databases. Once we did
this the resources would no longer work - errors pertaining to cannot directly book the resource.
I had to bring up the public folder database for the moved resources to work again. We do not use public folders any longer so we did not do any type of public folder migration. Do I need to do this for the resources to work?

Hi,
Could you please tell me your Outlook version?
I saw someone got the following error when he tried to book resource after migrating from Exchange 2007 to Exchange 2010, if Outlook version is Outlook 2007. But Outlook 2010 worked well.
"Cannot directly book a resource for this meeting."
Please switch between online and cached mode to check the result. And please check if this issue occurs in OWA.
If possible, please use Outlook 2010 to check the result.
Best regards,
Belinda
Belinda Ma
TechNet Community Support

Migrating a mailbox cross forest from exchange 2013 Sp1 to exchange 2010 SP2 Update rollup 8

I can migrate a mailbox fine from exchange 2010 sp2 update rollup 8 to exchange 2013 sp1 or Cu2.
I was testing today migrating cross forest from 2010 sp2 udpate rollup 8 back to exchange 2010 sp2 but I get the below error. Is this even possible? I cannot find any documentation on this scenario yet.
VERBOSE: [21:52:47.622 GMT] New-MoveRequest : The remote server doesn't support client 'casservername.domain.com'
version (14.2.341.0 caps:05FEFF). Missing functionality: 'TenantHint'.
VERBOSE: [21:52:47.637 GMT] New-MoveRequest : Admin Audit Log: Entered Handler:OnComplete.
The remote server doesn't support client 'casservername.domain.com' version (14.2.341.0 caps:05FEFF). Missing functionality: 'TenantHint'.
+ CategoryInfo : NotSpecified: (0:Int32) [New-MoveRequest], RemotePermanentException
+ FullyQualifiedErrorId : 782D22F0,Microsoft.Exchange.Management.RecipientTasks.NewMoveRequest

Hi Steve,
I'm a little confused what you are saying. Here is my understanding:
When you migrate mailboxes from Exchange 2013 back to Exchange 2007, the above error occurs.
If I have misunderstood your concern, please let me know.
For migrating mailboxes back to Exchange 2007, there is a simple and straightforward method. Please use the New-MailboxExportRequest cmdlet to convert all mailboxes into pst files. And then use the Import-Mailbox cmdlet to import all pst files into Exchange
2007.
Hope it helps.
Best regards,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Amy Wang
TechNet Community Support

Mailbox migration between two Exchange 2013 servers is horribly slow

Hi,
when migrating mailbox between 2 exchange 2013 servers,it s horribly slow. I have found some articles which describing problems about content indexing and missing AD group. This is not my problem, I have tried solutions but it didn't work. Both exchange
are next to each one, same VLAN, same switch. Just migrating between databases.
When I start batch jobs it is migrating only 1 mailbox at once and speed is really slow (2000 - 3000 mail items per 5 minutes). So mailboxes which have 10GB it's migrating 3 hours. My server is on 1gbps LAN.
I have also checked MsExchangeMailboxReplication.exe.config on both servers:
    MaxActiveMovesPerSourceMDB="20"
    MaxActiveMovesPerTargetMDB="20"
    MaxActiveMovesPerSourceServer="100"
    MaxActiveMovesPerTargetServer="100"
    MaxTotalRequestsPerMRS="100"
Do you have any idea where to look why only 1 mailbox is migrating at once?
Thanks

Hello,
For the reason why only 1 mailbox is migrating at once when you start batch jobs, there is no official articles or blog to explain it.
I recommend you check if the speed is slower when you move a smaller mailbox. If the issue doesn't occur, I recommend you set
the AllowLargeItems parameter.
Here are some articles for your reference.
New-MigrationBatch
http://technet.microsoft.com/en-us/library/jj219166(v=exchg.150).aspx
Exchange 2013 Local Mailbox Moves
http://www.msexchange.org/articles-tutorials/exchange-server-2013/mobility-client-access/exchange-2013-local-mailbox-moves-part1.html
If you have any feedback on our support, please click
here
Cara Chen
TechNet Community Support

How many system mailboxes should be in exchange 2013 after moving from exchange 2010?

Hi, I am moving mailboxes from exchange 2010 to exchange 2013, I noticed that in exchange 2013, besides discovery search mailbox, there are other 5 system mailboxes.(especially, there are 2 x Microsoft Exchange system mailboxes) Please see the pic attached.
Does this look right? thanks

Looks perfectly fine - Why MS decided to name two of the five arbitration mailboxes the same (Microsoft Exchange) is unclear but it is what it is :)
In EMS:
Martina Miskovic

Mailboxes wont move to Exchange 2013

Im currently attempting to move mailboxes over to Exchange 2013 from 2010. Upon creating the initial migration batch of 34 boxes, 31 failed and 3 system boxes completed. I then attempted to migrated a single mailbox and it completed without errors, however,
the mailbox didnt actually appear to have been moved.
I get 0 Total 0 Synced 0 Finalized and 0 Failed.
When I view the details on the batch, it shows nothing.
Any ideas?

Hi,
It's glade to hear the good news! Thanks for your update.
Best regards,
Belinda
Belinda Ma
TechNet Community Support

Import Exchange 2010 Mailbox Database .edb into Exchange 2013

My Exchange 2010 server recently crashed I am in the process of setting up a new 2013 server. Is it possible to import the .edb file from my old server to the new server to recover the mailboxes?

Hi sapper,
Thank you for your question.
We could not mount the database to new server simply, because all services are still on Exchange 2010. So we could refer to the following link:
Perform disaster recovery by the following link:
https://technet.microsoft.com/en-us/library/dd876880(v=exchg.141).aspx
Migrate Exchange 2010 to Exchange 2013 by the following link:
https://technet.microsoft.com/en-us/library/jj898583(v=exchg.150).aspx
If there are any questions regarding this issue, please be free to let me know.
Best Regard,
Jim
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Jim Xu
TechNet Community Support

Public Folder Mailbox- Missing Primary Hierarchy Exchange 2013

Similar Messages

Maybe you are looking for