The New-MailboxExportRequest cmdlet transfers mail items stored in the primary mailbox of an Exchange Server database to the PST file format. You can use this Exchange Management Shell (EMS) cmdlet to create mailbox export requests for multiple mailboxes, each with a distinct name. However, you should have special permissions to run this command.
To be specific, you will need to add the role of Mailbox Import Export to the role group, which remains unassigned by default to any group. At times, this command fails to create the mailbox export request and displays the error message, “New-MailboxExportRequest Couldn’t Connect to the Source Mailbox”.
In this blog, we will learn the causes behind this error, followed by methods to fix it and export the desired mail items or mailboxes to PST by using several utilitarian methods. We will also discuss the role of professional EDB to PST converter software, such as Stellar Converter for EDB, in resolving this issue with success.
Prominent Causes and Fixes for the Error
Using the new-mailboxexportrequest command to export an Exchange mailbox to PST format may fail due to several technical glitches. For proper execution of the command and for successful conversion, fixing this error is essential. Here are the root causes and relevant solutions for this error.
1. Connectivity Issue
Lag in network connectivity is one of the prominent reasons behind this New-MailboxExportRequest error. Unavailability of the required bandwidth can halt connectivity to the system and servers. Therefore, before executing any of the mailbox export commands, ensuring proper bandwidth is indispensable.
2. RBAC or Permission Issues
If you do not have the requisite Role Based Access Control (RBAC) or the necessary permission to use the mailbox file and the containing folder, it can cause an error. Make sure to have all the required permissions before requesting the EMS cmdlet.
3. Incorrect CU
The absence of the correct Exchange Cumulative Update (CU) or the necessary components can cause connection errors. A correct CU can remedy the error situation.
4. Corrupt or Damaged Mailbox
A damaged Exchange mailbox can be the source of the New-MailboxExportRequest error. To find the reason behind this error, use the Get-MailboxExportRequest cmdlet and then proceed with a suitable resolution to connect to the Source Mailbox.
5. MAPI Protocol Disabled
Ahead of all the other points, a disabled MAPI protocol can be a prominent cause behind the error. The Messaging Application Programming Interface (or MAPI) control points to a setting that determines if it is possible to access a user’s mailbox using MAPI clients, such as MS Outlook.
A disabled MAPI profile can be the key reason behind the New-MailboxExportRequest Couldn’t Connect to the Source Mailbox error. For smooth processing, enable this setting and connect to Outlook. Here are the steps:
- Check the internet and Exchange connectivity issues to rectify them
- Use your Outlook Web App (OWA) credentials to log in to the Exchange account
- If possible, export your inbox data to PST manually
- Find out if the MAPI mode is ‘Enabled’. For this, right-click the user mailbox from the EMS to check the Mailbox features
- Set the status of MAPI to Enabled, if not set by default
- You may also run the following command to serve this purpose:
Get-CASMailbox –Identify user name
- Verify the MAPI mode by setting its status to Disabled. Here is the command:
Set-CASMailbox ID –MAPIBlockOutlookNonCachedMode:$false
- Re-enable the MAPI mode immediately by using the command below:
Set-CASMailbox ID –MAPIBlockOutlookNonCachedMode:$True - Next, again run the export cmdlet: New-MailboxExportRequest–Mailbox USERID– FilePath\\SERVERNAME\ SHAREPATH\name.pst
Using a Third-Party Software for Error Resolution
Despite using all the manual methods, you may still struggle to deal with the New-MailboxExportRequest couldn’t connect to the source mailbox error. To recover from this situation, you can use professional EDB to PST converter software, such as Stellar Converter for EDB. It helps to easily export mailboxes from the Exchange server to PST without hassles. You don’t need additional Exchange Server permissions to use this software. You simply need admin access to save the EDB file to PST. Here are some of its main features
- Converts hosted or offline EDB files into PST with a high degree of precision.
- Converts EDB files of unlimited size into PST files
- Exports public folders and offline EDB files to Microsoft 365 or Live Exchange Server
- Use a parallel processing technique to process up to 8 mailboxes at once
- Gives the option to modify or set priority to mailbox conversion
- Enables the users to preview mailboxes and items to select/unselect mailbox items
- Converts EDB files into EML, MSG, HTML, RTF, and PDF formats
- Allows Export of contacts to CSV format
- Allows searching specific mails based on criteria, such as ‘To,’ ‘From,’ ‘Cc,’ ‘Subject,’ ‘Body,’ ‘Attachment’, etc.
Conclusion
Admins use the New-MailboxExportRequest command to export mailboxes and items to PST in the Exchange Server. Often executing this command gives “New-MailboxExportRequest Couldn’t Connect to the Source Mailbox” error. It could happen because of a network connectivity issue, permission requirements, a corrupt mailbox, or a wrong CU.
At times, a disabled MAPI profile can also trigger this error. Admins can resolve this issue by setting the MAPI status to Enabled by using the EMS command. If you still face the same error after trying all the methods, a better, quicker, and more feasible solution is to use professional EDB to PST converter software.
This is where Stellar Converter for EDB can prove highly effective. It allows users to export offline or hosted mailboxes to PST and several other formats. Additionally, many more capabilities of this software make it a widely recommended tool by MVPs worldwide.