Megha Sharma | Updated On - 23 Dec 2020 |

Read time 3 min

Errors are common while executing cmdlets in Exchange PowerShell or the Exchange Management Shell. For example, when a user uses
New-MailboxExportRequest cmdlet to export primary mailbox or archive content to PST file as under:.

Note: This export command is available only in Exchange on-premises. And to use it, you need to add the account to Mailbox Import Export role group.

Though it is an easy command to execute, sometimes an error can pop up. The error that gets displayed is –

Unable to open PST file ‘\\servername\sharename\user.pst’. Error details: Access to the path ‘\\servername\sharename\output.pst’ is denied.
+ CategoryInfo : NotSpecified: (0:Int32) [New-MailboxExportRequest], RemotePermanentException
+ FullyQualifiedErrorId : D7BD75A8,Microsoft.Exchange.Management.RecipientTasks.NewMailboxExportRequest
‘\\servername\sharename\user.pst’

Reasons for ‘New-MailboxExportRequest Access to Path is Denied’ error

While executing the cmdlet, the PST file location parameter should be a UNC path. And, the location should be a shared network with Read & Write permissions for Exchange Trusted Subsystem. Also, the user account performing the actions should have Mailbox Import Export permissions assigned to it. . Unfulfillment of these requirements while executing the New-MailboxExportRequest command might lead to the aforesaid “Access to Path Denied” error.

EASY SOLUTIONS TO FIX THE ERROR

We have 3 solutions to fix this error which can really work for you.

Let us consider manual solutions first for fixing the ‘Access path is denied’ error.

Solution No. 1 – Assigning Read & Write Permissions

One of the reasons for the access path denied error is that the Exchange Trusted Subsystem does not have enough rights over the folder. You should grant the Exchange Server access to the shared drive (read and write permissions to the Exchange trusted subsystem group).

To assign Read/Write permissions to the Exchange trusted subsystem group, right-click on the shared folder and click on the Properties option. Then switch to the Security tab, select the Exchange Trusted Subsystem permission and under Permissions for Exchange Trusted Subsystem section, select the Read & Execute and Write permissions checkboxes and click on OK. The permissions are now assigned.

Solution No. 2 – Adding The User Account To A Role Group With Mailbox Import-Export Permissions

Users can create a new role group with Mailbox Import Export permissions and add the user to it.
To create a new role group, execute the following command in Exchange Management Shell as the administrator:

Assigning Mailbox Export Import permissions to the account in this way will help you perform the export operation without errors.

Solution No. 3 – Using Kernel EDB to PST Converter Software [Best of the solutions]

Rather than trying manual ways to export Exchange mailbox data to PST, you can do it simply by using Kernel EDB to PST Converter software. The solution swiftly exports Exchange database mailboxes to Outlook PST files without any disturbing errors. It also repairs any corruption in EDB file and offers to Office 365 migration as well.

Conclusion

The frequently observed error – NewMailboxExportRequest (Access path is denied) can be fixed with different solutions. There are many limitations to manual solutions. But Kernel EDB to PST Converter, an alternative third-party solution, can perform the conversion without any issues.