One Exchange mailbox can receive mail but cannot send or open in OWA

0
0
Asked By MellowCedar47 On

One user on an on-premises Exchange server can receive email, but Outlook fails whenever they try to send or reply with the message: "None of your email accounts could send to this recipient." Other users in the same mailbox database are unaffected. Recreating the Outlook profile and reinstalling Office did not help.

OWA initially worked as a workaround, but it now fails with `Microsoft.Exchange.Data.Storage.StoragePermanentException` and an inner `Microsoft.Mapi.MapiExceptionDatabaseError`. Mailbox corruption checks found nothing, and the mailbox database itself appears healthy. Moving the mailbox to another database also fails with `MigrationMRSPermanentException`, `MapiExceptionNetworkError`, and Store error `0xA4D` while retrieving mailbox properties.

The mailbox has a quota configured, but the user has not reached it. Has anyone encountered this combination of errors, and what should I check or try next?

3 Answers

Answered By QuietHarbor8 On

The mailbox may have exceeded its named-property quota even though it is still below the normal mailbox size quota. That can cause odd Outlook and OWA behavior, and it may also prevent mailbox moves from reading the required properties. Check the named-property quota and related event logs, rather than only checking mailbox size or running a standard corruption repair.

Answered By SilverPine_62 On

A practical recovery option is to export or otherwise preserve the mailbox data, then remove and recreate the mailbox and restore the contents. It may be faster than continuing to troubleshoot a mailbox with damaged or invalid store properties. Before doing that, make sure you understand what mailbox metadata, calendar items, permissions, and server-side settings may not survive a PST-based restore.

MellowCedar47 -

Could the problem causing this also be carried into the PST? I want to avoid recreating the mailbox only to restore the same issue.

Answered By KindlyOrbit29 On

The configured mailbox quota is probably not the immediate cause if the user is below the limit. The named-property quota is separate, so check that specifically. The fact that both OWA and mailbox migration fail points more toward a mailbox-store or property issue than an Outlook client problem.

Related Questions

LEAVE A REPLY

Please enter your comment!
Please enter your name here

This site uses Akismet to reduce spam. Learn how your comment data is processed.