Exchange 2010 SP2 Rollup 4 errors after update: MSFTESQL and MapiExceptionUnexpectedMailboxState

This post is also available in: Polish


MSFTESQL error after applying Rollup 4 for Exchange 2010 SP2:

After updating yours Exchange 2010 SP2 environment to Rollup 4 or Rollup 4-v2 you can find errors in EventLog like below:

Event 4999:

Watson report about to be sent for process id: 14116, with parameters: E12, c-RTL-AMD64, 14.02.0297.000, ExMSFTE, M.E.Search.ExSearch, M.E.S.Crash.CrashNow, M.E.Common.FailFastException, 678e, 14.02.0318.001.
ErrorReportingEnabled: False

Event 64772:

The filter daemon process MSFTEFD exited unexpectedly. Here is the stack trace:

Event 1053:

The system exception c000010a was raised at 000007FEF9B60F16. Stack:

Also you can expirence problems with CPU utilization is reaching 100% during mailbox moves. All utilization is consumed by msftefd.exe

Those symptoms looks very similar to symptoms described for Exchange Server 2007:

The Msftefd.exe process constantly consumes up to 100 percent of CPU resources

Error message occurs on a server that is running Exchange Server 2007 and that has the mailbox server role installed


Sometimes helps applying the following hotfix to Microsoft Filter Pack 2.0:


If you uninstall Rollup 4 for Exchange 2010 SP2 the errors won’t appear anymore.

Also after installation of Rollup 4 for Exchange 2010 SP2 you can get problems with OWA search it’s not working.
If you try to rebuild search indexer or run ResetSearchIndex.ps1 it won’t help.

Microsoft know about this bug in Rollup 4 and Rollup 4-v2 and tells that this bug will be fixed in Rollup 5 for Exchange 2010 SP2.

As a workaround for bug with search index, belowed steps are recommended:

Set-MailboxDatabase ' Mailbox Database Name '-IndexEnabled $False
.\ResetSearchIndex.ps1 -all
 Set-MailboxDatabase ' Mailbox Database Name '-IndexEnabled $True


Exchange 2010 SP2 Rollup 4 MapiExceptionUnexpectedMailboxState: Unable to delete mailbox. (hr=0x80004005, ec=2634)


When you apply Rollup 3 or Rollup 4 for Exchange Server 2010 SP2, you can get error when you move mailbox from one mailbox database to another DB.

This error/warning looks like below:

The Microsoft Exchange Mailbox Replication service completed request <mailbox> with warnings.
Warning: Failed to clean up the source mailbox after the move.
Error details: MapiExceptionUnexpectedMailboxState: Unable to delete mailbox. (hr=0x80004005, ec=2634)


After move, mailbox in new database is available for user but mailbox in old database isn’t deleted.

You should check your Exchange 2010 SP2 environment for SoftDeleted mailboxes.

We wrote about it in this post:

How to remove (purge) Disconnected Mailboxes

First you should check your retention time which is set in mailbox database properties. Check how long mailboxes should be not purged after deletion.

Then run:

Get-MailboxStatistics -server MB01 | Where { $_.DisconnectReason -eq "SoftDeleted" } | Format-List DisplayName, DisconnectReason, DisconnectDate, Database | sort DisconnectDate


When you get list of all mailboxes with MailboxState SoftDeleted, check the DisconnectDate. If it’s greater than Retention time for deleted mailboxes, then you should remove SoftDeleted mailboxes using belowed command:

Remove-StoreMailbox -Database MailboxDatabase -Identity <MAILBOXGUID> -MailboxState Softdeleted



Print Friendly
Tagged , , , , , , , , , . Bookmark the permalink.

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>