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

Similar Messages

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

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 2010 - 2013 Public Folder Migration target database gets much bigger than source database

Hi,
i have a question about the pf migration from Exchange 2010 to Exchange 2013. The source database ist about 370 GB. The migration process is still running. At the moment the target database is already 491GB big. Is that a normal behaviour during the migration
process.
Thanks

Hi,
After you have finished the public folder migration process, you can compare the item count of public folders to make sure all public folders have been moved to Exchange 2013.
You can check this by comparing the snapshots before and after the migration. You can refer to the "How do I know this worked?" section in the following article.
Migrate Public Folders to Exchange 2013 From Previous Versions
http://technet.microsoft.com/en-us/library/jj150486(v=exchg.150).aspx
Best regards,
Belinda
Belinda Ma
TechNet Community Support

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."

Large Mail.que database in Exchange 2013

[Background]
Since Exchange 2013 is released, some user may come across the following situations:
The space of disk C is used up.
The transport service stops processing messages.
The Mailbox server is crash.
In this case, the issue can be resolved with checking with the mail.que file which is in the following path on the Mailbox server:
C:\Program Files\Microsoft\Exchange Server\V15\TransportRoles\data\Queue
[Symptom]
The Mail.que file on all Exchange 2013 servers grows very large and it’s even over 20 GB.
[Cause]
It’s a by design behavior.
Different from the previous Exchange server, Safety Net which has the same function with the Transport dumpster in Exchange 2013 takes up the volume of the mail.que file and
it’s the feature which is responsible for the large size of the mail.que in Exchange 2013.
And here is a reference about the feature Safety Net in Exchange 2013:
http://technet.microsoft.com/en-us/library/jj657495(v=exchg.150).aspx
[Workarounds]
1. Allocate large space for the Exchange 2013 installation or increase the volume for Exchange 2013.
These articles will also provide further detail of size calculating:
http://blogs.technet.com/b/exchange/archive/2013/05/14/released-exchange-2013-server-role-requirements-calculator.aspx
http://blogs.technet.com/b/exchange/archive/2013/05/06/ask-the-perf-guy-sizing-exchange-2013-deployments.aspx
(See section: “Transport storage requirements”)
2. Moved queue database to another drive by using
Move-DatabasePath
3. Reduce the SafetyNetHoldTime and MessageExpirationTimeouton values to one day (default values are 2 days). And these commands can be in use:
Set-TransportConfig SafetyNetHoldTime 1.00:00:00
Get-TransportService | Set-TransportService -MessageExpirationTimeout 1.00:00:00
Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

[Background]
Since Exchange 2013 is released, some user may come across the following situations:
The space of disk C is used up.
The transport service stops processing messages.
The Mailbox server is crash.
In this case, the issue can be resolved with checking with the mail.que file which is in the following path on the Mailbox server:
C:\Program Files\Microsoft\Exchange Server\V15\TransportRoles\data\Queue
[Symptom]
The Mail.que file on all Exchange 2013 servers grows very large and it’s even over 20 GB.
[Cause]
It’s a by design behavior.
Different from the previous Exchange server, Safety Net which has the same function with the Transport dumpster in Exchange 2013 takes up the volume of the mail.que file and
it’s the feature which is responsible for the large size of the mail.que in Exchange 2013.
And here is a reference about the feature Safety Net in Exchange 2013:
http://technet.microsoft.com/en-us/library/jj657495(v=exchg.150).aspx
[Workarounds]
1. Allocate large space for the Exchange 2013 installation or increase the volume for Exchange 2013.
These articles will also provide further detail of size calculating:
http://blogs.technet.com/b/exchange/archive/2013/05/14/released-exchange-2013-server-role-requirements-calculator.aspx
http://blogs.technet.com/b/exchange/archive/2013/05/06/ask-the-perf-guy-sizing-exchange-2013-deployments.aspx
(See section: “Transport storage requirements”)
2. Moved queue database to another drive by using
Move-DatabasePath
3. Reduce the SafetyNetHoldTime and MessageExpirationTimeouton values to one day (default values are 2 days). And these commands can be in use:
Set-TransportConfig SafetyNetHoldTime 1.00:00:00
Get-TransportService | Set-TransportService -MessageExpirationTimeout 1.00:00:00
Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.
You cant move the queue database with move-databasepath. You have to follow this method:
http://technet.microsoft.com/en-us/library/bb125177(v=exchg.150).aspx
Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

What is the best backup plan for Archive Databases in Exchange 2013?

Hi,
We have Exchange 2013 with Hybrid setup with O365.
We have On premise exchange 2013 servers with 3 copies of primary Database & Single Copy of Archival DBs.
Now we have to frame backup policy with Symantec Backup Exec which has to backup our primary & Archival DBs
In 2007 exchange, before migration to 2013, we had policy of DBs - Weekly Full backup & Monthly Full Backup
Please suggest what would be the best possible backup strategy we can follow with 2013 DBs.
That too, especially for Archiving DBs
Our Archiving Policy are - 3 category - Any emails older than 6 month OR 1 Year OR 2 Year should go to Archive mailbox.
Keeping this in mind how to design the backup policy ?
Manju Gowda

Hi Manju,
you do not find best practice different from the common backup guidelines, as there is no archive db specific behaviour. Your users may move items to their archive at any time as well as your retention policies may move items that machted the retention policies
at any time. The result is frequently changing content to both, mailbox and archive mailbox databases, so you need to backup both the same way. You also may handle archives together with mailboxes together in the mailbox db
Please keep in mind that backup usually means data availability in case of system failure. So you may consider to do a less frequent backup with your archive db with dependency to the "keep deleted items" (/mailboxes) setting on your mailbox database.
Example:
keep deleted items: 30 days
backup of archive db: every 14 days
restore procedure:
* restore archive DB content
* add difference from recover deleted items (or Backup Exec single item recovery) for the missing 14 days.
So it depends more on your process than on a backup principle.
Regards,
Martin

MailboxInSiteFailoverException - OWA session error on database *over (Exchange 2013 SP1)

Hi all, I have noticed an issue with OWA when database(s) are failed over between DAG members. The environments in question (issue can be reproduced in separate implementations of 2013 SP1 all-role servers) are 2 or more DAG members within the same
AD site/subnet. These are also fresh implementations with SP1 and not upgraded. Exchange servers are load balanced via Netscaler.
So to the issue - OWA users experience the below "..MailboxInSiteFailoverException" message when the database copy is activated. Exchange does not immediately proxy the requests to the active database. You can wait several minutes and
the issue is resolved by refreshing the browser or if you recycle the MSExchangeOWAAppPool on both DAG members, the issue is resolved immediately (OWA session re-established on refresh).
Testing so far involved opening multiple OWA sessions and activating a database copy. At that point, upon refresh of the browser the below error is shown (in all test browsers/sessions below) where I would expect any DAG member to be able to proxy
the client request to the active database server immediately (and not after several minutes).
https://netscaler_LB/owa
https://ex2013server-1/owa
https://ex2013server-2/owa

Hi Simon, I have tested with no firewall on the exchange servers and on client machines within the same subnet as the servers. All with the same results.
I can see many ASP.NET 4.0.30319.0 Event ID 1309 logs similar to this and other threads (http://social.technet.microsoft.com/Forums/windowsserver/en-US/c938dda0-b3bc-4544-851e-f27b503cf4ed/exchange-2013-event-id-1309-source-aspnet-40303190).
IIS logs show similar monitoring mailbox issues but I am still currently looking through the logs. Thanks for your input.
2014-03-30 00:00:23 127.0.0.1 POST /owa/proxylogon.owa - 444 - 127.0.0.1 Mozilla/4.0+(compatible;+MSIE+9.0;+Windows+NT+6.1;+MSEXCHMON;+ACTIVEMONITORING;+OWADEEPTEST) - 401 0 0 13
2014-03-30 00:00:23 127.0.0.1 POST /owa/proxylogon.owa - 444 - 127.0.0.1 Mozilla/4.0+(compatible;+MSIE+9.0;+Windows+NT+6.1;+MSEXCHMON;+ACTIVEMONITORING;+OWADEEPTEST) - 401 0 0 13
2014-03-30 00:00:23 127.0.0.1 POST /owa/proxylogon.owa - 444 - 127.0.0.1 Mozilla/4.0+(compatible;+MSIE+9.0;+Windows+NT+6.1;+MSEXCHMON;+ACTIVEMONITORING;+OWADEEPTEST) - 401 1 2148074254 0
2014-03-30 00:00:23 127.0.0.1 POST /owa/proxylogon.owa - 444 - 127.0.0.1 Mozilla/4.0+(compatible;+MSIE+9.0;+Windows+NT+6.1;+MSEXCHMON;+ACTIVEMONITORING;+OWADEEPTEST) - 401 1 2148074254 0
2014-03-30 00:01:23 ::1 POST /owa/proxylogon.owa &ex=UE:Microsoft.Exchange.Data.Storage.IllegalCrossServerConnectionException 444 DOMAIN\SM_3ce57cd622aa4655a ::1 Mozilla/4.0+(compatible;+MSIE+9.0;+Windows+NT+6.1;+MSEXCHMON;+ACTIVEMONITORING;+OWADEEPTEST)
- 302 0 0 47
2014-03-30 00:01:23 ::1 POST /owa/proxylogon.owa &ex=UE:Microsoft.Exchange.Data.Storage.IllegalCrossServerConnectionException 444 DOMAIN\SM_2891f9d41af2422e8 ::1 Mozilla/4.0+(compatible;+MSIE+9.0;+Windows+NT+6.1;+MSEXCHMON;+ACTIVEMONITORING;+OWADEEPTEST)
- 302 0 0 47

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

Maximum database size Exchange 2013 Standard

Hi,
Does anybody is aware of database size limitation for Exchange 2013 Standard. I remember in older version there was a registry tweak to increase database limits.
Thank you
alfa21

Hi,
This is the official answer :
Supported: Approximately 16 terabytes.
Best practice:
2 terabytes or less.
Provision for 120 percent of calculated maximum database size.
https://technet.microsoft.com/en-us/library/ee832792%28v=exchg.150%29.aspx
Cordialement,
Mickaël LOPES
Blog : http://lopes.im

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

Public Folder Mailbox causes database failover Exchange 2013

Similar Messages

Maybe you are looking for