{"id":88078,"date":"2021-09-28T07:15:07","date_gmt":"2021-09-28T07:15:07","guid":{"rendered":"https:\/\/www.stellarinfo.com\/blog\/?p=88078"},"modified":"2026-05-01T06:37:19","modified_gmt":"2026-05-01T06:37:19","slug":"microsoft-exchange-data-storage-connection-failedtransientexception","status":"publish","type":"post","link":"https:\/\/www.stellarinfo.com\/blog\/microsoft-exchange-data-storage-connection-failedtransientexception\/","title":{"rendered":"How to Fix the Error: Microsoft.Exchange.Data.Storage.ConnectionFailedTransientException?"},"content":{"rendered":"

When trying to open the Exchange Admin Center (EAC) to manage your Exchange Server or servers, you may get the error Microsoft.Exchange.Data.Storage. ConnectionFailedTransientException<\/strong>. The complete error message reads as:<\/p>

X-ClientId: T1T8 – TACB – 1UYP – EFDPEZGA<\/em><\/p>

X-OWA-Error: Microsoft.Exchange.Data.Storage. ConnectionFailedTransientException<\/em><\/p>

X-OWA-Version: 15.1.225.42<\/em><\/p>

X-FEServer: BRA-EXCHANGE<\/em><\/p>

X-BEServer: BRA-EXCHANGE<\/em><\/p>

Date: 18\/02\/2017 22:07:53<\/em><\/p>

\"Error:<\/figure>

This error may also appear when accessing mailbox using the Outlook Web Application (OWA).<\/p>

The error message indicates that there is an issue while connecting to the database or with the mailbox permissions.<\/p>

Reasons for Microsoft.Exchange.Data.Storage. ConnectionFailedTransientException Error<\/strong><\/h2>

Here are some possible reasons that can lead to this error:<\/p>

    \n
  1. Insufficient Permissions<\/strong>: If you do not have the required permissions to access a mailbox through OWA, you will get this error.<\/li>\n\n\n\n
  2. Unstable Network<\/strong>: If your network is unstable, it may cause issues while connecting the client to the Exchange Server, causing this error.<\/li>\n\n\n\n
  3. Configuration Changes<\/strong>: Updating the server with new security patches sometimes changes the server configuration. Due to this, you may not be able to access the mailboxes or EAC.<\/li>\n\n\n\n
  4. Database Corruption<\/strong>: If the database that contains the mailbox is corrupted, you may get this error.<\/li>\n<\/ol>

    Methods to Fix the Microsoft.Exchange.Data.Storage. ConnectionFailedTransientException Error<\/strong><\/h2>

    Here are the methods that can help you to resolve this error.<\/p>

    Method 1: Check and Assign the Mailbox Permissions to the User<\/strong><\/h3>

    You need to ensure that your user account has the permissions to access the mailbox or EAC. You can check this by using the Get-MailboxPermission<\/strong> PowerShell cmdlet. See the example below:<\/p>

    Get-MailboxPermission –Identity Anubhuti | Format-List<\/strong><\/code><\/pre>
    \"Get-MailboxPermission<\/figure>
    In the output, locate the mailbox that you want to access and check if the AccessRights<\/strong> field is showing the status as FullAccess<\/strong> and the InheritanceType<\/strong> is set to All<\/strong>.<\/p>
    If not, you can assign the permissions by using the Add-MailboxPermission<\/strong> cmdlet. See the below example:<\/p>
    Add-MailboxPermission –Identity Anubhuti –User Anu –AccessRights FullAccess –InheritanceType All<\/strong><\/code><\/pre>
    \"Add-MailboxPermission\"<\/figure>
    Once you have assigned the permissions, check if you’re able to access the mailbox.<\/p>
    Method 2: Check the Event Viewer<\/strong><\/h3>
    You can go back and track the changes from the time when the web applications were working to the time you started getting the error. Sometimes, changes in the configuration of server or installation of a third-party application can cause issues. To identify the cause of issue, you can check the Event<\/strong> Viewer<\/strong>.<\/p>
    \"Check<\/figure>
    After opening the Event Viewer, click on the dropdown button next to Windows Log,<\/strong> select Exchange,<\/strong> and view the settings.<\/p>
    \"Select<\/figure>
    If any particular setting is blocking the access to mailbox or EAC, change that setting. Then, try accessing the mailbox or EAC again.<\/p>
    Method 3: Mount the Database if it is Dismounted<\/strong><\/h3>
    You may not able to connect to mailbox if the database (where the mailbox is stored) is dismounted. You can check if there are any issues with the copy status of database by running the below command:<\/p>
    Get-MailboxDatabaseCopyStatus<\/strong><\/a><\/p>
    \"Get-MailboxDatabaseCopyStatus<\/figure>
    This will give an indication if there is a problem with the copy status of the database and if the database is mounted or not. If the database is not mounted, you can try to mount the database via the Exchange Management Shell (EMS) or by using the Exchange Admin Center (EAC).<\/p>
    To mount the database via EMS, you can use the following PowerShell command:<\/p>
    Mount-Database MyDatabase<\/strong><\/code><\/pre>
    \"Mount-Database<\/figure>
    Method 4: Repair the Corrupted Database<\/strong><\/h3>
    If the database fails to mount, then there are chances that the database is corrupt. In such a case, you can try to repair the database by using the native utility – <\/strong>EseUtil<\/strong><\/a> and perform Soft Recovery, which will run a quick recovery of the database. This is ideal to start with as it can fix minor corruption issues. After this is successful, try to mount the database. If this is unsuccessful, you can perform the hard recovery. But it is to be noted that hard recovery would result in data loss. The other option is to restore the database from the backup. However, this would mean that any data from the backup until the error showed up would be lost.<\/p>
    To avoid data loss, you can use Stellar Repair for Exchange.<\/strong> This advanced Exchange repair software can recover mailboxes from corrupt database (EDB) files<\/a> and directly export them to a live Exchange Server. It can also save the recovered mailboxes to PST and various other formats. It can also export the repaired EDB file data directly to Microsoft 365 without any hassles. This software supports all the Exchange Server versions – from Exchange 5.5 to Exchange 2019.<\/p>
    \n