Warning: "continue" targeting switch is equivalent to "break". Did you mean to use "continue 2"? in /home/servertools/public_html/blog/wp-content/themes/schema/schema/options/php-po/php-po.php on line 187
{"id":706,"date":"2017-04-17T10:51:43","date_gmt":"2017-04-17T10:51:43","guid":{"rendered":"http:\/\/www.stellarservertools.com\/blog\/?p=706"},"modified":"2020-11-25T12:18:37","modified_gmt":"2020-11-25T12:18:37","slug":"new-mailboxexportrequest-cmdlet-failed","status":"publish","type":"post","link":"https:\/\/www.stellarservertools.com\/blog\/new-mailboxexportrequest-cmdlet-failed\/","title":{"rendered":"New-MailboxExportRequest Cmdlet Failed -How to Export Mailboxes to PST"},"content":{"rendered":"\n

Summary:<\/strong><\/em> In this blog, we explain how to export mailboxes to PST when New-MailboxExportRequest cmdlet fails or does not work. In addition, we outline some scenarios where this PowerShell cmdlet fails to export the mailboxes to PST. <\/em><\/p>\n\n\n\n

New-MailboxExportRequest is a PowerShell cmdlet to export or archive the primary mailbox to PST files in MS Exchange 2010 SP1 and later versions. However, at times, the New-MailboxExportRequest cmdlet fails to export the mailboxes to PST.\u00a0In such cases, you may attempt to fix the problem by troubleshooting various options or quickly export the mailboxes from Exchange EDB to PST by using an EDB to PST converter software, such as Stellar Converter for EDB.\u00a0<\/p>\n\n\n\n

However, to help you, we have discussed various scenarios where the New-MailboxExportRequest cmdlet may fail and how you can use the cmdlet to export mailboxes to PST successfully.<\/p>\n\n\n\n

\"\"<\/a><\/figure><\/div>\n\n\n\n

Why New-MailboxExportRequest Fails to Export PST?<\/strong><\/h2>\n\n\n\n

There could be several reasons and scenarios where New-MailboxExportRequest<\/em> cmdlet may fail to export mailbox to PST, such as:<\/p>\n\n\n\n

Scenario 1: Unsupported Exchange Version<\/h6>\n\n\n\n

You can execute New-MailboxExportRequest cmdlet on MS Exchange Server 2010 SP1 or later versions to export mailboxes from the Exchange database to PST. If you are trying to export a mailbox from an earlier version, the command will not execute.<\/p>\n\n\n\n

Scenario 2: Missing Required Permissions and Roles<\/h6>\n\n\n\n

In this situation, the user may receive the following error after executing the cmdlet,<\/p>\n\n\n\n

Couldn’t find the Enterprise Organization container.
+CategoryInfo : NotSpecified:<\/strong> (0:Int32) [New-MailboxExportRequest], OrgContainerNotFoundException
+FullyQualifiedErrorId<\/strong>:<\/strong>D320F6E8,Microsoft.Exchange.Management.RecipientTasks.NewMailboxExportRequest<\/p>\n\n\n\n

Thus, you must first assign this role by executing the following PowerShell command,<\/p>\n\n\n\n

New-ManagementRoleAssignment -Name \u201cname\u201d -SecurityGroup \u201csecurity_group_name\u201d -Role \u201cMailbox Import Export\u201d<\/code><\/pre>\n\n\n\n
Scenario 3: Hidden Mailbox<\/h6>\n\n\n\n
In this scenario, the most common issue is that the associated source mailbox is hidden from the global address list (GAL). In general, this New-MailboxExportRequest cmdlet does not look into every hidden source mailbox. Plus, there could be a combination of other factors responsible for New-MailboxExportRequest cmdlet failure. For instance,in Place Hold and Litigation Hold<\/a>.<\/strong><\/p>\n\n\n\n
New-MailboxExportRequest <username> -FilePath \\\\servername\\sharename\\username.pst<\/code><\/pre>\n\n\n\n
After running the above cmdlet, you may see the following error message:<\/strong><\/p>\n\n\n\n
Couldn\u2019t connect to the Source Mailbox.
+ CategoryInfo : NotSpecified<\/strong>: (0:Int32) [New-MailboxExportRequest], RemotePermanentException
+FullyQualifiedErrorId<\/strong>:B1C4188,Microsoft.Exchange.Management.RecipientTasks.NewMailboxExportRequest<\/p>\n\n\n\n
The basic solution to fix this is to connect to the source mailbox. You simply have to unhide the mailbox and export again.<\/p>\n\n\n\n
Scenario 4: Corrupted Items in the Mailbox<\/strong><\/h6>\n\n\n\n
The New-MailboxExportRequest cmdlet fails due to bad or corrupt items in the mailbox. As a result, the following message is displayed,<\/p>\n\n\n\n
[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<\/strong>
Protect: False
Suspend: True
Direction: Push
RequestStyle: IntraOrg
OrganizationId:
Identity: company.com\/Users\/user\\MailboxExport
IsValid: True
ObjectStat: New
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<\/p>\n\n\n\n
Description:<\/h4>\n\n\n\n
Request \u2018RequestGuid (a70af14e-d6eb-4631-985a-8bdb159b77f6), RequestQueue: (fc69518e-824e-4edd-a91a-62a3b61f582e)\u2019 (a70af14e-d6eb-4631-985a-8bdb159b77f6) failed.<\/p>\n\n\n\n
Error code: -2146233088<\/strong>
This mailbox exceeded the maximum number of corrupted items that were specified for this move request
Context:
\u2014\u2014\u2013
Folder:   \u2018\/Recoverable Items\u2019, entryId [len=46, data=000000006E82A1713AC59842B25E5F99B17A025C0100E860929A75F299468B47B5CDC03D99F5000000149F0A0000], parentId [len=46, data=000000006E82A1713AC59842B25E5F99B17A025C0100E860929A75F299468B47B5CDC03D99F5000000149EDD0000]

The solution is to specify the number of bad items that you want to skip in the export process. You can do this by using the \u2018Set-MoveRequest<\/strong>\u2019 cmdlet. The steps are as follows,<\/p>\n\n\n\n