Microsoft brought the Exchange Management shell tool equipped with Powershell cmdlets to manage the Exchange Server. The New-MailboxExportRequest is the basic Powershell cmdlet that enables administration for exporting single & multiple mailboxes to PST format for migration & backup reasons.
You may also be facing New-MailboxExportRequest failed problems like many others. If yes, you are at the right place. In this blog, you will learn about suitable ways of resolving the issue through the Exchange Management Shell (PowerShell cmdlets).
We will also discuss how Stellar Converter for EDB, the ultimate tool for EDB to PST conversion, can help solve the issue more conveniently. So, let’s start!
Introduction to New-MailboxExportRequest
The New-MailboxExportRequest cmdlet is useful for initiating the process of exporting components of the main mailbox & archiving them to a .pst file
When performing the export process through cmdlet, several problems may surface, such as:
- Hardware & software issues
- Improper execution of cmdlet, or
- Wrongly provided syntax of the cmdlet
These issues can lead to multiple errors throughout the process.
Types of New-MailboxExportRequest Error and their reason
Several errors might arise due to technical issues or other problems. Here are some of them followed by the reason behind their occurrence.
1. Error Code“0x80040115”
In this scenario, the user is unable to export the large mailboxes to PST. The error points out the issues in connection to one of the stores involved in the process. In several instances, the connection to PST is error-prone when the network accesses the PST.
2. New-MailboxExportRequest error-
New-MailboxExportRequest PowerShell in Exchange 2010 sets the content filter and utilizes dates in non-US format. The New-MailboxExportRequest error occurs when it fails to recognize the date in US formats.
3. Access denial error
The New-MailboxImportRequest PowerShell & New-MailboxExportRequest require a UNC path for the FilePath parameter. You cannot use
New-MailboxExportRequest -Mailbox MailboxName -FilePath C:\output.pst
Instead, you should use
New-MailboxExportRequest -Mailbox MailboxName -FilePath\\servername\sharename\output.pst
If the share & NTFS permission is not set properly on the destination path, you could get an error like this.
4. Other instances
Some more causes that might lead to New-MailboxExportRequest error include:
- The PST file’s position parameter is a UNC route while using the cmdlet.
- Connection errors with Exchange Servers
- Disabled MAPI control
- The Import Export permission of Mailbox allocated to the user account
- The location must be a public network with writing & reading abilities
- No access to permission roles & shared folder paths
- Issues with a particular mailbox
- Inconsistent database or the cmdlet contains the wrong parameters
- Wrong command syntax, lack of space on the server, or a disconnected mailbox
After covering the above reasons that cause the New-MailboxExportRequest error, it is time to resolve them.
Resolving New-MailboxExportRequest Failed errors
Here are the solutions to resolve New-MailboxExportRequest Failed errors by using the PowerShell cmdlets:
1. Check the failed mailbox export request
After checking the failed mailbox export request by utilizing the Get-MailboxExportRequest cmdlet,
This will clarify what went wrong so that you can see only the messages for failed commands.
2. Remove requests for completed mailbox export
Often, you might encounter error messages like- “Can’t connect to the mailbox database.” In this case, check whether it is accessible & then try again.
This issue occurs when the completion of exports from the mailbox database takes place, which does not exist. To know more about issues & to assess additional information, you may use Get-Mailbox Export Request Statistics with the Get-Mailbox Export Request cmdlet. Here is the command for the same:
Get-Mailbox Export Request- Status failed: Get-Mailbox Export Request Statistics- Include Report: Format-List> \\ex01\pstfiles\report.txt
Through this command, you can generate a brief report & save them for later. You can open the report in any text editor application and go through it to investigate & evaluate the errors.
3. Analyze Log file
If you scroll down the log file, you will find some more errors that may have led to the New-MailboxExportRequest cmdlet request error. In these scenarios, the problem is with content filtering of data or errors in date format.
4. Verify the time and location of the server
At times, the time & date do not correspond to the location & time of the server, so you need to verify the time & server location. Rectify the date and then re-execute them. Once you fix the date, you can successfully export the mailbox content.
Limitations with manual methods
Resolving the error issue with the help of PowerShell cmdlets is a task best executed by admins having keen knowledge of the ingrained technicalities. Here are the other restrictions of using these cmdlets.
- These methods are too technical and may create confusion in writing the commands.
- The command may take considerable time to execute.
- Due to some unnoticed syntaxes or other reasons, the cmdlets may fail to execute, resulting in the inability to resolve the New-MailboxExportRequest error issue.
To get away with such limitations, you can utilize 3rd party integration tools like Stellar EDB to PST conversion. It helps you to export PST files from the Exchange server without showing any errors. The entire process is quick and smooth, enabling you to correct the problem without hassle.
Using Stellar Converter for EDB
Stellar Converter for EDB aims to transform EDB’s offline/hosted files into PST with 100% precision. This software prioritizes supporting mailbox conversion without hampering the server’s performance.
It has become one of the top choices because of its potential to transform bigger EDB files into PSTs without any size limitations. Furthermore, it supports Exchange servers 2019, 2013, and all the previous versions.
Conclusion
When working on the Exchange database, you may encounter New-MailboxExportRequest errors. It could be due to any reason, such as lack of disk space, corrupted mailbox or Export request, invalid file path or permission, etc. To resolve the issue, you may try several PowerShell cmdlets.
Nevertheless, it can be a daunting task to resolve New-MailboxExportRequest errors through manual methods overall. The Stellar Converter for EDB, the widely used EDB to PST conversion tool can help your cause in this context.
The software can save considerable time and effort in resolving the issues. Moreover, it will export your mailbox smoothly and quickly. This third-party integration tool is reliable and worth considering to keep your business up and running.