How to Fix “The Mailbox With Mailbox Guid Caused A Crash Or Resource Outage On Database” Error?
Summary: Here in this write-up, we will provide the cause and solution to fix this error: “the mailbox with mailbox guid caused a crash or resource outage on database”.
Handling Microsoft Exchange Server is a very tough job. It requires highly technical skill, in-depth knowledge and hand-on experience to handle it. Also, it is prone to corruption, so it is the duty of Exchange administrator to keep the data safe & secure from unautorized users, from being corrupted or deleted.
Nowadays Microsoft are providing many new features in Exchange that ease the workload of Exchange admin. Then they don’t have to do all the work manually, these feature automatically perform their function. One of the feature that Microsoft introduced is automatic quarantining the Exchange mailboxes.
It is first came up in Exchange 2010 SP1 and then it is including in all above version. It is an excellent feature which is designed to detect the clients that are taking so much store attention, it basically means something is wrong.
Messaging Application Programming Interface (MAPI) client like Microsoft Outlook user many threads inside the store process when they are connected to the mailboxes. If a particular thread or more than it freeze then the Information store have to consume more CPU usage in order to provide service to the thread.
Why user have to be so worry about this feature? The reason is if more than five threads connected to the mailbox freezes for more than 60 sec or three thread crash in 2hr period, then the information store quarantine mailbox and considered to be in not a normal state. Then the application and users cannot access those mailbox for 24 hours.
Use the Exchange Get-MailboxStatistics PowerShell cmdlet to verify the that user Exchange mailbox is quarantined.
Get-MailboxStatics “Admin” | Select-Object DisplayName, IsQuarantined | Format-Table -AutoSize
If the mailboxes is quarantine the IsQuarantined parameter will display true or if not it will show false. Use the Disable-MailboxQuarantine PowerShell command give below to disable the quarantine mailbox.
Disable-MailboxQuarantine “Testing”
This Exchange PowerShell cmdlet will disable quarantine mailbox.
Sometimes, in Microsoft Exchange 2013 the mailboxes are unexpectedly quarantined and the DB is dismounted. It may also occur if the server is a member of DAG or it fails to another member of the Exchange Server.
What is the Cause Of “The Mailbox With Mailbox Guid Caused A Crash Or Resource Outage On Database” Error?
First, view the following error’s given below:
ID: 1014
Level: Warning
Source: MSExchangeIS
Machine: abc.example.com
Message: The mailbox with mailboxguid “xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx” has been quarantined. Access to this mailbox will be restricted to administrative logons for 1.00:00:00 since the last report.
ID: 1013
Level: Error
Source: MSExchangeIS
Machine: abc.example.com
Message: The mailbox with mailboxguid “xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx” caused crash or resource outage on database (GUID=”xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx”)
ID: 126
Level: Error
Source: ExchangeStoreDB
Machine: abc.example.com
Message: At ’11/11/2020 2:12:08 PM’ the Exchange store database ‘DAG1-DB1011’ copy on this server encountered an error that caused the database to be dismounted. For more detail about the failure, consult the Event log on the server for other “ExchangeStoreDb” or “msexchangerepl” events. A successful failover restored service.
This error occurs when the .Net Framework 4.6 is installed on the Exchange Server because this version is not supported in MS Exchange 2013.
Solution to Fix “The Mailbox With Mailbox Guid Caused A Crash Or Resource Outage On Database” Error
From Microsoft Exchange Server uninstall .Net Framework 4.6. It is a very simple solution to solve the error. But in some cases the Exchange database is damaged or corrupted that cause this issue which use the Exchange Server resources like – bad hard disk drive in RAID pack. Because of this the Exchange database or mailboxes is corrupted and then this result in dismount the database.
If the other database is not affected in Exchange Server then corruption is the cause of this problem.
In this case user have to repair the Exchange database and move all the mailboxes to the new Exchange database. For that, you can use the SysTools Exchange EDB File Repair Tool that easily repair corrupt offline/dismounted Exchange database and mailboxes with no data loss. The Quick & Advance scanning option of this recovery manager for Exchange database tool repair EDB file and mailboxes from corruption. After successful recovery of offline Exchange mailboxes, users can export it directly to the Live Exchange 2016 / 2013 / 2010 / 2007 / 2003 Server mailboxes in a hassle freeway.
Also users can export Exchange database mailbox to Office 365 and HTML, EML, PDF MBOX, MSG, PST file formats.
Bringing It All Together
This write-up provides detailed information on how to fix this error: “the mailbox with mailbox guid caused a crash or resource outage on database” by using the solution mentioned here. If the cause of the issue is corruption in Exchange database then users can resolve the database corruption Exchange 2010, 2013, 2016 without any loss of data and export the mailboxes to Exchange Server in a simplified way by using the automated wizard given in the above section.