One on-premises Exchange user can receive email normally, but Outlook fails whenever they send or reply with the error: "None of your email accounts could send to this recipient." Recreating the Outlook profile and reinstalling Office made no difference. OWA initially worked, but it later began returning Microsoft.Exchange.Data.Storage.StoragePermanentException with an inner MapiExceptionDatabaseError. Mailbox repair found no corruption, the mailbox databases appear healthy, and moving the mailbox to another database fails with a MapiExceptionNetworkError and StoreEc 0xA4D. Other users in the same database are unaffected. What could cause this, and what is the safest way to recover the mailbox?
3 Answers
If the mailbox is not recoverable, export it to a PST, verify the export, then recreate the mailbox and import the data. That is often faster than spending days chasing a damaged mailbox. A PST generally contains the mailbox data, not the underlying Exchange mailbox metadata or named-property state, so recreating the mailbox can remove the problem—but preserve anything important before deleting it.
The mailbox quota is still worth checking, including hidden or system-related limits, even if the user has not reached the normal storage quota. A normal quota warning would not usually explain all these symptoms, but a named-property limit or mailbox metadata problem could.
This looks more like a mailbox-level problem than an Outlook or database issue. Check whether the mailbox has exceeded the named-property quota. That can cause sending, OWA access, and mailbox moves to fail even when the database itself is healthy. The failed move and repeated MAPI errors make this especially worth investigating.
Could the underlying issue be carried into the PST during the export? I want to make sure I do not recreate the same problem.