{"id":43777,"date":"2026-11-02T14:34:03","date_gmt":"2026-11-02T09:04:03","guid":{"rendered":"https:\/\/www.wikitechy.com\/technology\/?p=43777"},"modified":"2026-11-02T14:38:22","modified_gmt":"2026-11-02T09:08:22","slug":"convert-edb-to-pst-when-built-in-command-fails","status":"publish","type":"post","link":"https:\/\/www.wikitechy.com\/technology\/convert-edb-to-pst-when-built-in-command-fails\/","title":{"rendered":"How to Convert EDB to PST When the Built-In Command Fails"},"content":{"rendered":"

When New-MailboxExportRequest fails, you can usually fix it in minutes, but if the database can’t be mounted or the server is gone, you need a tool that reads the EDB file directly.<\/span><\/p>\n

Exchange administrators export mailboxes to PST for many reasons: archiving a departed employee’s mail, answering a legal hold request, moving data off a server being retired, or handing a user a copy of their old mailbox. Microsoft’s built-in route is the New-MailboxExportRequest cmdlet. It works well when everything is in place. When it isn’t, the errors are often vague and the request can sit in the queue for hours.<\/span><\/p>\n

This guide covers how the built-in command works, the most common reasons it fails and how to fix each one, the situations where it can’t work at all, and how to convert EDB file to PST without Exchange Server when you hit those limits.<\/span><\/p>\n

The built-in method: New-MailboxExportRequest<\/b><\/h2>\n

New-MailboxExportRequest<\/span><\/a> exports a mailbox from a running, on-premises Exchange server to a PST file on a network share. It is available in Exchange 2010 SP1 and later, including Exchange 2013, 2016, 2019 and Exchange Server SE, and it is not available in Exchange Online.<\/span><\/p>\n

Before you run it, three things must be in place:<\/span><\/p>\n

    \n
  1. The Mailbox Import Export role.<\/b> Microsoft does not assign this role to any role group by default, so even an Organization Management admin can’t run the cmdlet until the role is added.<\/span><\/li>\n
  2. A UNC network share.<\/b> The FilePath must be a share path such as \\SERVER01\\PSTExports\\user.pst, not a local drive path like C:\\PST.<\/span><\/li>\n
  3. Share permissions for Exchange Trusted Subsystem.<\/b> This group needs Read\/Write permission on the share, because the Exchange server writes the PST, not your admin account.<\/span><\/li>\n<\/ol>\n

    The basic command looks like this:<\/span><\/p>\n

    # Grant the role to your admin account<\/span>
    \n<\/span>New-ManagementRoleAssignment -Role “Mailbox Import Export” -User admin01<\/span>
    \n<\/span>
    \n<\/span># Start the export and check its progress<\/span>
    \n<\/span>New-MailboxExportRequest -Mailbox jsmith -FilePath “\\\\SERVER01\\PSTExports\\jsmith.pst”<\/span>
    \n<\/span>Get-MailboxExportRequest | Get-MailboxExportRequestStatistics<\/span><\/p>\n

    Add -IsArchive to export a user’s archive mailbox instead of the primary one. After assigning the role, close and reopen the Exchange Management Shell so the new permission takes effect.<\/span><\/p>\n

    Why New-MailboxExportRequest fails, and how to fix it<\/b><\/h2>\n

    Most failures come from missing permissions, a bad file path, or corrupt items, and each has a direct fix. Start by pulling the failure report, because the cmdlet itself reports very little:<\/span><\/p>\n

    Get-MailboxExportRequest -Status Failed | Get-MailboxExportRequestStatistics -IncludeReport | Format-List > \\\\SERVER01\\PSTExports\\report.txt<\/span><\/p>\n

    Then match what you see against this table.<\/span><\/p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n
    Symptom or error<\/b><\/th>\nLikely cause<\/b><\/th>\nFix<\/b><\/th>\n<\/tr>\n<\/thead>\n
    “The term ‘New-MailboxExportRequest’ is not recognized”<\/span><\/td>\nThe Mailbox Import Export role isn’t assigned, or you’re connected to Exchange Online<\/span><\/td>\nAssign the role and reopen the Exchange Management Shell. In Exchange Online, use a Microsoft Purview eDiscovery export instead<\/span><\/td>\n<\/tr>\n
    Exchange can’t connect to the PST file on the share<\/span><\/td>\nA local path was used, or Exchange Trusted Subsystem lacks share permissions<\/span><\/td>\nUse a UNC path and give Exchange Trusted Subsystem Read\/Write on the share<\/span><\/td>\n<\/tr>\n
    “Couldn’t connect to the source mailbox”<\/span><\/td>\nThe mailbox database is dismounted, or the Mailbox Replication service is unhealthy<\/span><\/td>\nCheck with Get-MailboxDatabase -Status, mount the database, and restart MSExchangeMailboxReplication<\/span><\/td>\n<\/tr>\n
    Request stays in Queued for hours<\/span><\/td>\nThe Mailbox Replication service is hung, or DAG replication is unhealthy<\/span><\/td>\nRestart MSExchangeMailboxReplication, run Test-ReplicationHealth, then remove and resubmit the request<\/span><\/td>\n<\/tr>\n
    Fails with a bad items error (TooManyBadItemsPermanentException)<\/span><\/td>\nCorrupt items in the mailbox; BadItemLimit defaults to 0, so one bad item fails the job<\/span><\/td>\nAdd -BadItemLimit 10, or run New-MailboxRepairRequest first. On Exchange 2010, values of 51 or more also need -AcceptLargeDataLoss<\/span><\/td>\n<\/tr>\n
    Fails on oversized messages<\/span><\/td>\nItems exceed the message size limit; LargeItemLimit defaults to 0 (Exchange 2013 and later)<\/span><\/td>\nAdd -LargeItemLimit 10. Values of 51 or more also need -AcceptLargeDataLoss<\/span><\/td>\n<\/tr>\n
    Date-filtered export fails or returns nothing<\/span><\/td>\nContentFilter can’t export between two dates; it accepts a “from” or a “to” date, not both<\/span><\/td>\nUse a single date boundary and filter further in Outlook afterwards<\/span><\/td>\n<\/tr>\n
    New request is rejected for the same mailbox<\/span><\/td>\nExchange auto-names only 10 requests per mailbox (MailboxExport0 to 9), and failed requests aren’t removed automatically<\/span><\/td>\nClear old requests with Remove-MailboxExportRequest, or give the new one a unique -Name<\/span><\/td>\n<\/tr>\n
    Request times out calling the MailboxReplicationService<\/span><\/td>\nLoad balancer or CAS array misconfiguration (Exchange 2010)<\/span><\/td>\nPoint the request at a CAS outside the array with -MRSServer<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

    When the built-in command can’t work at all<\/b><\/h2>\n

    New-MailboxExportRequest only exports mailboxes from a mounted database in a live Exchange organization. It cannot read an EDB file on its own, so no amount of troubleshooting helps in these cases:<\/span><\/p>\n