New-MailboxExportRequest cmdlet Failed -How to export mailboxes to pst

Summary: This blog explains how you can export mailbox to PST, when you face a New-MailboxExportRequest cmdlet Failed issue. Read on to know more.

Let us a take a look at a few scenarios.

Scenario 1: You run the cmdlet:

New-MailboxExportRequest <username> -FilePath \\servername\sharename\username.pst
After running, you face the below error message:

Couldn’t connect to the Source Mailbox.
+ CategoryInfo : NotSpecified: (0:Int32) [New-MailboxExportRequest], RemotePermanentException
+ FullyQualifiedErrorId : B1C4188,Microsoft.Exchange.Management.RecipientTasks.NewMailboxExportRequest

What to do next?

In this scenario, the most common issue is that the associated source mailbox is hidden from the GAL. In general, this error message does not look into every hidden source mailbox. There are combination of factors responsible for this error message. One such factor could be “hidden + litigation hold”

Solution 1: Unhide the Mailbox

The most common and basic solution to connect to the source mailbox. In this solution, you simply have to unhide the mailbox and export again.

Scenario 2:

[PS] C:\>Get-MailboxExportRequest | FL
RunspaceId: 024fbbda-19f7-47d7-960f-a511c52c7c76
FilePath: \\server\share\user.pst
SourceDatabase: CORP-DB1
Mailbox: company.com/Users/User
Name: MailboxExport
RequestGuid: a70af14e-d6eb-4631-985a-8bdb159b77f6
RequestQueue: CORP-DB1
Flags: IntraOrg, Push, Suspend
BatchName:
Status: Failed
Protect: False
Suspend: True
Direction: Push
RequestStyle: IntraOrg
OrganizationId:
Identity: company.com/Users/user\MailboxExport
IsValid: True
ObjectStat: New

In this situation, find the event log and more useful information i.e, the reason. Here, in this scenario, the reason is corrupted items excess than the stipulated for the move request. Adding more, it also has the legal hold enabled.
Log Name: Application
Source: MSExchange Mailbox Replication
Date: 1/31/2016 5:25:35 AM
Event ID: 1100
Task Category: Request
Level: Error
Keywords: Classic
User: N/A

Description:
Request ‘RequestGuid (a70af14e-d6eb-4631-985a-8bdb159b77f6), RequestQueue: (fc69518e-824e-4edd-a91a-62a3b61f582e)’ (a70af14e-d6eb-4631-985a-8bdb159b77f6) failed.

Error code: -2146233088
In this mailbox, the maximum number of corrupted items are more than the specified for the move request.
Context:
——–
Folder: ‘/Recoverable Items’, entryId [len=46, data=000000006E82A1713AC59842B25E5F99B17A025C0100E860929A75F299468B47B5CDC03D99F5000000149F0A0000], parentId [len=46, data=000000006E82A1713AC59842B25E5F99B17A025C0100E860929A75F299468B47B5CDC03D99F5000000149EDD0000]
Here in this situation, the reason for cmdlet fail is the presence of bad sectors in the recoverable items folder. The best method to resolve this concern is to state clearly the number of bad sectors that you can skip in the export process.

Solution 2: Set-MoveRequest
Follow the steps below:

• Open Exchange Management Shell.
• Type Set-MoveRequest.
• Select the number of bad items that you wish to ignore.

Set-MoveRequest -BadItemLimit 50 -AcceptLargeDataLoss -Identity “UserName” –AcceptLargeDataLoss

Solution 3: New-MailboxRequest

• Click and open Exchange Management Shell
• Now, exclude all the existing mailbox export request
• Once you are done with it, get the mailbox using the cmdlet(Get-MailboxExportRequest | FL). Example: Get-MailboxExportRequest -Mailbox “company.com/Users/XYZ” | Remove-MailboxExportRequest
• Now, create an export request for new mailbox. Do ensure to state the acceptable bad item limits
New-MailboxExportRequest -BadItemLimit 50 -AcceptLargeDataLoss -Identity “UserName” –AcceptLargeDataLoss

Scenario 3:

Couldn’t find the Enterprise Organization container.
+ CategoryInfo: NotSpecified: (0:Int32) [New-MailboxExportRequest], OrgContainerNotFoundException
+ FullyQualifiedErrorId : D310F4E6,Microsoft.Exchange.Management.RecipientTasks.NewMailboxExportRequest
This type of errors usually arises when we do not assign Mailbox Import Export role based access control (RBAC) management role to the Exchange administrator’s account.

Solution 4:

Simple way to resolve this issue is assign your account the Mailbox Import Export RBAC management role. Method to assign this role is as follows:

Run cmdlet:
New-ManagementRoleAssignment -Name “name” -SecurityGroup “security_group_name” -Role “Mailbox Import Export”

Apart from the afore-mentioned scenarios, the other possible Scenarios in which the Exchange Administrator Receive an Error Message are as follows:

• While exporting the contents of a mailbox to a .pst file
• While installing Microsoft Exchange Server 2010 Service Pack 1 (SP1) or Service Pack 2 (SP2)
• While running New-MailboxExportRequest cmdlet.

An All-in-one Comprehensive Solution

In addition to these specific solutions, the one sure-shot solution to cater to all PST Export issues is Stellar Converter for EDB tool. Coming from the noteworthy leader, Stellar Converter for EDB is a truly a perfect metaphor of exceptional functionality and remarkable quality. Acclaimed as a top-performer, this easy and economical solution is tried, tested, and approved by renowned data recovery experts.

Stellar Converter for EDB: Synopsis

Simple, efficient, easy, powerful, and reliable are some of the key attributes that best describes the Stellar Converter for EDB software. This dedicated professional software is a perfect solution to convert MS Exchange database files mailboxes into the PST File. Using this outstanding do-it-yourself software, you can easily convert both Online and Offline Exchange databases.

The best thing about this user-friendly approach is features such as Selective conversion option, multiple files conversion flexibility, support to restore converted mailbox to Office 365, specific mail searching option from the converted file, support for the archive mailboxes conversion, preview option, and ability to save results in various formats such as HTML, RTF, and PDF. This dedicated software is compatible with MS Exchange Server 2016, 2013, 2010, 2007, 2003, 2000, 5.5 and Office 2016, 2013, 2010, 2007, and 2003.

How to Export Mailboxes to PST Using Stellar Converter for EDB

In case of Offline EDB Files Conversion:
The offline EDB File Conversion is further divided into two phases.

First Phase—EDB File Selection

• Click on the File Menu.
• Select the EDB File.
• Run Stellar Converter for EDB.
• A dialog box will pop up. From this dialog box, choose the Conversion Mode and then select Offline EDB section.
• Click on Open EDB.
• Now, choose the file that you want to convert (If you are unware about the file location, use Find option).
• After selection of the desired file, click Ok.

Second Phase— EDB File Conversion

• Click on Start
• After successful completion of the conversion process, a list of all the converted file will be enlisted under the Root node in a tree-like structure.
• Go to the list and choose the desired file that you wish to preview.
• After a successful preview completion, choose the desired mailbox folder and simply click on the Save option.
• Now, a new window will pop up with a list of file saving format. Choose the PST option and state the location where you want to save file.
• Click on OK.

In Case of Online EDB Files Conversion

In situations, where you are in complete connectivity with the Exchange Server, you are able to view the mailbox as well as status easily. Adding more, in conditions when you are connected to all the mailboxes on the server, you see a list that includes all the mailboxes of the server along with their status. In this state, simply click on Ok and close it. Once you close it, you will be able to preview the selected EDB filename. On successful completion of preview, you can choose the desired EDB Files to migrate and click on the Save option.

The Way Forward

By now, you are aware of the MailboxExportRequest cmdlet Failed issue and their possible solutions. In addition, you can also leverage the third-party software, Stellar Converter for EDB, which ensures to resolve all your EDB to PST File conversion seamlessly. You may try the demo version from here.

Leave a Reply

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