New-MailboxExportRequest Couldn’t Connect to the Source Mailbox

The Microsoft Exchange Server provides users with an option to export the items of the primary mailbox to Outlook compatible data file using the New-MailboxExportRequest cmdlet. Users can raise more than one mailbox export request per mailbox and every mailbox should have the unique name. There is another feature to remove already created an export request by using Remove-MailboxExportRequest cmdlet. Sometimes, the users might face some issues while using the cmdlet. One such issue is New-MailboxExportRequest couldn’t connect to the source mailbox. This article explains the solution to resolve the issue in an efficient way.

Know More About the Error

The Exchange Server users might not be able to utilize this option to export mailbox items to PST file format using the New-MailboxExportRequest cmdlet. Due to some problems, users are not able to transfer mailbox data and the New-MailboxExportRequest couldn’t connect to the source mailbox error pop-ups. The following command is used to convert the data to the PST file:

New-MailboxExportRequest–Mailbox USERID–FilePath\\SERVERNAME \SHAREPATH\name.pst

For exporting mailbox, the users can take help of the New-MailboxExportRequest cmdlet using the -Mailbox parameter. This specifies the source mailbox from where the mailbox items will be converted along with the -FilePath parameter. Then, specify the desired PST file which you want to create and export data in. In order to get a detailed information, you can try the following command line:

New-MailboxExportRequest–MailboxUSERID–FilePath\\SERVERNAME\ SHAREPATH\name.pst-Verbose

Important Note: Before trying any solution, you can try logging in to the account using OWA. If you are not able to do so, then first you have to resolve the issue and then try the Export process. If you can log in to the OWA and still getting the error, then you can proceed to the following solution.

Resolve New-MailboxExportRequest Couldn’t Connect to the Source Mailbox Error

Most of the problems associated with Mailbox Export request are due to MAPI protocol. This protocol allows or disallows the access to Exchange mailbox from the MAPI client such as MS Outlook. Thus, the first step is to check if MAPI protocol is enabled or not. It is the major factor which is required for connecting to Outlook. If a user wants to transfer Exchange mailbox while it is online, then the MAPIBlockOutlookNonCachedMode option should be checked. A user can perform the following steps listed below:

Get-CASMailbox –Identify username

We will check that the MAPI status is true or false. Moreover, we can also check the properties of the mailbox to verify if MAPI is enabled or not.

Set-CASMailbox ID –MAPIBlockOutlookNonCachedMode:$false

Set-CASMailbox ID –MAPIBlockOutlookNonCachedMode:$True

New-MailboxExportRequest–Mailbox USERID– FilePath\\SERVERNAME\ SHAREPATH\name.pst

Automated Solution to Resolve the Error

If you are still unable to export Exchange mailbox to PST format using the cmdlet scripts and getting the New-MailboxExportRequest couldn’t connect to the source mailbox error. Then the only remaining option is to use a reliable solution i.e. SysTools MailPro+ which will help you to perform the hassle-free conversion. It contains a lot of other features as well which makes the process easy even for the novice users.

Conclusion

There can be several reasons due to which users have the need to convert EDB files to Outlook file format. Moreover, relying on command line scripts or the manual procedure can be quite confusing and comes with a bit of risk and difficulties. Whether you are looking for a better server response or better storage management offered by PST file, the above-mentioned professional solution can help you to accomplish the task in a simple way.