{"id":15623,"date":"2018-02-02T12:12:51","date_gmt":"2018-02-02T12:12:51","guid":{"rendered":"https:\/\/www.stellarinfo.com\/blog\/?p=15623"},"modified":"2025-10-07T11:10:11","modified_gmt":"2025-10-07T11:10:11","slug":"new-mailboxexportrequest-couldnt-connect-to-the-source-mailbox","status":"publish","type":"post","link":"https:\/\/www.stellarinfo.com\/blog\/new-mailboxexportrequest-couldnt-connect-to-the-source-mailbox\/","title":{"rendered":"Error Solved: new-mailboxexportrequest couldn’t connect to the source mailbox"},"content":{"rendered":"

Exchange server includes inbuilt utilities that can help database administrators (DBAs) perform the most complex of tasks easily, with the help of a few lines of code. However, utilities such as Exchange Management Shell (EMS) sometimes fail to perform the task owing to technical issues. In such cases, administrators can take the help of a reliable third-party software to accomplish what they set out to do.<\/p>

In this post we’re taking up the case of a failed new-mailboxexportrequest cmdlet issued to export Exchange mailboxes to PST format due to problems with connection or source mailbox. In such a case, you may experience the following error,<\/p>

\"Error:<\/figure>

Couldn’t connect to the source mailbox. MapiExceptionProtocolDisabled. Unable to make connection to the server.<\/p>

………………..<\/p>

………….<\/p>

Couldn’t connect to the source mailbox.<\/p>

    + CategoryInfo          : NotSpecified: (0:Int32) [New-MailboxExportRequest], RemoteTransientException<\/p>

    + FullyQualifiedErrorId : 6B6493C8,Microsoft.Exchange.Management.RecipientTasks.New-MailboxExportRequest<\/p>

About New-MailboxExportRequest Cmdlet<\/strong><\/h2>

Before heading to fixes and solutions, you must know about the New-MailboxExportRequest and its pre-requisites. The New-MailboxExportRequest cmdlet is used to export the contents of a primary Exchange mailbox to a PST file or archive it. This cmdlet is available only with the on-premise Exchange server 2010 SP1 or later versions. Also, only users assigned with the Mailbox Import Export role can use and execute this cmdlet.<\/p>

Thus, to use this cmdlet, you must assign the Mailbox Import Export role to a user or role group to which the user belongs. By default, this role isn’t assigned to any user or group, including the administrator.<\/p>

The syntax used to run New-MailboxExportRequest cmdlet is as follows,<\/p>

New-MailboxExportRequest -Mailbox <username> -FilePath “FullFilePath.pst”<\/code><\/pre>
By using this New-MailboxExportRequest  cmdlet, administrators can create multiple mailbox export requests, but each request should have a unique name. This unique name can be later used to view the progress or status of the export requests by using the Get-MailboxExportRequest cmdlet<\/p>
Methods to Fix “Couldn’t Connect to the Source Mailbox” Error<\/strong><\/h2>
While trying to export a user mailbox from EDB to PST<\/a>, if you encountered an error like “couldn’t connect to the source mailbox”, it indicates an underlying technical issue. Thus, the New-MailboxExportRequest cmdlet fails. To resolve this error, you must find the reasons and fix the issues. Plus, you need to ensure that the cmdlet is correctly executed.<\/p>
\n
To know more, read how to use the New-MailboxExportRequest cmdlet<\/strong><\/a><\/em><\/p>\n<\/blockquote>
1. Connectivity issues with the Exchange server <\/strong><\/h5>
 The reason for the ‘New-MailboxExportRequest couldn’t connect to the source mailbox’ error is most probably network related. Thus, you must check and verify that all the connections to servers and systems are working, before running the mailbox export commands. Also, ensure that you have the required permissions to access the folder paths and required files. Read More<\/strong><\/a><\/p>
\"Stellar\"<\/figure>
2. Disabled MAPI protocol<\/strong><\/h5>
The problem can also be associated with the MAPI protocol that permits access to MS Exchange mailboxes from MAPI clients such as Outlook. Thus, you must check that the MAPI profile is enabled\/disabled. If not, enable it to connect to Outlook and also check the ‘MAPIBlockOutlookNonCachedMode’ feature. The steps are as follows,<\/p>
    \n
  1. Check and rectify Internet connectivity and Exchange connectivity issues<\/li>\n\n\n\n
  2. Login to Exchange account through the Outlook Web App (OWA) and see if you can get through. If yes, manually export your inbox data to PST from the OWA.<\/li>\n\n\n\n
  3. Check if the MAPI mode is enabled or not by verifying the Client Access Server mailbox status of the user. For this either right-click on the user mailbox from the Exchange Management Shell (EMS) and check its properties or run the following command:<\/li>\n<\/ol>
    Get-CASMailbox –Identify user name<\/code><\/pre>
    \n
    \"Stellar\"<\/figure>\n<\/div>
    4.  To double-check if it’s working, disable the MAPI mode and re-enable it immediately. To disable it, use the following command:<\/p>
    Set-CASMailbox ID –MAPIBlockOutlookNonCachedMode:$false<\/code><\/pre>
    5. Now enable it through this command:<\/p>
    Set-CASMailbox ID –MAPIBlockOutlookNonCachedMode:$True<\/code><\/pre>
    6. Now run the export cmdlet again:<\/p>
    New-MailboxExportRequest–Mailbox USERID– FilePath\\\\SERVERNAME\\ SHAREPATH\\name.pst<\/code><\/pre>
    Alternative Method to Convert EDB to PST<\/strong><\/h2>
    If you’re still encountering the New-MailboxExportRequest couldn’t connect to the source mailbox error, use reliable third-party software to export mailboxes from Exchange server databases to PST.<\/p>
    We recommend using Stellar Converter for EDB<\/strong> to perform the EDB to PST export task. This professional Exchange database (EDB) to PST converter software is also recommended by Microsoft MVPs and IT admins to export PST from the Exchange mailbox database. Moreover, you don’t need additional permissions or roles to run this software. Only admin access is required to save EDB data to PST files. Plus, this powerful software can convert offline or hosted EDB files and export the data to PST, Office 365, or Live Exchange server without dismounting the Exchange database files.<\/p>
    In addition to the capability of performing the hassle-free and accurate conversion, the software is packed with other impressive features such as an interactive user interface, granular mailbox content export, and much more. You can start by downloading the free demo version by using the following link.<\/p>
    Conclusion<\/strong><\/h2>
    There could be several reasons why you’d need to export mailboxes from Exchange server EDB to PST format. New-MailboxExportRequest is one such cmdlet that makes it easy for the Exchange admins to create mailbox to PST export requests in MS Exchange 2010 SP1 or later versions. However, manual techniques and command-line scripts often come with their share of difficulties and risks. You may experience errors and technical challenges while exporting the PSTs.<\/p>