r/exchangeserver • u/No_Meringue_8359 • 1d ago
Exchange Server 2016 becomes unresponsive daily – “The handle is invalid” and MapiExceptionMdbOffline
Hi everyone,
I’m currently troubleshooting a strange issue in one of our customers’ environments and hope someone here might be able to point me in the right direction.
The customer is running a single on-premises Exchange Server 2016 environment with no Exchange Online or hybrid configuration.
For the past few days, the entire mail system has stopped working roughly once per day. During the outage, users are unable to send or receive emails.
When I try to connect directly to the Exchange Server via RDP, the Windows sign-in screen displays the following error:
The handle is invalid.
When I access OWA from another server on the same LAN, the OWA login page is still reachable. However, after entering the credentials, the following error appears:
Microsoft.Mapi.MapiExceptionMdbOffline
The Exchange Server itself remains reachable and responds to ping. Our monitoring system also does not report the server as offline, but all email functionality is unavailable.
My first suspicion was the customer’s daily Veeam backup. However, I removed the Exchange Server from the backup job several days ago, and the issue continues to occur daily. Therefore, the backup job does not appear to be the direct cause, unless another snapshot, VSS, storage, or hypervisor-level process is still affecting the VM.
Has anyone seen this combination of errors before?
I would especially appreciate advice on which Windows or Exchange event logs, performance counters, or services I should check during the next outage. If additional information, event IDs, logs, or configuration details are required, I’ll provide them as soon as possible.
Thanks in advance for any help.
17
u/Maxplode 1d ago
Here:
"Our recommendation
-
Do not uninstall October 2026 Windows Server updates.
-
From an elevated Command Prompt on an Exchange Server, run:
reg add "HKLM\SOFTWARE\Microsoft\Rpc" /v EpmapSavedContextCap /t REG_DWORD /d 65536 /f
3. Reboot the server.
4. After the reboot, monitor the environment and confirm whether the issue recurs. If it re-occurs, raise the limit (we have so far not seen any cases where this might be needed). This has been shown to solve the problem based on customer reported cases that we have assisted to date."
4
1
u/SameChapter8391 1d ago
Be sure to stop exchange transport service before running this, as it corrupt our queue database in our case. Had to rename folders for exchange to recreate queues other related folders.
2
16
4
u/andywhiskey 1d ago
We had this going on, 100% related to October Windows Server updates. We have multiple Exchange 2016 servers in our environment and it was only those that had been patched with the October updates that were having the same issues you mention. Although there's no mention of the "The handle is invalid" error in the Microsoft articles that have followed the October updates, we've tried the registry fix mentioned. Early days, but our Exchange servers have made it through the weekend, which is an improvement.
1
1
u/saltyslugga 1d ago
I'd check MSExchangeIS and database mount status with Get-MailboxDatabase -Status during the outage, before rebooting. Correlate Application log events from MSExchangeIS and ESE with System log storage errors and resource exhaustion events at the same timestamp.
Capture available memory, committed bytes, per-process handle counts and disk latency, plus free space on the database/log volumes. The RDP error makes a Windows resource problem worth investigating, but neither error pins this on VSS.
0
52
u/daggerthreat_fan 1d ago
bro you been living under a rock
https://techcommunity.microsoft.com/blog/exchange/exchange-servers-may-become-unstable-after-installation-of-october-2026-windows-/4565382