none
New-MailboxExportRequest Couldn't connect to the source mailbox. RRS feed

  • Question

  • Exchange 2010 SP1
    2 servers (both CAS+DAG)

    When I try to export a mailbox I get the following error :

    cmdlet New-MailboxExportRequest at command pipeline position 1
    Supply values for the following parameters:
    FilePath: \\fileserver01\temp\stephan.van.hienen.pst
    Mailbox: stephan.van.hienen
    Couldn't connect to the source mailbox.
        + CategoryInfo          : NotSpecified: (0:Int32) [New-MailboxExportRequest], RemoteTransientException
        + FullyQualifiedErrorId : 3F21D713,Microsoft.Exchange.Management.RecipientTasks.NewMailboxExportRequest


    Any hints ?

    Thursday, September 9, 2010 11:05 AM

Answers

  • Mailbox Import or Export Requests may fail when using a Cisco ACE Load Balancer and a Client Access Server Array

    SYMPTOMS

    In Exchange 2010 Sp1, if you attempt to Export or Import a mailbox by using New-ExportRequest, or New-ImportRequest, the request may time out with the following error

    [PS] New-MailboxExportRequest -Mailbox "<Mailbox Name>" -FilePath "\\SERVERNAME\SHARE\filename.pst"

    The call to 'net.tcp://SERVERNAME/Microsoft.Exchange.MailboxReplicationService SERVERNAME (14.1.218.11 caps:07)' timed out. Error details: This request operation sent to net.tcp://SERVERNAME/Microsoft.Exchange.MailboxReplicationService did not receive a reply within the configured timeout (00:01:00).  The time allotted to this operation may have been a portion of a longer timeout.  This may be because the service is still processing the operation or because the service was unable to send a reply message.  Please consider increasing the operation timeout (by casting the channel/proxy to IContextChannel and setting the OperationTimeout property) and ensure that the service is able to connect to the client.
        + CategoryInfo          : NotSpecified: (0:Int32) [New-MailboxExportRequest], TimeoutErrorTransientException
        + FullyQualifiedErrorId : 59EDFA88,Microsoft.Exchange.Management.RecipientTasks.NewMailboxExportRequest

    CAUSE

    If a Client Access Array has been set up, and a Cisco ACE Load Balancer is being used with SNAT (Source NAT'ing) disabled, this can cause connections to time out on the load balancer because the MRS "client" is not honoring the session that has already been established. This will result in resets being issued and will result in the timeout errors above. This is due to the Mailbox Replication Service functioning as both a "Client" and as a "Server", and the client attempts to initiate direct connections to the server instead of using the session via the load balancer.

    When a mailbox import or export request is submitted, there are several steps to this process. Overall, it is very similar to the Move Request process.

    The basic process entails the following steps

    1. Exchange creates the request, then logs on and places a special message in the System mailbox of the database containing the mailbox to be exported or imported. The request will be placed into a Queued status.

    Note: this initial step is the step that fails with the error above, so the request is never placed into the System Mailbox.

    2. All MRS instances within the same AD site periodically check that mailbox. If no MRSServer is specified in the command, one will be randomly chosen. If a specific MRSServer is designated in the command, that MRS instance will be used.
    3. MRS begins the export (or import), and when finished, changes the export request to a status of Completed.
    4. Optionally, the export or import request can then be cleared by an administrator.

    See the following Technet article  for a description of the Move Request process, which covers these basic steps.

    RESOLUTION

    SNAT (Source NAT'ing) should be enabled on the Cisco ACE load balancer. Enabling SNAT will force the MRS "client" process to use the existing session via the load balancer.

    In addition, the following workarounds have been documented to allow the move request to be submitted. These workarounds can be implemented if enabling SNAT on the Cisco ACE load balancer is not possible.

    1. You can change the value of the RPCClientAccessServer on the Database containing the mailbox you wish to import or export to point to a specific CAS server instead of pointing to the CAS Array which will use the load balancer. This is a dynamic setting which can be changed on the fly.

    2. You can use the -MRSServer switch in the New-MailboxExportRequest or New-MailboxImportRequest cmdlet, and specify a CAS server that is not part of the CAS Array.


    Friday, May 6, 2011 12:12 PM

All replies

  • Are you using the right command? What are you typing in?

    Do you have enough rights?

     


    Rajith Enchiparambil | http://www.howexchangeworks.com |
    Thursday, September 9, 2010 11:48 AM
  • I'm running the command with the administrator account.

    and the comand :

    cmdlet New-MailboxExportRequest -Mailbox stephan.van.hienen -Filepath \\fileserver01\temp\stephan.van.hienen.pst

    Thursday, September 9, 2010 1:19 PM
  • Can you try the New-MailboxExportRequest again with -Verbose - it should show more about the error.

    Steve


    Steve Goodman
    Check out my Blog for more Exchange info or find me on Twitter

    Tuesday, September 14, 2010 8:22 PM
  • I'm getting the same error, but if I continue to issue the command it works and gets queued after 2 - 5 tries (never on the first).

     

    Eivind

    Wednesday, September 15, 2010 9:58 AM
  • Hi Stephan,

    Any luck with running it with -Verbose?

    Steve


    Steve Goodman
    Check out my Blog for more Exchange info or find me on Twitter

    Thursday, September 16, 2010 7:49 PM
  • [PS] C:\>New-MailboxExportRequest -Mailbox stephan.van.hienen -Filepath \\fileserver01\temp\stephan.van.hienen.pst -verb
    ose
    VERBOSE: [08:55:35.715 GMT] New-MailboxExportRequest : Active Directory session settings for 'New-MailboxExportRequest'
     are: View Entire Forest: 'False', Default Scope: 'nt.thepeoplesvalley.net', Configuration Domain Controller:
    'dc02.nt.thepeoplesvalley.net', Preferred Global Catalog: 'dc01.nt.thepeoplesvalley.net', Preferred Domain Controllers:
     '{ dc01.nt.thepeoplesvalley.net }'
    VERBOSE: [08:55:35.731 GMT] New-MailboxExportRequest : Runspace context: Executing user:
    nt.thepeoplesvalley.net/Users/admin, Executing user organization: , Current organization: , RBAC-enabled: Enabled.
    VERBOSE: [08:55:35.731 GMT] New-MailboxExportRequest : Beginning processing &
    VERBOSE: [08:55:35.731 GMT] New-MailboxExportRequest : Instantiating handler with index 0 for cmdlet extension agent
    "Admin Audit Log Agent".
    VERBOSE: [08:55:35.746 GMT] New-MailboxExportRequest : Current ScopeSet is: { Recipient Read Scope: {{, }}, Recipient
    Write Scopes: {{, }}, Configuration Read Scope: {{, }}, Configuration Write Scope(s): {{, }, }, Exclusive Recipient
    Scope(s): {}, Exclusive Configuration Scope(s): {} }
    VERBOSE: [08:55:35.746 GMT] New-MailboxExportRequest : Searching objects "stephan.van.hienen" of type "ADUser" under
    the root "$null".
    VERBOSE: [08:55:35.746 GMT] New-MailboxExportRequest : Previous operation run on domain controller
    'dc01.nt.thepeoplesvalley.net'.
    VERBOSE: [08:55:35.762 GMT] New-MailboxExportRequest : Searching objects "user1" of type "MailboxDatabase" under the
    root "$null".
    VERBOSE: [08:55:35.762 GMT] New-MailboxExportRequest : Previous operation run on domain controller
    'dc02.nt.thepeoplesvalley.net'.
    VERBOSE: [08:55:35.777 GMT] New-MailboxExportRequest : [DEBUG] MDB 8b377b24-9cc4-4c6e-976b-901ec47c78bb found to belong
     to Site: nt.thepeoplesvalley.net/Configuration/Sites/Amsterdam
    VERBOSE: [08:55:35.777 GMT] New-MailboxExportRequest : [DEBUG] MRSClient: attempting to connect to
    'EXCHANGENODE01.nt.thepeoplesvalley.net'
    VERBOSE: [08:55:36.167 GMT] New-MailboxExportRequest : [DEBUG] MRSClient: connected to
    'exchangenode01.nt.thepeoplesvalley.net', version 14.1.218.11 caps:07
    VERBOSE: [08:55:36.167 GMT] New-MailboxExportRequest : Processing object "RequestGuid
    (e55b3729-0090-4e7c-8e53-0ad9a01fb1c4), RequestQueue: (8b377b24-9cc4-4c6e-976b-901ec47c78bb)".
    VERBOSE: [08:55:47.431 GMT] New-MailboxExportRequest : Couldn't connect to the source mailbox. -->
    MapiExceptionNetworkError: Unable to make connection to the server. (hr=0x80004005, ec=2423)
    Diagnostic context:
        ......
        Lid: 15000   dwParam: 0x6BA      Msg: EEInfo: prm[2]: Pointer val: 0x4A2448D400000000
        Lid: 16280   dwParam: 0x6BA      Msg: EEInfo: ComputerName: n/a
        Lid: 8600    dwParam: 0x6BA      Msg: EEInfo: ProcessID: 3328
        Lid: 12696   dwParam: 0x6BA      Msg: EEInfo: Generation Time: 2010-09-20 08:55:47:431
        Lid: 10648   dwParam: 0x6BA      Msg: EEInfo: Generating component: 18
        Lid: 14744   dwParam: 0x6BA      Msg: EEInfo: Status: 10061
        Lid: 9624    dwParam: 0x6BA      Msg: EEInfo: Detection location: 318
        Lid: 13720   dwParam: 0x6BA      Msg: EEInfo: Flags: 0
        Lid: 11672   dwParam: 0x6BA      Msg: EEInfo: NumberOfParameters: 0
        Lid: 59505   StoreEc: 0x977
        Lid: 52465   StoreEc: 0x977
        Lid: 60065
        Lid: 33777   StoreEc: 0x977
        Lid: 59805
        Lid: 52209   StoreEc: 0x977
        Lid: 19778
        Lid: 27970   StoreEc: 0x977
        Lid: 17730
        Lid: 25922   StoreEc: 0x977
    VERBOSE: [08:55:47.431 GMT] New-MailboxExportRequest : Admin Audit Log: Entered Handler:OnComplete.
    Couldn't connect to the source mailbox.
        + CategoryInfo          : NotSpecified: (0:Int32) [New-MailboxExportRequest], RemoteTransientException
        + FullyQualifiedErrorId : A4D05D44,Microsoft.Exchange.Management.RecipientTasks.NewMailboxExportRequest

    VERBOSE: [08:55:47.446 GMT] New-MailboxExportRequest : Ending processing &

    Monday, September 20, 2010 8:57 AM
  • Hi Stephan,

    I am getting the same error. Did you manage to go further with this?

    Thanks,

    Friday, October 8, 2010 2:30 PM
  • I opened a supportcase last week, no updates yet.
    Monday, October 11, 2010 8:40 AM
  • one suggestion: try and enable source nat on the hardware load balance of the CAS array, this should solve the problem.
    Monday, October 18, 2010 6:00 PM
  • Lots of great suggestions from other team members and looks like you have a support case open as well.  If you cant get it working you should check out Lucid8's DigiScope http://www.lucid8.com/product/digiscope.asp since it can do all that you are looking for and more.
    Troy Werelius
    www.Lucid8.com
    Monday, October 18, 2010 7:39 PM
  • confirmed, source natting on the load balancer was the culprit in my case.
    Sunday, October 31, 2010 8:55 AM
  • have the same error on loadbalanced cas array. this works for me, but that can't be the solution:

    i changed the rpcclientaccessserver on the mailbox database to one cas server

    set-mailboxdatabase "mailboxdatabase" -rpcclientaccessserver cas1.domain.ch

    and then used the cas server as MRSServer

    New-MailboxExportRequest -Mailbox 'mailboxtoexport' -FilePath "Networkshare" -MRSServer cas1.domain.ch -Verbose

     

    Friday, November 5, 2010 10:04 AM
  • I realy don't like to change the settings in Exchange, so I tried some things and found this work arround:

    Add the IP of the MRSServer + the name of the CASARRAY to the hostsfile on the CAS/MRS Server

    It only needs to be in the HOSTS file while executing the new-mailboxexportrequest CMDLET.

     

    I wrote a Powershellscript that dynamically updates the local HOSTS file and starts the export on the fly.

    Find it on my blog:

    http://blog.exchange-guy.dk/2010/12/error-in-new-mailboxexportrequest-if.html


    MCT - MCSE Messaging & Security 2003 - MCTS SQL 2005, Vista & Exchange 2003-2010  / Enterprise Messaging Administrator 2010 Charter Member
    Monday, December 20, 2010 9:38 PM
  • Hi boys,

    is here any working solution for this problem ?

    [PS] C:\>New-MailboxExportRequest –Mailbox “organization\user” –Filepath “\\CASHUB01\PST\user.pst”
    Couldn't connect to the source mailbox.
        + CategoryInfo          : NotSpecified: (0:Int32) [New-MailboxExportRequest], RemoteTransientException
        + FullyQualifiedErrorId : 612C3665,Microsoft.Exchange.Management.RecipientTasks.NewMailboxExportRequest

    hostfile CAS/CASarray IP fake is not working for me.

    Thanks Biba

    Tuesday, May 3, 2011 10:16 AM
  • Hi Stephan,

    any news with this case? Same problem ...

    [PS] C:\>New-MailboxExportRequest –Mailbox “organization\user” –Filepath “\\CASHUB01\PST\user.pst”
    Couldn't connect to the source mailbox.
        + CategoryInfo          : NotSpecified: (0:Int32) [New-MailboxExportRequest], RemoteTransientException
        + FullyQualifiedErrorId : 612C3665,Microsoft.Exchange.Management.RecipientTasks.NewMailboxExportRequest

     

    Thanks B.

    Wednesday, May 4, 2011 5:58 AM
  • Mailbox Import or Export Requests may fail when using a Cisco ACE Load Balancer and a Client Access Server Array

    SYMPTOMS

    In Exchange 2010 Sp1, if you attempt to Export or Import a mailbox by using New-ExportRequest, or New-ImportRequest, the request may time out with the following error

    [PS] New-MailboxExportRequest -Mailbox "<Mailbox Name>" -FilePath "\\SERVERNAME\SHARE\filename.pst"

    The call to 'net.tcp://SERVERNAME/Microsoft.Exchange.MailboxReplicationService SERVERNAME (14.1.218.11 caps:07)' timed out. Error details: This request operation sent to net.tcp://SERVERNAME/Microsoft.Exchange.MailboxReplicationService did not receive a reply within the configured timeout (00:01:00).  The time allotted to this operation may have been a portion of a longer timeout.  This may be because the service is still processing the operation or because the service was unable to send a reply message.  Please consider increasing the operation timeout (by casting the channel/proxy to IContextChannel and setting the OperationTimeout property) and ensure that the service is able to connect to the client.
        + CategoryInfo          : NotSpecified: (0:Int32) [New-MailboxExportRequest], TimeoutErrorTransientException
        + FullyQualifiedErrorId : 59EDFA88,Microsoft.Exchange.Management.RecipientTasks.NewMailboxExportRequest

    CAUSE

    If a Client Access Array has been set up, and a Cisco ACE Load Balancer is being used with SNAT (Source NAT'ing) disabled, this can cause connections to time out on the load balancer because the MRS "client" is not honoring the session that has already been established. This will result in resets being issued and will result in the timeout errors above. This is due to the Mailbox Replication Service functioning as both a "Client" and as a "Server", and the client attempts to initiate direct connections to the server instead of using the session via the load balancer.

    When a mailbox import or export request is submitted, there are several steps to this process. Overall, it is very similar to the Move Request process.

    The basic process entails the following steps

    1. Exchange creates the request, then logs on and places a special message in the System mailbox of the database containing the mailbox to be exported or imported. The request will be placed into a Queued status.

    Note: this initial step is the step that fails with the error above, so the request is never placed into the System Mailbox.

    2. All MRS instances within the same AD site periodically check that mailbox. If no MRSServer is specified in the command, one will be randomly chosen. If a specific MRSServer is designated in the command, that MRS instance will be used.
    3. MRS begins the export (or import), and when finished, changes the export request to a status of Completed.
    4. Optionally, the export or import request can then be cleared by an administrator.

    See the following Technet article  for a description of the Move Request process, which covers these basic steps.

    RESOLUTION

    SNAT (Source NAT'ing) should be enabled on the Cisco ACE load balancer. Enabling SNAT will force the MRS "client" process to use the existing session via the load balancer.

    In addition, the following workarounds have been documented to allow the move request to be submitted. These workarounds can be implemented if enabling SNAT on the Cisco ACE load balancer is not possible.

    1. You can change the value of the RPCClientAccessServer on the Database containing the mailbox you wish to import or export to point to a specific CAS server instead of pointing to the CAS Array which will use the load balancer. This is a dynamic setting which can be changed on the fly.

    2. You can use the -MRSServer switch in the New-MailboxExportRequest or New-MailboxImportRequest cmdlet, and specify a CAS server that is not part of the CAS Array.


    Friday, May 6, 2011 12:12 PM
  • Make sure you have granted the Exchange Trusted Installer account at least Modify rights to the directory you are exporting the mailbox to.
    Tuesday, July 19, 2011 5:01 AM
  • Hi Stephan,

    Thank you for posting the resolution.


    Gulab | MCITP: Exchange 2010-2007 | Skype: Gulab.Mallah | Blog: www.ExchangeRanger.Blogspot.com
    Tuesday, July 19, 2011 5:45 AM
  • I'm trying to make a powershell script to export all mailboxes (~200) to pst files. The script runs ok for a random number of mailboxes (sometimes 20, sometimes 40), but never for all mailboxes. After throwing an error for one the mailboxes, any export request from a new mailbox will also throw an error.

    I reproduce here the same command found in the script for each mailbox with verbose parameter added. Curiously, the same command will execute succesfully after a random period of time.

    Is there a limit of number of export mailbox requests per batch?

    [PS] C:\Windows\system32>New-MailboxExportRequest -BatchName Backup_2011-11-13_15-1-19 -Mailbox somemailboxalias -FilePath \\s
    torage\MailboxBackup\Backup_2011-11-13_15-1-19\somemailboxalias.pst -MRSServer someserver.domain.com -verbose
    VERBOSE: [13:08:28.660 GMT] New-MailboxExportRequest : Active Directory session settings for 'New-MailboxExportRequest'
     are: View Entire Forest: 'False', Default Scope: 'domain.com', Configuration Domain Controller: 'someserver.domain.com',
    Preferred Global Catalog: 'someserver.domain.com', Preferred Domain Controllers: '{ someserver.domain.com }'
    VERBOSE: [13:08:28.660 GMT] New-MailboxExportRequest : Runspace context: Executing user: someserver.domain.com/Users/Administrator,
     Executing user organization: , Current organization: , RBAC-enabled: Enabled.
    VERBOSE: [13:08:28.660 GMT] New-MailboxExportRequest : Beginning processing &
    VERBOSE: [13:08:28.660 GMT] New-MailboxExportRequest : Instantiating handler with index 0 for cmdlet extension agent
    "Admin Audit Log Agent".
    VERBOSE: [13:08:28.660 GMT] New-MailboxExportRequest : Current ScopeSet is: { Recipient Read Scope: {{, }}, Recipient
    Write Scopes: {{, }}, Configuration Read Scope: {{, }}, Configuration Write Scope(s): {{, }, }, Exclusive Recipient
    Scope(s): {}, Exclusive Configuration Scope(s): {} }
    VERBOSE: [13:08:28.660 GMT] New-MailboxExportRequest : Searching objects "somemailboxalias" of type "ADUser" under the root
    "$null".
    VERBOSE: [13:08:28.676 GMT] New-MailboxExportRequest : Previous operation run on domain controller
    'someserver.domain.com'.
    VERBOSE: [13:08:28.676 GMT] New-MailboxExportRequest : Searching objects "Level 4 Database" of type "MailboxDatabase"
    under the root "$null".
    VERBOSE: [13:08:28.676 GMT] New-MailboxExportRequest : Previous operation run on domain controller
    'someserver.domain.com'.
    VERBOSE: [13:08:28.692 GMT] New-MailboxExportRequest : [DEBUG] MRSClient: attempting to connect to 'someserver.domain.com'
    VERBOSE: [13:08:29.456 GMT] New-MailboxExportRequest : [DEBUG] MRSClient: connected to 'someserver.domain.com', version
    14.1.325.0 caps:07
    VERBOSE: [13:08:29.456 GMT] New-MailboxExportRequest : Processing object "RequestGuid
    (c71f7380-f0d4-4372-aa2a-365bbdb5f5e1), RequestQueue: (17c3dec5-7ba6-4de6-a21a-1516bb815446)".
    VERBOSE: [13:08:29.581 GMT] New-MailboxExportRequest : Couldn't connect to the source mailbox. -->
    MapiExceptionCallFailed: Unable to make connection to the server. (hr=0x80004005, ec=2614)
    Diagnostic context:
        Lid: 59431   EMSMDB.EcDoConnectEx called [length=137]
        Lid: 34855   EMSMDB.EcDoConnectEx returned [ec=0xA36][length=56][latency=0]
        Lid: 59505   StoreEc: 0xA36
        Lid: 52465   StoreEc: 0xA36
        Lid: 60065
        Lid: 33777   StoreEc: 0xA36
        Lid: 59805
        Lid: 52209   StoreEc: 0xA36
        Lid: 56583
        Lid: 52487   StoreEc: 0xA36
        Lid: 19778
        Lid: 27970   StoreEc: 0xA36
        Lid: 17730
        Lid: 25922   StoreEc: 0xA36
    VERBOSE: [13:08:29.581 GMT] New-MailboxExportRequest : Admin Audit Log: Entered Handler:OnComplete.
    Couldn't connect to the source mailbox.
        + CategoryInfo          : NotSpecified: (0:Int32) [New-MailboxExportRequest], RemotePermanentException
        + FullyQualifiedErrorId : 11828CA4,Microsoft.Exchange.Management.RecipientTasks.NewMailboxExportRequest

    VERBOSE: [13:08:29.596 GMT] New-MailboxExportRequest : Ending processing &

     

    Sunday, November 13, 2011 1:25 PM
  • I'm trying to make a powershell script to export all mailboxes (~200) to pst files. The script runs ok for a random number of mailboxes (sometimes 20, sometimes 40), but never for all mailboxes. After throwing an error for one the mailboxes, any export request from a new mailbox will also throw an error.

    I reproduce here the same command found in the script for each mailbox with verbose parameter added. Curiously, the same command will execute succesfully after a random period of time.

    Is there a limit of number of export mailbox requests per batch?

    [PS] C:\Windows\system32>New-MailboxExportRequest -BatchName Backup_2011-11-13_15-1-19 -Mailbox somemailboxalias -FilePath \\s
    torage\MailboxBackup\Backup_2011-11-13_15-1-19\somemailboxalias.pst -MRSServer someserver.domain.com -verbose
    VERBOSE: [13:08:28.660 GMT] New-MailboxExportRequest : Active Directory session settings for 'New-MailboxExportRequest'
     are: View Entire Forest: 'False', Default Scope: 'domain.com', Configuration Domain Controller: 'someserver.domain.com',
    Preferred Global Catalog: 'someserver.domain.com', Preferred Domain Controllers: '{ someserver.domain.com }'
    VERBOSE: [13:08:28.660 GMT] New-MailboxExportRequest : Runspace context: Executing user: someserver.domain.com/Users/Administrator,
     Executing user organization: , Current organization: , RBAC-enabled: Enabled.
    VERBOSE: [13:08:28.660 GMT] New-MailboxExportRequest : Beginning processing &
    VERBOSE: [13:08:28.660 GMT] New-MailboxExportRequest : Instantiating handler with index 0 for cmdlet extension agent
    "Admin Audit Log Agent".
    VERBOSE: [13:08:28.660 GMT] New-MailboxExportRequest : Current ScopeSet is: { Recipient Read Scope: {{, }}, Recipient
    Write Scopes: {{, }}, Configuration Read Scope: {{, }}, Configuration Write Scope(s): {{, }, }, Exclusive Recipient
    Scope(s): {}, Exclusive Configuration Scope(s): {} }
    VERBOSE: [13:08:28.660 GMT] New-MailboxExportRequest : Searching objects "somemailboxalias" of type "ADUser" under the root
    "$null".
    VERBOSE: [13:08:28.676 GMT] New-MailboxExportRequest : Previous operation run on domain controller
    'someserver.domain.com'.
    VERBOSE: [13:08:28.676 GMT] New-MailboxExportRequest : Searching objects "Level 4 Database" of type "MailboxDatabase"
    under the root "$null".
    VERBOSE: [13:08:28.676 GMT] New-MailboxExportRequest : Previous operation run on domain controller
    'someserver.domain.com'.
    VERBOSE: [13:08:28.692 GMT] New-MailboxExportRequest : [DEBUG] MRSClient: attempting to connect to 'someserver.domain.com'
    VERBOSE: [13:08:29.456 GMT] New-MailboxExportRequest : [DEBUG] MRSClient: connected to 'someserver.domain.com', version
    14.1.325.0 caps:07
    VERBOSE: [13:08:29.456 GMT] New-MailboxExportRequest : Processing object "RequestGuid
    (c71f7380-f0d4-4372-aa2a-365bbdb5f5e1), RequestQueue: (17c3dec5-7ba6-4de6-a21a-1516bb815446)".
    VERBOSE: [13:08:29.581 GMT] New-MailboxExportRequest : Couldn't connect to the source mailbox. -->
    MapiExceptionCallFailed: Unable to make connection to the server. (hr=0x80004005, ec=2614)
    Diagnostic context:
        Lid: 59431   EMSMDB.EcDoConnectEx called [length=137]
        Lid: 34855   EMSMDB.EcDoConnectEx returned [ec=0xA36][length=56][latency=0]
        Lid: 59505   StoreEc: 0xA36
        Lid: 52465   StoreEc: 0xA36
        Lid: 60065
        Lid: 33777   StoreEc: 0xA36
        Lid: 59805
        Lid: 52209   StoreEc: 0xA36
        Lid: 56583
        Lid: 52487   StoreEc: 0xA36
        Lid: 19778
        Lid: 27970   StoreEc: 0xA36
        Lid: 17730
        Lid: 25922   StoreEc: 0xA36
    VERBOSE: [13:08:29.581 GMT] New-MailboxExportRequest : Admin Audit Log: Entered Handler:OnComplete.
    Couldn't connect to the source mailbox.
        + CategoryInfo          : NotSpecified: (0:Int32) [New-MailboxExportRequest], RemotePermanentException
        + FullyQualifiedErrorId : 11828CA4,Microsoft.Exchange.Management.RecipientTasks.NewMailboxExportRequest

    VERBOSE: [13:08:29.596 GMT] New-MailboxExportRequest : Ending processing &

     


    Hi Rumbu13,

    I am struggling with the same issue (with ec=2614) exporting 350+ mailboxes. The first 50 get queued without problems and then random failures en mailboxes that get queued.

    I am using a user with the right roles and i've created a new throttlingpolicy and raised the value of RCAMaxConcurrency to no avail.

    Did you find a solution yet or anybody else that can shed some light?

    Regards, Ed

    Thursday, November 24, 2011 10:19 AM
  • Hi Rumbu13,

    I am struggling with the same issue (with ec=2614) exporting 350+ mailboxes. The first 50 get queued without problems and then random failures en mailboxes that get queued.

    I am using a user with the right roles and i've created a new throttlingpolicy and raised the value of RCAMaxConcurrency to no avail.

    Did you find a solution yet or anybody else that can shed some light?

    Regards, Ed


    Hi everyone,

    I found the answer to my problem.

    We were having event id's 2915 from source MSExchange ADAccess on an Exchange 2010 server which put me on the wrong track whiel searching for the solution. Event ID 2915 states a threshold value of 100 and some user 'Sid~NT AUTHORITY\SYSTEM~RCA~false' who has gone over budget 'nnn' times for component 'RCA'. Information about this issue is very limited so I started with a new throttlingpolicy and assigned an account to it that has the import-export role. All of this led to nothing until I came across editing the MSExchangeMailboxReplication.exe.config, located in the \Exchange Server\V14\Bin folder.

    This config file sets the limits when moving (or exporting) your mailboxes. I've altered the following settings and am happily exporting 350+ mailboxes now.

    - Always first make a copy of the original config!!

    - Editing the value of MaxTotalMovesPerMRS = "100" to "500" did the trick...

    I thought I'd share this info because surely there are more people looking for this information.

    Regards, Ed


    • Edited by EdjeM Wednesday, November 30, 2011 4:29 PM
    Wednesday, November 30, 2011 4:29 PM
  • Check this link out http://www.stevieg.org/2010/07/using-the-exchange-2010-sp1-mailbox-export-features-for-mass-exports-to-pst/
    Troy Werelius
    www.Lucid8.com
    Search, Recover, & Extract Mailboxes, Folders, & Email Items from Offline EDB's and Live Exchange Servers with Lucid8's DigiScope
    Wednesday, November 30, 2011 4:38 PM
  • Check this link out http://www.stevieg.org/2010/07/using-the-exchange-2010-sp1-mailbox-export-features-for-mass-exports-to-pst/
    Troy Werelius
    www.Lucid8.com
    Search, Recover, & Extract Mailboxes, Folders, & Email Items from Offline EDB's and Live Exchange Servers with Lucid8's DigiScope


    Hi Troy,

    Thank you for your contribution.

    The script that stevieg wrote is the exact script I am using and the article doesn't mention anything about the issue stated above by Rumbu13

    Rumbu13:

    I'm trying to make a powershell script to export all mailboxes (~200) to pst files. The script runs ok for a random number of mailboxes (sometimes 20, sometimes 40), but never for all mailboxes. After throwing an error for one the mailboxes, any export request from a new mailbox will also throw an error.

    In particular the random number of mailboxes being queued and rejected was applying to our situation.

    Very usefull article though.

    Thursday, December 1, 2011 10:48 AM
  • This is not only for cisco ace firewalls but more firewalls types, NAT was disabled on the side of the customer, we enabled NAT on the firewall rules that makes the connection to exchange and now everything works. (in this case it was a Fortigate Firewall)

    the site from stevie.org what troy rights is a really good script, it works perfectly!

    maybe for the topic solution provider, please add this in your article?

    solution worked!

    Monday, January 30, 2012 12:23 AM
  • Hi!

    Make sure that Mapi for inbox is enabled.

    You can check this using command: Get-CASMailbox -Identity <mailbox> .


    Wojciech Sciesinski

    • Proposed as answer by Ashu103 Wednesday, August 22, 2012 6:57 PM
    Wednesday, February 29, 2012 10:32 PM
  • All,

    I had this same problem. 

    I have Exchange 2010 SP1 right now using the same cmdlet string you guys appear to be using.

    Strangely enough, the solution I found was to DISCONNECT the mailbox from the user and RECONNECT the mailbox to a common user we have created for this task.

    Once we opened the mailbox in Outlook, we were able to run the cmdlet again and everything worked fine.

    I wish it were a less work-intensive answer, but this is what we have so far.

    Good Luck, All!

    Thursday, May 3, 2012 8:40 PM
  • So I'm having the same issue also, with client connections going through a load balancer. However, the engineers confirmed that source natting is enabled on the load-balancers, but I'm still having the problem. Are there any other fixes that need to made on LB-side that could clear this up? I believe they are F5's

    To try to narrow the issue, I tried the HOSTS file trick tversteergaard mentioned above, this allowed the mailbox export to go through fine.

    I also changed the RPCClientAcceesServer attribute for an unused database to point directly to a CAS instead of the LB, and this also allowed the export to go through. However, I do not imagine this to be a practical solution, as client connectivity is affected if this attribute is changed for production DBs.

    Tuesday, May 8, 2012 9:57 PM
  • Im having the same issue - where we have to issue the new-mailboxexportrequest command several times for it to work - and we have only one Exchange server running all the roles. No load balanced CAS or cluster. 

    Go figure.

    Tuesday, August 7, 2012 10:39 AM
  • THANK YOU!!! This worked for me..after hours of digging around. :)
    Wednesday, August 22, 2012 6:57 PM
  • This was my fix for the problem. Thanks Wojciech!

    Wednesday, September 19, 2012 2:57 PM
  • I came across the issue after restoring our Exchange Server onto a lab enviroment. Thankfully for me the fix was quite simple - restart the Microsoft Exchange RPC Client Access Service
    Monday, December 17, 2012 12:11 PM
  • Please try to run the Clean-MailboxDatabase commad , it will resolve the issue

    [PS] C:\Windows\system32>New-MailboxExportRequest -Mailbox check -FilePath "\\db01\PST\1.pst"

    Couldn't connect to the source mailbox.
        + CategoryInfo          : NotSpecified: (0:Int32) [New-MailboxExportRequest], RemoteTransientException
        + FullyQualifiedErrorId : E08EACCD,Microsoft.Exchange.Management.RecipientTasks.NewMailboxExportRequest

    [PS] C:\Windows\system32>Clean-MailboxDatabase -Identity DB52
    [PS] C:\Windows\system32>New-MailboxExportRequest -Mailbox check -FilePath "\\db01\PST\1.pst"


    Name                                           Mailbox                                        Status
    ----                                           -------                                        ------
    MailboxExport                                  contoso.com/Organizations/Users a... Queued

    • Proposed as answer by Siva_shankar Friday, March 8, 2013 11:31 AM
    Friday, March 8, 2013 11:31 AM
  • I had this same problem and looked at the account under Exchange Managment Console. The LAN Admin had disabled all of the features on the account. It appears the Export requires MAPI in order to complete the Export as soon as I enabled this feature it worked. 

    Jessica Cochran

    • Proposed as answer by Mr. Choice Monday, September 14, 2015 10:12 AM
    Wednesday, May 15, 2013 2:05 PM
  • Apparently, there are multiple reasons for this error to occur. In my case, I had reconnected a mailbox. I couldn't export the mailbox, and the EMC still showed the mailbox as disconnected. I had to run the following cmdlet:

    Get-MailboxDatabase | Clean-MailboxDatabase

    I suppose this triggers the mailbox cleanup process. I also suppose, in many of the described cases, waiting a day for the task to run also solves the error.

    Thursday, June 20, 2013 2:25 PM
  • I had this issue in our Exchange environment, and it was because I copied the legacyExchangeDN as an X500 address onto a contact, because we were helping a customer migrate off our email system.

    I.E. Create contacts, set mailboxes to forward to those contacts, and we proactively grabbed the legacyeExchangeDN from the mailbox and added it as an X500 address on the contact so that when the mailbox went away Outlook nick name cached entries would still work (and silently go to the contact versus the now removed mailbox).

    Apparently Exchange 2010 doesn't like having a mailbox with a legacyExchangeDN that is duplicated as an X500 address on a contact, because the error logs on the CASs were complaining of too many legacyExchageDNs, and once I removed it MAPI access (both from Outlook and the New-MailboxExportRequest) started working fine.

    Ironically OWA didn't have an issue while this issue was present.

    I hope this helps as another possible solution, and may be why unlinking and re-linking the mailbox to an AD account worked for some people (because they would get a new randomized legacyExchangeDN).

    • Proposed as answer by THE_WillF Friday, May 20, 2016 3:46 AM
    Wednesday, August 7, 2013 9:58 PM
  • That's the answer.. thanks Woj!
    Saturday, January 4, 2014 11:28 PM
  • I had this same problem and looked at the account under Exchange Managment Console. The LAN Admin had disabled all of the features on the account. It appears the Export requires MAPI in order to complete the Export as soon as I enabled this feature it worked. 

    Jessica Cochran

    This was the answer for me. Although I'm confused as to who in my organization would disable mapi for any mailbox. Thank you.
    Friday, March 21, 2014 11:07 PM
  • Check This Solutions

    http://johnyassa.wordpress.com/2014/06/30/couldnt-connect-to-the-source-mailbox-while-running-new-mailboxexportrequest/


    John Yassa - Senior Platform Engineer - http://johnyassa.wordpress.com/

    • Proposed as answer by John.Yassa Monday, June 30, 2014 8:55 PM
    Monday, June 30, 2014 8:55 PM
  • My case was for disabling MAPI access for the mailbox. After enabling the access New-MailboxExportRequest worked. Till then I was getting the following error;

    Couldn't connect to the source mailbox.
        + CategoryInfo          : NotSpecified: (0:Int32) [New-MailboxExportRequest], RemotePermanentException
        + FullyQualifiedErrorId : 489E274E,Microsoft.Exchange.Management.RecipientTasks.NewMailboxExportRequest

    -Guru.

    Friday, September 19, 2014 7:05 AM
  • Please execute the below command for the affected user mailbox.

    Set-CASMailbox -Identity "user email address " -MAPIBlockOutlookNonCachedMode:$false

    Once run the above command,then try to Export the mailbox.

    It will work.

    Regards
    Murali

    Murali

    Monday, May 25, 2015 8:12 AM
  • Murali's solution fixed it for me.

    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

    Friday, June 26, 2015 10:34 PM
  • I had the same problem when I ran the cmdlet while logged into a CAS, but it worked fine if I ran the exact same cmdlet from my workstation.

    Edit: I had this problem with another mailbox and Sheehan's solution worked this time. I had a mail contact with the old mailbox's exchangelegacydn as an x500 address. After removing that address from the contact, the export worked fine. When the export was done, add the X500 back to the contact.


    Blog / Twitter


    • Edited by reprac Wednesday, February 24, 2016 10:22 PM More info
    Thursday, July 9, 2015 3:05 PM
  • HI

    Please Enable MAPI for the mail box

    • Proposed as answer by rafeeque.k Tuesday, September 15, 2015 9:53 AM
    Tuesday, September 15, 2015 9:53 AM
  • This worked for me thanks!
    Thursday, November 12, 2015 10:33 AM
  • I had this issue in our Exchange environment, and it was because I copied the legacyExchangeDN as an X500 address onto a contact, because we were helping a customer migrate off our email system.

    I.E. Create contacts, set mailboxes to forward to those contacts, and we proactively grabbed the legacyeExchangeDN from the mailbox and added it as an X500 address on the contact so that when the mailbox went away Outlook nick name cached entries would still work (and silently go to the contact versus the now removed mailbox).

    Apparently Exchange 2010 doesn't like having a mailbox with a legacyExchangeDN that is duplicated as an X500 address on a contact, because the error logs on the CASs were complaining of too many legacyExchageDNs, and once I removed it MAPI access (both from Outlook and the New-MailboxExportRequest) started working fine.

    Ironically OWA didn't have an issue while this issue was present.

    I hope this helps as another possible solution, and may be why unlinking and re-linking the mailbox to an AD account worked for some people (because they would get a new randomized legacyExchangeDN).

    This was my issue exactly! I guess I created my own problem, while trying to "help" the end-user! But Yes, removing the X500 and performing the PST export worked for me! Sad I discovered this "answer" AFTER I figured it out for myself. SMH!

    ITIL Foundation; BCSA (Blackberry Certified System Administrator); Network Engineer

    Friday, May 20, 2016 3:49 AM
  • Excellent. Woj suggestion worked for me. 

    MAPI enabled and it worked. 

    Tuesday, October 4, 2016 6:59 AM
  • Amazing. Thanks a lot Dan - Youre a life saver

    Ratish Nair | Microsoft MVP | Publisher at MSExchangeGuru www.MSExchangeGuru.com | Learn Exchange The Guru Way

    Wednesday, June 14, 2017 7:41 AM
  • Worked for me tyvm!
    Wednesday, September 6, 2017 7:22 AM
  • Thank you!!!

    Restarting the Microsoft Exchange RPC Client Access Service worked!

    $mbox=Get-Mailbox username
    New-MailboxExportRequest -Mailbox $mbox -FilePath \\server\path.pst
    
    Couldn't connect to the source mailbox.
    
    

    I was seeing MAPI connection message in the Verbose.

    Thursday, October 19, 2017 1:14 PM
  • This worked for me. Thanks!

    Max

    Monday, November 27, 2017 11:04 PM