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

December 17th, 2014 1:51am

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 tnmff@microsoft.com

Free Windows Admin Tool Kit Click here and download it now
December 18th, 2014 3:54pm

Yes, to narrow down this issue, I suggest we repair the public folder mailbox by New-MailboxRepairRequest or move it to another DB. If the issue doesn't re-occur, then there must be something wrong with the PF mailbox itself. And move the mailbox could always correct corruptions of the mailbox.

Thanks.

December 19th, 2014 6:58am

Hi,

Any update on this issue?

Free Windows Admin Tool Kit Click here and download it now
December 23rd, 2014 12:09pm

Hi , sorry it's been a while since my last update - I did move the Public Folder Mailbox to another Database but pretty much everyday that database moves to another DAG member with the same error message.

It doesn't tend to move on the weekends which suggest it's probably related to user activity.

At the moment I just put up with it but is there anything else I can check ?

March 19th, 2015 6:16pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics