Fix Error: New-MailboxExportRequest Access To Path Is Denied
Summary: While exporting the mailboxes from the Exchange database file (.edb) to PST using the New-MailboxExportRequest cmdlet, you may encounter a common error, “Access to the path is denied”—preventing you from exporting the mailboxes to PST. In this article, you will learn solutions to fix the error and quickly export all mailboxes to PST format with complete integrity by using the PowerShell cmdlet and an EDB to PST Converter software.
The ‘access path denied’ error in Exchange appears while executing the PowerShell commands, such as New-MailboxExportRequest. This usually occurs when a user tries to execute the New-MailboxExportRequest for PST export but doesn’t have sufficient rights over the folder (UNC). Thus, to successfully export mailbox to PST via New-MailboxExportRequest cmdlet, a user is required to define a UNC (Universal Naming Convention) path parameter with sufficient rights.
Reasons for ‘New-MailboxExportRequest Access to Path is Denied’ Error
When a user doesn’t have adequate permissions to ‘Read/Write’ Exchange Trusted Subsystem for network location, all mailbox-related requests are denied from the Exchange subsystem. In such a case, following error message is displayed,
New-MailboxExportRequest Access to Path is denied.
[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. + CategoryInfo : NotSpecified: (:) [New-MailboxExportRequest], RemotePermanentException + FullyQualifiedErrorId : [Server=MYEMAILSERVER,RequestId=23983583-a349-4c96-bb11-edb7d52b1a0a,TimeStamp=11/4/2017 6:55:33 AM] [Failure Category=Cmdlet-RemmanentException] 6DE05BB8,Microsoft.Exchange.Management.RecipientTasks. NewMailboxExportRequest |
The error may also occur if the user enters wrong UNC path in the PowerShell or doesn’t have Mailbox Import Export Role assigned. Even Exchange Administrators don’t have these rights by default. These permissions and assign roles are required to execute mailbox export or import cmdlets. In case it’s not possible, one may use a reliable professional EDB to PST Converter tool to convert the EDB or Exchange Database files into PST. It doesn’t require any additional permissions, besides administrator or mailbox access.
Solutions to Fix ‘New-MailboxExportRequest Access to Path is Denied’ Error
Below we have discussed a few solutions to fix the ‘access path denied’ error.
Solution 1: Grant Read & Execute Permissions
The problem can be resolved by granting the “Read & Execute” permissions to the Exchange Trusted Subsystem group and allow it to execute the request.
Once you check the box for “Read & Execute” permissions for Exchange Trusted Subsystem, you are able to fix the error “New-MailboxExportRequest Access to Path is denied”.
Drawbacks of Grant Read & Write Permissions
- PowerShell commands have limitations as these are unable to resolve the errors, all the time.
- These cmdlets are not applicable for Exchange 2007 and lower Exchange versions.
Solution 2: Remove the ManagementRoleAssignments and Create New Role Group
The alternate method to fix the error “New-MailboxExportRequest Access to Path is denied” is to remove both the ManagementRoleAssignments for exadmin and create a new Role Group.
- Remove both ManagementRoleAssignments for Exadmin
Remove-ManagementRoleAssignment -Identity “Mailbox Import Export-exadmin-1”
Remove-ManagementRoleAssignment -Identity “Mailbox Import Export-exadmin” - Create a new RoleGroup
New-RoleGroup -Name “Exchange Mailbox Import Export” -Roles “Mailbox Import Export” -Members “Domain\exadmin” -DisplayName “”Exchange Mailbox Import Export” -Description “This group provides access to mailbox export and import cmdlet within entire Exchange Organization.”
For more details read: How to manage role groups|Microsoft Doc
Drawback of the above solution
- Doesn’t resolve the problem and shows access denied error.
Solution 3: Deploy a Professional Software
A professional software like Stellar Converter for EDB helps in EDB to PST conversion where users do not have to undergo complex processes of assigning permissions, roles, and using command line tool for mailbox export.
With Stellar Converter for EDB, you can achieve better results and export multiple mailboxes at once to PST in a few clicks. All you need to do is,
- Install and open Stellar Converter for EDB software.
- Select and Scan EDB File.
- Preview and save mailboxes as PST file or export them to live Exchange server directly.
Why Prefer Professional Software over Manual Methods to fix Access Path Denied Error?
Sometimes, the incident-response activities are so complicated that users are unable to execute the complex commands in Exchange PowerShell. Instead of fixing the error, these commands further aggravate the problem, like in this case of “New-MailboxExportRequest access to path is denied”. To avoid such issues and make the system work at normal pace, it is best to introduce a professional software like Stellar Converter for EDB for Exchange database related problems. The preeminent part of using this software is that the user is able to forego the drawbacks of using complex PowerShell commands. The drawbacks of New-MailboxExportRequest are:
- Cmdlets are complex and lengthy in nature.
- Take more than the required downtime.
- Item preview is not available.
- Unable to save specific mail items.
Conclusion
The New-MailboxExportRequest cmdlet is used to export the contents of the primary mailbox to a PST file or archive to a PST file. The cmdlet is available in the Mailbox Import Export role, and this role is not assigned to any role group, by default. You need to add the Export-Import role to a role group to use this cmdlet. If these roles and permissions are not assigned to the user, including the administrator, it can lead to the error ‘New-MailboxExportRequest access to a path is denied’. To avoid any complications and export PST from the Exchange database without the ‘access path denied’ error message, you can use a GUI-based EDB to PST converter software. It not only prevents any possible errors but also recovers lost or deleted mailboxes during EDB scans.
I was trying to Export Mailbox to PST Access and facing Path Denied error in Exchange 2016. How to resolve path denied error message?
You can assign Read & Execute permission to the Exchange trusted subsystem group. If still error persists then try a reliable third-party tool which allows users to export Exchange mailbox to PST file format.
Double checked that permissions are correct, still cant export.
Hello Dennis,
Kindly share your problem in a detailed way. Then, we would be able to help you smoothly.
After using New-MailboxExportRequest command in Exchange Server 2013 it gives an error “Unable to open PST File. Access to path is denied.” Any help.
Ensure that the Exchange Trusted Subsystem group has full rights to share (read & write permissions). It will be able to resolve the error message.
one thing I found that was fun was I had to add the permissions not only to the security tab but also in the SHARE permissions if it’s a shared folder on the network.
Not sure why this was never a problem before but suddenly it was.
maybe windows update?
Yes!
Sometimes, a Windows update is also responsible for this one trouble. Please read the steps carefully to achieve 100% success.
While trying to import PST into mailbox getting this message:
Exchange 2010: New-MailboxExportRequest–“Access to the path is denied”
Need help.
You can enable Read/Write permissions to Exchange Trusted Subsystem for the network location. Through this solution, you can easily fix this error.
I also faced “New-MailboxExportRequest” error message while executing the PowerShell command. So, to fix this error I tried Stellar Converter for EDB tool and easily sorted this error.
Thank You!
Yesterday, I run this command but responded an error message:
Unable to open PST file ‘\\Server\Exports\Test.pst’. Error details: Access to the path ‘\\ExServer1\Imports\calgary_medical.pst’ is denied.
Please suggest!
Hi Olive,
To solve this error, you just need to grant permissions to the “Exchange Trusted Subsystem” group to allow it to read/write in the folder.
I am a PowerShell admin & full rights of administrative task. but, I still getting this error continuously.
Why?
In this situation, you can try an alternative solution like Stellar Converter for EDB.