Error Solved: This mailbox database is associated with one or more active mailbox export requests

Deleting an Exchange database after taking a backup of user mailboxes is a common task done by Exchange administrators. They can easily remove the Exchange database from the Exchange admin center (by navigating to servers>databases). Except sometimes, the process of deleting the Exchange database does not go well. Rather than deleting the Exchange database, the following error pops up. So here we will discuss the error “This mailbox database is associated with one or more active mailbox export requests”.

This error message is self-explanatory. It indicates that the reason behind the unsuccessful deletion or removal of the Exchange database is some active mailbox export requests that associate with the database. Some Exchange mailboxes are still in the queue for exportation.

So, the ultimate way to resolve this issue is by removing the active Exchange mailbox export request.

Removing/Completing Queued Exchange Mailbox Export Requests

For performing any operation related to Exchange mailbox export requests, ensure that the Exchange administrator is assigned the Mailbox Import Export role.

Run the Exchange Management Shell with administrative details and perform this command:

New-ManagementRoleAssignment -Role “Mailbox Import Export” -User <adminusername>

Promptly, the Exchange administrator can run the Get-MailboxExportRequest command to know if there is any active mailbox export request.

This command’s output can be a list of requests in the export queue with status as failed. If you do not want to export anymore, then try eliminating these mailbox export requests with this Management Shell command.

Get-MailboxExportRequest | Remove-MailboxExportRequest -Confirm:$false

Doing this will remove all the Mailbox Export Request held in the Exchange Management Shell.

On the contrary, if you are aware of the mailbox export request and like to proceed with this export, create a new Mailbox Export Request in the following manner:

New-MailboxExportRequest -Mailbox -FilePath “<PST folder network shared path>”

Once all mailboxes are export to PST files, Exchange administrators can now attempt to exclude the mailbox database again.

Using ADSIEdit to Remove the Database from AD Schema

Here we recommend a different way includes direct elimination of the mailbox database from the Active Directory Schema. It is possible using the ADSIEdit.

  • Log in to your Domain Controller.
  • , type ADSIEdit.msc, On the Start menu search bar, and launch the application.
  • In the opened ADSIEdit, follow Action>Connect to.
  • Below choose a well-known naming Context section, click on Configuration. In the opened tree-like hierarchy, move to CN=Configuration>DC=mydomain>DC=Local.
  • Then expand and navigate to CN=Services>Microsoft Exchange >mydomain>Administrative Groups>CN=Databases.
  • Select the database which you want to delete, right-click, and select the Delete option.
  • After this, open Command Prompt and run this command to check if the Schema is up dated or not.
  • Replamdin /replsummary
  • It will verify if you delete the database or not.

Now that users have all the possible fixes to solve the “this mailbox database is associated with one or more active mailbox export requests” error that appears while trying to delete the Exchange mailbox database.

As we have learned this error occurs while performing Exchange mailbox export manually using the New-MailboxExportRequest syntax, we would like to bring your attention to a simpler and error-free method to perform the Exchange mailboxes export.

For a clean export of mailboxes, trusting a proficient professional utility would be the best decision Exchange administrators can take.

Try this Automated Approach

Exchange EDB to PST tool integrates powerful algorithms that can scan the added offline EDB file, recover data from the corrupted database, make it available for preview to users, and then export it to the destinations such as PST, Live Exchange, Outlook Profiles, or Microsoft 365. The user interface is simple and easy to work with. Furthermore, the software supports all Exchange Server versions and not just the latest ones.


Deleting an Exchange Server database can become impossible owing to the failure of some mailbox export requests. You can be correct it by removing the export requests manually or by deleting them directly from the Active Directory Schema. Administrators have various options as described in this article to fix the Exchange “this mailbox database is associated with one or more active mailbox export requests” error.

Leave a Reply

Your email address will not be published. Required fields are marked *