New-mailboxexportrequest Access to Path Denied Error Message Resolved

While saving Exchange mailboxes data into Outlook Data format, Powershell commands “New-MailboxExportRequest used. But while using this cmdlet, the parameter with this commands should be correct otherwise, the user starts getting problem-related to access path is denied. Even sometimes there is a chance that folder will not have the permissions to allow the Exchange server to write into it. Due to this reason, the command would return the New-mailboxexportrequest Access to Path denied error message. Now, our task is to resolve this new-mailboxexportrequest Exchange 2010 Error message. First, let’s understand this PowerShell command and its working.

It can also be possible that a user is having an offline EDB file that he or she wants to export to PST format. For an instant, reliable, and hassle-free solution, SysTools EDB to PST Converter tool. It is one of the best way to extract mailbox from EDB File Exchange 2016/2013 to Outlook PST format. If you have damaged Exchange database file then user can use this utility easily  that resolve the database corruption Exchange 2010, 2013, 2016 and repair EDB File as well as mailboxes from corruption with no data loss.

About New-MailboxExportRequest Command in Exchange?

The Export command is available only in Exchange on-premises. People are using this cmdlet to start the exporting process of contents of a primary mailbox. However, this command is only available in the Mailbox Import Export role. In addition, the role is not assigned to any role groups by default. Thus, in order to use the Export Powershell command, you require adding the Mailbox Import Export role to the role group.

Role of New-MailboxExportRequest PowerShell Command

People execute the PowerShell command ‘New-MailboxExportRequest’ to export the PST files. But, If the MS Exchange trusted subsystem group does not have enough read and write permissions, then it leads the following error message:

[PS] C :\> New-MailboxExportRequest “userabc” -FilePath “\\MYSERVER\PST\userabc.pst”

Unable to open PST file ‘\\MYSERVER\PST\userabc.pst’. Error details: 
Access to the path ‘\\MYSERVER\PST\userabc.pst’ is denied

These are some most common parameter included with New-Mailbox Export Requests:

• [-BadItemLimit ]: Used when corruption issue arise while exporting data.
• [-IncludeFolders <String[]>]: Parameter used to include Specific Folder items while the export process.
• [-ExcludeFolders <String[]>]: Used to save information except for the folder in Exclude Folder Parameter.
• [-ContentFilter ]

User’s Problem
“I was trying to export Exchange mailboxes to PST file by using ‘New-MailboxexportRequest’ Powershell cmdlet. But I didn’t have any idea about the UNC path. So, I used to copy the normal path of the file. That is why the request becomes failed and I got an error message i.e. new-mailboxexportrequest access to the path is denied. Now, I want to resolve this error message. Please guide me what should I do to fix the New-MailboxexportRequest Exchange 2010 error without any data loss. You help or any suggestion would be appreciated!!”

How to Resolve New-mailboxexportrequest Access to Path Denied Error?

In this section, we will discuss the three most commonly used methods to fix the new-mailboxexportrequest Exchange error message. By using any of these solutions, users can easily resolve the cmdlet issue.

Solution 1: Grant Read and Write permissions

The new-mailboxexportrequest access to path denied error message can be resolved by giving the permission of “Read and Execute” to the Exchange trusted subsystem group. This permission allows them to execute the request. For granting the Read and Write permission, users need to click on the checkbox. After that, you will be able to resolve the error message “New-MailboxExportRequest Access to Path is denied”.

Drawbacks of Giving Read & Write Permissions

• PowerShell commands are unable to resolve the errors, all the time.
• These cmdlets are not applicable for Exchange 2007 & lower versions of Exchange.

Solution 2: Remove the ManagementRoleAssignments & Create a new Role Group

• Remove both Management Role Assignments

Remove-Management Role Assignment -Identity “Mailbox Import Export-exadmin-1”
Remove-Management Role Assignment -Identity “Mailbox Import Export-exadmin”

• Create a new Role Group

You need to follow the below commands to create the new Role group:

New-RoleGroup -Name “Exchange Mailbox Import Export” -Roles “Mailbox Import Export”
-Members“Domain\exadmin”-Display Name”Exchange Mailbox Import Export”

-Explanation “This group offers the access to the mailbox export & import command within the entire Exchange Server Organization.”

Drawbacks of with this Solution
It does not resolve the problem and displays access denied error message.

Solution 3: Fix Exchange Export  Acess Path Denied Error

PowerShell new-mailboxexportrequest method is a good option but it is too complex and takes lots of time. So, it is better to choose the SysTools Exchange Export Tool. Because this software is completely able to export Exchange mailboxes into PST file without any hassle.

With the help of this utility, one can easily move emails, contacts and other data items without generating an error message. You can use this automated application by performing the steps given below that easily bulk export mailbox to PST Exchange 2010, 2013, 2016:

• First of all, you need to install & run the Software

• After that, you can preview the mailbox name with permissions

• Now, apply the date filter to move data of specifics dates.

• Apply Different Filter: You can apply the different additional filter such as:

1. Maintain Folder Hierarchy
2. Split Resulted PST File

• At last click on Export Button to avoid any kind of access Path denied error.

Conclusion

The Powershell Export cmdlet is used to export the contents of the primary mailbox of Exchange to a PST file. But, sometimes these cmdlet occurs new-mailboxexportrequest access to path denied error message. Therefore, in this post, we have covered manual ways to resolve this error message. If you do not want to face this error and want to move multiple Live Exchange Server mailboxes to Outlook Data format then you can go mention the automated solution.