The Exchange Administrator can use Exchange Management Shell to run several commands that provide a greater control and more in-depth reach towards the Exchange mailbox data. There are is great set of cmdlets that the Administrator can run and perform any action. Sometimes, the cmdlets show some problems while running in forms of several errors or warnings. These problems can cause corruption and deletion in the Exchange database and the Administrator should tackle these errors smartly.
You can also convert Exchange EDB Mailbox to PST using third party tools, but the present article focuses on removing the MailboxExportRequest cmdlet error while trying to transport or export the Exchange mailboxes to PST file. The article will show why does the error occur and how the Exchange Administrator can troubleshoot it.
What is the error?
The error that we are going to discuss basically in words is displayed like this –
“The Term ‘New-MailboxExportRequest’ is not recognized as the name of a cmdlet, function, script file, or operable program” this indicates that you have not been provisioned with the role.”
There are times when a user or organization requires moving the EDB data to PST file. The common reason for EDB to PST export is creating a backup of the Exchange database in PST file format which is easily accessible than the EDB file format in difficult times like data loss, Server crash, Exchange under maintenance, etc. One can also use free methods to convert Exchange EDB to PST file.
Microsoft Exchange Server 2010 and Exchange Server 2013 utilize the Exchange Management Shell commands to migrate the Exchange mailboxes to PST format. The EMS command that is being used by the Exchange Server 2010 for exporting the Exchange mailboxes is as given below:
Provide the correct respective values with Domain Controller name, Fully Qualified Domain Name mainly responsible for writing configuration changes to Active Directory.
This command creates a mailbox request and converts EDB mailboxes to PST with some more commands usage. This execution of the Exchange Management Shell commands certainly requires technical knowledge but is useful in exporting EDB data to PST. But there are situations when this mailbox-request becomes failed and in turn the user received the error message as mentioned above.
To reach the solution for this error, first it is important to know about the causes for it.
Why this error occurs?
In a simple manner, some of the effective reasons for the NewMailboxExportRequest is not recognized in Exchange Server are mentioned below:
- The user is using a shortcut for EMS rather than running it as an administrator
- Required permissions are unavailable with the account performing the execution
- Exchange Server requires an update
- Using Windows PowerShell in place of Exchange Management Shell
- Error(s) in spellings while writing commands
- Corruption in EDB files
- Compatibility issue with Windows System bit versions
Possible Solutions
1st Method – Assign the necessary role group
The MailboxExportRequest cmdlet is available to run in the on-premises Exchange Server only. It can export the content from primary mailbox and archive mailbox to a PST file. But, this cmdlet is active in Mailbox Import Export Role only. This role is not a member of any role group by default. If you are an Administrator, then you need to add the Mailbox Import Export Role in the Role Group.
- In the Exchange Admin Center, go to Permissions, then choose Admin Roles.
- Select the Role Group where you want to add the role and click Edit.
- In the Role section, choose Mailbox Import Export Role and save the changes.
- Save the Changes in the Admin Roles and come out of the wizard.
2nd Method – Use the proper parameters
If the cmdlet is stuck in the process due to problems in the source mailbox, then there are several parameters that can solve them. Some of the important parameters are-
- -AcceptLargeDataLoss: The parameter will allow the cmdlet to run even if a large number of items in the source mailbox can’t be copied. You do not need to input a number of items in the switch.
- -BadItemLimit: Bad Items Limit shows the corrupt items in the source mailbox that can’t be copied in the PST file. The parameter will set a number of bad items that are allowed before the request will fail. You can set the bad item limit and manage the faulty items in mailbox.
3rd Method
- One solution that you can try is choosing the ‘Run as Administrator’ by right clicking on EMS icon rather than using a shortcut for it. After that ensure that login credentials are also accurately written. EMS runs only with administrator rights with correct login credentials.
- Install SP1 and update Exchange if not done earlier as this is required to run the mailbox request command. Once updated, restart the EMS to see any difference.
- While writing the commands, check the credentials are accurate without any error in spellings. Domain Name has to be specified correctly within the command.
- The account should be given the ‘Import Export Mailbox’ role for the export request.
- Assign the permission with this command
New-ManagementRoleAssignment –Role “Mailbox Import Export” –User <domain >\ <username >
- Now run the export cmdlet, save to local path in this cmdlet
New-MailboxExportRequest <username> -Filepath \\<server>\location\<filename>.pst
- Look at the .pst export progress executing the following command
Get-MailboxExportRequest | Get-MailboxExportRequestStatistics
- Once export reaches to 100%, remove pst move request from the queue using this command
Get-MailboxExportRequest | Remove-MailboxExportRequest
- Assign the permission with this command
Here provide the respective details like – domain, username, server, location, filename, etc. as per assigned to the account in the Exchange Server for all of the above commands.
The solutions which are explained above may solve the error or work if it is not much severe. Sometimes, Exchange Database files are heavily corrupted or damaged, or permissions have some issues, or there are compatibility problems. So EMS commands are always not sufficient enough to export Exchange EDB data to PST file. Also, it would be hard for a non-technical user to execute such technical, complex commands. Data loss would be an issue with minor carelessness. And importantly, only system administrators have the right to perform the execution of the EMS commands. Exchange administrators and users have option to perform the export of EDB mailboxes to Outlook PST file more conveniently and securely by adopting a perfect professional tool that additionally supports recovery of Exchange mailboxes along with its export to PST and more destinations including Office 365 directly. Follow the next section to get an introduction about such EDB recovery tool.
Better Alternative Solution
To export the Exchange mailboxes to PST, use a professional, third-party Exchange Recovery tool for errorless both EDB recovery and migration. The tool is incorporated with the innovative features and friendly user-interface allowing exporting each file item of Exchange mailbox data to Outlook PST file. One can perform bulk mailboxes migration and even choose data for export via filters. The tool extensively supports all Exchange Server and Outlook versions. It would be best if user visit the software website to know about this tool in detail.
Conclusion
The discussion has been made over the error – NewMailboxExportRequest not recognized in Exchange Server, its causes and solutions. In the end, it has been experienced that the ultimate quick and easy solution to fix this error is using a third-party tool for the export of Exchange mailbox files to Outlook and more destinations flawlessly.
I am trying to export my mailbox with other employees and then this error occurs, to handle this problem I used this blogs methods. It becomes helpful and I am able to access my EDB mailbox with Exchange server.