The New-MailboxExportRequest cmdlet works in MS Exchange Server 2010 SP1 and later versions to export the data of a primary mailbox to a PST or archive file. It is available in the Mailbox Import Export role, which is not assigned to any role groups by default. Therefore, before using it, you must add the Mailbox Import Export role to a role group.
Admins use this cmdlet for mailbox migration, compliance, backup or archival tasks. At times, while working on it, users may get New-MailboxExportRequest failed error. If left unresolved, this issue may lead to hampered migration, incomplete backup, administrative downtime, and more.
Therefore, it is crucial to detect the root cause behind the error and come up with a faster issue. Here is detailed info on this topic.
What is the reason behind the Exchange Mailbox Export Request Failed error?
The New-MailboxExportRequest failed error can result from several reasons. Here are some common ones:
- No role-based permission: Microsoft requires role-based access permission from the users to facilitate secure data transfer during mailbox export. In the absence of an adequate role, the command will fail.
- Network issues: The connections to servers and systems should be in proper working condition before executing the New-MailboxExportRequest cmdlet. Failing it can cause a severe error.
- Disabled MAPI: The Messaging Application Programming Interface (MAPI) protocol allows applications to send and receive emails and use messaging services from Outlook and other MAPI clients. The export request will fail if you disable MAPI and stop the export.
- Corrupted mailbox data: Missing items or corrupted data in the target mailbox can be the reason behind the failed export request. To confirm this specific reason, run the Get-MailboxExportRequest cmdlet followed by checking the BadItemsEncountered field.
- Inaccessible database: When running the New-MailboxExportRequest, you may come across the error: Can’t connect to the mailbox database. To ensure this error does not happen again, verify the accessibility of the database.
- Use of wrong parameters: Using incorrect parameters or switches or wrong command syntax can also cause the request to fail.
- Incorrect date/time format: An incorrect date format used with the –ContentFilter parameter will create a mismatch with the time and location of the server. The InvalidContentFilterPermanentException error that occurs will require you to correct the format to resolve the export request error.
Types of Exchange mailbox export request errors and resolutions?
To know the error that is halting the mailbox export request, you have to check its requests by using the PowerShell cmdlet Get-MailboxExportRequest cmdlet. Here is the command:
Get-MailboxExportRequest | Get-MailboxExportRequestStatistics
If the command can detect the errors, use the following command to know about the error details in the log:
Get-MailboxExportRequest -Status Failed | Get-MailboxExportRequestStatistics -IncludeReport | Format-List
Depending on the outcome, here are the possible errors, followed by their resolution:
Error 1: “Couldn’t Connect to the Source Mailbox”
A common error faced by Exchange admins, it happens mainly due to a connectivity issue or a disabled MAPI on the mailbox. Often, the admins disable MAPI for some specific users when enforcing security policies. To resolve this error, you have to make your mailbox MapiEnabled. Here is the command to know the status.
Get-CASMailbox -Identity “roger.fed” | Select MapiEnabled
If the result shows FALSE, enable it by using the command below:
Set-CASMailbox -Identity ” roger.fed ” -MAPIEnabled $true
Error 2: Insufficient Permissions or Access Denied
Admins who are new to the Exchange Server environment are more likely to face this error. To run the New-MailboxExportRequest cmdlet successfully, the user must have the Mailbox Import Export management role assigned. Since it is not assigned to any role group or organization management by default, you have to do it manually. Here is the command:
New-ManagementRoleAssignment -Role “Mailbox Import Export” -User “AdminUser”
After assigning the role, close the Exchange Management Shell, and then reopen it. This is because the role assignment will not take place in the ongoing session. This move will allow the required Exchange-level permissions, enabling you to start the mailbox export request without hassles.
In addition, also check the NTFS permissions on the shared folder where you are about to export the mailbox data. The Exchange Trusted Subsystem security group should have full read/write permission to the shared folder.
Error 3: Bad Items Limit Exceeded
With time, mailboxes collect several corrupted emails, damaged headers, unparsed attachments, or misaligned calendar entries. When the mailbox data export request passes through these corrupted items, it does not skip them but stops by default. In the event of a New-MailboxExportRequest failed error, it will reflect as BadItemLimitExceededException in the failure report.
To fix this issue, increase the Bad Item limit when executing the export request:
New-MailboxExportRequest -Mailbox “roger.fed” -FilePath “\ServerShareroger_fed.pst” -BadItemLimit 50 -AcceptLargeDataLoss
This command will skip the corrupted items instead of stopping. The skipped items will not appear in the PST, which may be a concern for compliance reasons. Therefore, it is better to make this decision wisely.
Error 4: Large Items Limit Exceeded
Just like bad items, the limit of large items can also exceed the threshold for oversized mailboxes, e.g., more than 50MB. When it happens, it halts the mailbox export request, leading to an error. To deal with this situation, use the -LargeItemLimit parameter with the New-MailboxExportRequest cmdlet. Here is the command:
New-MailboxExportRequest -Mailbox “roger.fed” -FilePath “\ServerShareroger_fed.pst” -LargeItemLimit 20 -AcceptLargeDataLoss
The command will skip the items that exceed the threshold instead of exporting them. Hence, you should be careful when running it.
Error 5: InvalidContentFilterPermanentException
This error results from a mismatch in the date format when using the -ContentFilter parameter. You must ensure to match the format with the server’s regional settings instead of your local machine. Even a difference of MM/dd/yyyy and dd/MM/yyyy in the date format is enough to cause the error. To resolve this issue, make sure the data format on your workstation matches the regional configuration of your server. Once confirmed, run the request again. Here is the PowerShell cmdlet:
ContentFilter {Received -gt ’02/25/2025′}
Error 6: UNC Path Issues
The local paths will not work with New-MailboxExportRequest unless you use a UNC path in the –FilePath parameter in the following format: \ServerNameShareNamefilename.pst
Additionally, ensure that the path is shareable and reachable from the Exchange Server alongside your workstation. Access the UNC path directly from the Exchange Server to find out if the path provided is correct.
Error 7: Export Request Already Exists
If you create a new export request without removing an old request, even if a failed one, it will create a conflict. This is because the Exchange records every export request, including the failed ones. Therefore, before initiating the new request, make sure to clean the old request by using the following command:
Remove-MailboxExportRequest -Mailbox “roger.fed” -RequestName “MailboxExport”
You can also remove all failed requests through a single command instead of removing individual requests. Here is the command:
Get-MailboxExportRequest -Status Failed | Remove-MailboxExportRequest
Once done, proceed to create a new request.
Additional tips to avert failures
Besides resolving these errors, you should also be aware of some ideal practices to avert failures while executing the New-MailboxExportRequest.
- Use UNC paths with proper permissions and pointing to shares before starting
- The connectivity to source mailboxes should be intact before carrying out the bulk export
- Choose non-peak hours to run the export requests. This will minimize the chances of errors from resource restrictions
- Document the role assignments properly to avoid struggling for permissions in the middle of an export request
Using an EDB to PST converter
Manual fixing of the errors resulting from Mailbox export request errors could be troublesome, time taking, and prone to further errors. Moreover, those recently shifted to the Microsoft Exchange Server environment or users with limited technology may find it hard to resolve the errors. A better and more concrete measure to deal with New-MailboxExportRequest failed errors could be to use an EDB to PST converter, such as Stellar Converter for EDB.
Conclusion
The New-MailboxExportRequest helps to export mailboxes and the contained data to PST or archive files. To carry out this request, the user must have the Mailbox Import Export role assigned, which does not exist by default. Once you get the requisite permission access, you can continue with the request. During the execution of the request, there is always the possibility of encountering a New-MailboxExportRequest failed error.
In such a situation, you should go through the failure report or error log generated by the Get-MailboxExportRequestStatistics –IncludeReport command. Instead of jumping to conclusions, it is better to read this log to detect the FailureType. It can show any of the several errors, like Couldn’t Connect to the Source Mailbox, Large Items Limit Exceeded, UNC Path Issues, and more.
Depending on the New-MailboxExportRequest failed error, use the appropriate PowerShell command to fix and let the export request complete. Nevertheless, you may find these manual fixes troublesome, as they take excessive time, require you to have deep technical knowledge, and are likely to result in more errors. Using an EDB to PST converter such as Stellar Converter for EDB can be a feasible move to avoid such hassles.