Error Solved: “NewMailboxExportRequest” is not recognized in Exchange Server

Exporting Exchange mailbox data to PST format is pretty straightforward, thanks to the New-MailboxExportRequest command. However many a times, this command fails to complete the export operation successfully. In such a case, a reliable third-party tool such as Stellar EDB to PST converter can complete the required task quickly and efficiently.

Microsoft Exchange 2010 / 2013 makes use of Exchange Management Shell (EMS) commands to export mailboxes to PST format. EMS commands prove to be quite helpful for solving importing / exporting purposes and many other Exchange server tasks. Executing them does require a good level of technical know-how but still, they make for a free of cost and mostly accurate way of exporting mailbox contents from Exchange to PST.

Sometimes however, EMS cmdlets fail to accomplish their designated task. Take the case of “New-MailboxExportRequest” for example. Many Exchange administrators report that while attempting to export Exchange mailboxes to PST format using “New-MailboxExportRequest” command, the export request failed with the error “New-MailboxExportRequest” is not recognized. There could be several reasons behind this anomaly and several ways to resolve it. Let us visit each in detail, but first a brief introduction to the “New-MailboxExportRequest command.

The “New-MailboxExportRequest” Command

The New-MailboxExportRequest cmdlet is used to initiate the process of exporting a primary Exchange mailbox or archive to a PST file. What this command basically does is create a mailbox export request which when followed by more commands converts EDB file data to PST format.

This cmdlet can be used to create more than one mailbox export request per mailbox where each request must have a unique name. Moreover, to run this cmdlet you need to have appropriate permissions.

Primary causes behind the error

The most common reasons why you can face mailbox export fail include:

  • Exchange needs an update
  • You aren’t running EMS as administrator
  • The account performing the export request doesn’t have the required permissions

Depending upon what the actual cause is, you can use one of the solutions mentioned in the next section to resolve the error.

Solutions to the Error

  • Update Exchange by installing SP1 which is mandatory to execute the “New-MailboxExportRequest” command. Once updated, restart EMS to see if the command works now. If it doesn’t, move on to the next fix.
  • Instead of starting EMS through its shortcut, explicitly run it as Administrator by right-clicking on its icon and selecting ‘Run as Administrator’. Also, make sure you’re logged-in with administrator credentials. The actual EMS automatically disables much of the commands by default if not logged in and not running as administrator for security reasons.
  • The account initiating the export request needs to be granted the ‘Import Export Mailbox’ role. Grant yourself the role as follows:

New-ManagementRoleAssignment –Role “Mailbox Import Export” –User “DOMAIN\USER”

Once this permission has been assigned, restart your EMS session and try running the export request. It should work like a charm.

Why EMS Commands aren’t enough?

Although Exchange Management Shell and associated commands are sufficient for performing import / export operations and many other Exchange tasks, often, they fall short or fail to complete the task at hand. This happens because:

  • There are compatibility issues (32-bit / 64-bit)
  • Exchange Database Files (EDB) are damaged / corrupted / dismounted / offline
  • There are permission issues

Moreover, using EMS requires a good amount of technical knowledge and expertise. The slightest error could lead to data loss, potentially permanent. Although such tasks are usually performed by system administrators who are competent enough and knowledgeable, even they can face errors which are beyond their understanding.

The better way

To overcome all the above mentioned issues and ensure a simple process like Exchange mailbox export request stays simple, using reliable, automated, easy-to-use tools is ideal.

We recommend using Stellar Converter for EDB to export Exchange mailbox components to PST format. This professional utility assists you in extracting all vital Exchange mailbox data such as emails, contacts, attachments, etc. from online as well as offline Exchange Server database (EDB) files and efficiently converts them into equivalent Outlook PST files. The software is equipped with an interactive user interface and includes a bunch of other impressive features that make it the ideal choice for dealing with mailbox export fail and other EDB related errors.


Final Words

As is clear from the description above, simple things like missed updates or insufficient permission can put a halt to complex tasks. Thus, always make sure Exchange is updated and you have the appropriate permissions to execute the commands you’re trying to execute. For all other EDB problems, make sure you take the assistance of reliable tools like Stellar Converter for EDB. It can also be used when you need to extract mailbox data from Large & Multiple EDB files.

One Response

  1. Peter Gomes September 29, 2017

Leave a Reply

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