Troubleshooting Mailbox Moves
Applies to: Exchange Server 2010
Troubleshooting content will be made available as issues arise. If there’s a troubleshooting issue you’d like us to document, click Click to Rate and Give Feedback at the top of this topic and send us feedback. Include as much detail as you can, including any relevant error codes, error descriptions, or event IDs.
Legend
FC |
Failure code |
ID |
Event ID source and number |
General steps for troubleshooting mailbox moves
- If the move request didn't complete, view the Move Request Statistics. For more information, see the section "Use the Shell to view the status of an in-progress move request" in View Move Request Properties.
- If the move request completed with errors, view the move report. For more information, see the section "Use the Shell to view a completed move request report" in View Move Request Properties.
- View the Event log on the Client Access server running the instance of the Microsoft Exchange Mailbox Replication service that's processing the failed move request.
- Step 4 - If you still can't determine the problem, use the Exchange Management Console or the Exchange Management Shell to increase the diagnostic logging levels on the Client Access server for the Mailbox Move and Service categories of the MSExchange Mailbox Replication service. Then resume the failed move request. For details about how to modify the diagnostic logging level, see Manage Diagnostic Logging Levels.
Problems with cross forest\remote move requests
If you're experiencing errors when moving mailboxes across forests, it's possible that the target forest hasn't been properly prepared. For details, see Prepare Mailboxes for Cross-Forest Move Requests.
Corrupted item limit reached (FC: -2147467259 | ID: MSExchange Mailbox Replication 1100)
Problem
The move request fails because the mailbox has more corrupted items than the move request is configured to skip.
Diagnosis
The move request fails, and the Get-MoveRequestStatistics cmdlet returns the following error:
| Failure code | Message |
|---|---|
-2147467259 |
Error: This mailbox exceeded the maximum number of corrupted items that were specified for this move request. |
The following Event log entry appears on the Client Access server on which the move request was initiated:
Log Name |
Application |
Source |
MSExchange Mailbox Replication |
Date |
10/26/2009 2:47:17 PM |
Event ID |
1100 |
Task Category |
Mailbox Move |
Level |
Error |
Keywords |
Classic |
User |
N/A |
Computer |
CAS01.fabrikam.com |
Description |
Mailbox move for 'fabrikam.com/Users/TonySmith' (de278a9f-33eb-49f9-950a-070db3323715) has failed. Error code: -2147467259 This mailbox exceeded the maximum number of corrupted items that were specified for this move request. |
Resolution
- Use the Set-MoveRequest cmdlet to increase the BadItemLimit threshold. For details, see Configure Move Request Properties.
- Resume the failed move request. For details, see Complete a Move Request.
Rules in source mailbox's Inbox folder are larger than 32 KB
Problem
The move request fails when you attempt to move a mailbox from Exchange 2010 to Exchange 2003 because the size of the rules in the Exchange 2010 mailbox exceeds the size of the rules that's allowed in Exchange 2003 (32 KB).
Diagnosis
When you attempt to move the mailbox, you receive an error similar to the following:
Mailbox 'fabrikam.com/Users/tonysmith' could not be moved because rules in source mailbox's inbox folder are larger than 32KB. Please use parameter -IgnoreRuleLimitErrors to skip copying rules.
+ CategoryInfo : InvalidArgument: (mbx2:MailboxOrMailUserIdParameter) [New-MoveRequest], RecipientTaskExc eption + FullyQualifiedErrorId : BB833F3D,Microsoft.Exchange.Management.RecipientTasks.NewMoveRequest
Resolution
- Run the Set-MoveRequest cmdlet with the IgnoreRuleLimitErrors parameter. For details, see Configure Move Request Properties.
- Resume the move request. For details, see Complete a Move Request.
Note
End users will need to re-create their rules.
The mailbox dumpster size exceeds the target quota
Problem
The recoverable items quota for the mailbox being moved has exceeded the target quota. This error occurs when you're moving mailboxes from Exchange 2003 or Exchange 2007 to Exchange 2010.
Diagnosis
When you try to move the mailbox, you receive an error similar to the following:
Mailbox dumpster size 713 MB (747,659,085 bytes) exceeds target quota 500 MB (524,288,000 bytes).
+ CategoryInfo : InvalidArgument: (xxxxx/xxxx/xxxx/xxxx:MailboxOrMailUserIdParameter) [New-MoveRequest], RecipientTaskException + FullyQualifiedErrorId : 93F29192,Microsoft.Exchange.Management.RecipientTasks.NewMoveRequest
Resolution
Move requests don't support moving an Exchange 2003 or Exchange 2007 dumpster to Exchange 2010. However, the move request will still compare the dumpster size between the two product versions. To fix this issue, perform the following steps.
- Increase the recoverable items quota for the target mailbox database by using the Set-MailboxDatabase cmdlet with the RecoverableItemsQuota parameter. For details, see Configure Single Item Recovery.
- Resume the failed move request. For details, see Complete a Move Request.
- When the move request is complete, return the recoverable items quota ** to its original size.
MapiExceptionMdbOffline error (FC: -2147467259 | ID: MSExchange Mailbox Replication 1100)
Problem
While the move was in progress, the source or target mailbox database went offline. By default, the Microsoft Exchange Mailbox Replication service (MRS) will attempt to reconnect with the offline database for 30 minutes. If the database doesn't come online within that time, the move will fail. For more information about how to change the MRS connection rate, see Understanding Move Requests.
Diagnosis
The move request fails, and when you run the Get-MoveRequestStatistics cmdlet, you receive the following error:
| Failure code | Message |
|---|---|
-2147467259 |
Error: MapiExceptionMdbOffline: Unable to open entry ID. (hr=0x80004005, ec=1142) |
Also, the Client Access server that was processing the move request will log an event similar to the following:
Log Name |
Application |
Source |
MSExchange Mailbox Replication |
Date |
10/27/2009 10:30:02 AM |
Event ID |
1100 |
Task Category |
Mailbox Move |
Level |
Error |
Keywords |
Classic |
User |
N/A |
Computer |
CAS01.fabrikam.com |
Description |
Mailbox move for 'fabrikam.com/Users/TonySmith' (8dfd4b3b-8147-4e1b-b86f-5d00799abbf3) has failed. Error code: -2147467259 MapiExceptionMdbOffline: Unable to open entry ID. (hr=0x80004005, ec=1142) Diagnostic context: |
Resolution
- Mount the mailbox database. For details, see Mount a Database.
- Resume the move request. For details, see Complete a Move Request.
No available healthy database copies (FC: -2147220223 | ID: MSExchange Mailbox Replication 1100)
When the target database is a replicated database in a database availability group (DAG), MRS regularly checks the replication health of the target database. High availability infrastructure verifies the current replication health against the configured throttling behavior for high availability mailbox moves (as specified by the DataMoveReplicationConstraint parameter) for the target database. Depending on the results, MRS will either continue with the move or wait. If the target database isn't healthy for 30 minutes, MRS will fail. For details about how to change the MRS connection rate, see Understanding Move Requests.
Diagnosis
The move request fails when you run the Get-MoveRequestStatistics cmdlet, and the output file returns an error similar to the following:
| Failure Code | Message |
|---|---|
-2147220223 |
Error: Move for mailbox '/o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=MBX1' is stalled because DataMoveReplicationConstraint is not satisfied for the database 'mdb1' (agent MailboxDatabaseReplication). Failure Reason: Database 1541069d-2976-4f40-afb1-569ed323de0b does not satisfy constraint SecondCopy. There are no available healthy database copies. |
Also, the Client Access server that was processing the move request will log an event similar to the following:
Log Name |
Application |
Source |
MSExchange Mailbox Replication |
Date |
10/27/2009 10:30:02 AM |
Event ID |
1100 |
Task Category |
Mailbox Move |
Level |
Error |
Keywords |
Classic |
User |
N/A |
Computer |
MBX01.fabrikam.com |
Description |
Mailbox move for 'MBX01.fabrikam.com/Users/MBX1' (214dbbab-bb93-4954-a593-515dcc200e7c) has failed. Error code: -2147220223 Move for mailbox '/o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=MBX1' is stalled because DataMoveReplicationConstraint is not satisfied for the database 'mdb1' (agent MailboxDatabaseReplication). Failure Reason: Database 1541069d-2976-4f40-afb1-569ed323de0b does not satisfy constraint SecondCopy. There are no available healthy database copies. |
Resolution
To resolve this issue, try the following options:
- Remove the move request and then move the mailbox to a healthy target database. For details, see Remove or Clear Move Requests
- Resolve the issue with the target database's replication and resume the move request. For more information, see Understanding High Availability and Site Resilience.
- Update the DataMoveReplicationConstraint parameter on the Set-MailboxDatabase cmdlet for the target database to reflect its current state (if the constraint that's specified is the wrong constraint). For details, see Configure Mailbox Database Properties.
Certificates are too large or too many
Problem
The user has too many certificates on the mailbox account or the certificates are too large. The maximum number of certificates should be under 1 MB.
Diagnosis
When you attempt to create a move request, you receive an error similar to the following:
The call to 'net.tcp:// cas01.fabrikam.com/Microsoft.Exchange.MailboxReplicationService' failed.
Error details: The maximum message size quota for incoming messages (262144) has been exceeded. To increase the quota, use the MaxReceivedMessageSize property on the appropriate binding element. --> The maximum message size quota for incoming messages (262144) has been exceeded. To increase the quota, use the MaxReceivedMessageSize property on the appropriate binding element..
+ CategoryInfo : NotSpecified: (0:Int32) [New-MoveRequest], MailboxReplicationTransientException + FullyQualifiedErrorId : 500EA9BF,Microsoft.Exchange.Management.RecipientTasks.NewMoveRequest
Resolution
- Start Active Directory Users and Computers.
- On the View menu, click Advanced Features.
- In the console tree, expand the domain you want, and then click Users
- In the details pane, right-click the user, and then click Properties.
- In <User Name> Properties, on the Published Certificates tab, select the certificate that you want to delete, and then click Remove. Repeat this process until you have removed enough certificates
- Resume the move request. For details, see Complete a Move Request.
There aren't any available servers running the Mailbox Replication Service.
Problem
The Microsoft Exchange Mailbox Replication (MSExchangeMailboxReplication) service must be running on at least one Client Access server in the local Active Directory site.
Diagnosis
When you try to create a move request, you receive the following error:
There are no available servers that are running the Mailbox Replication Service.
+ CategoryInfo : NotSpecified: (0:Int32) [New-MoveRequest], MailboxReplicationTransientException + FullyQualifiedErrorId : 5C08CF31,Microsoft.Exchange.Management.RecipientTasks.NewMoveRequest
Resolution
Start the Microsoft Exchange Mailbox Replication Service on at least on Client Access server. For details about how to start the service, see Start, stop, pause, resume, or restart a service.
The Microsoft Exchange Mailbox Replication Service fails to start (ID: MSExchange Mailbox Replication 1010)
Problem
The Microsoft Exchange Mailbox Replication (MSExchangeMailboxReplication) service fails to start.
Diagnosis
The event log on the Client Access server that was processing the request logs the following event:
Provider [Name] |
MSExchange Mailbox Replication |
Event ID |
1010 |
[Qualifiers] |
49156 |
Level |
4 |
Task |
1 |
Keywords |
0x80000000000000 |
TimeCreated [SystemTime] |
2009-07-22T20:53:26.000Z |
Channel |
Application |
Computer |
CAS01.fabrikam.com |
EventData |
System.ServiceModel.CommunicationException: The TransportManager failed to listen on the supplied URI using the NetTcpPortSharing service: failed to start the service because it is disabled. An administrator can enable it by running 'sc.exe config NetTcpPortSharing start= demand'.. ---> System.InvalidOperationException: Cannot start service NetTcpPortSharing on computer '.'. ---> System.ComponentModel.Win32Exception: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it --- End of inner exception stack trace --- at System.ServiceProcess.ServiceController.Start(String[] args) at System.ServiceModel.Channels.SharedConnectionListener.SharedListenerProxy.HandleServiceStart(Boolean isReconnecting) --- End of inner exception stack trace --- at System.ServiceModel.Channels.SharedConnectionListener.SharedListenerProxy.HandleServiceStart(Boolean isReconnecting) at System.ServiceModel.Channels.SharedConnectionListener.SharedListenerProxy.Open(Boolean isReconnecting) at System.ServiceModel.Channels.SharedConnectionListener.StartListen(Boolean isReconnecting) at System.ServiceModel.Channels.SharedTcpTransportManager.OnOpenInternal(Int32 queueId, Guid token) at System.ServiceModel.Channels.SharedTcpTransportManager.OnOpen() at System.ServiceModel.Channels.TransportManager.Open(TransportChannelListener channelListener) at System.ServiceModel.Channels.TransportManagerContainer.Open(SelectTransportManagersCallback selectTransportManagerCallback) at System.ServiceModel.Channels.ConnectionOrientedTransportChannelListener.OnOpen(TimeSpan timeout) at System.ServiceModel.Channels.TcpChannelListener`2.OnOpen(TimeSpan timeout) at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout) at System.ServiceModel.Dispatcher.ChannelDispatcher.OnOpen(TimeSpan timeout) at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout) at System.ServiceModel.ServiceHostBase.OnOpen(TimeSpan timeout) at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout) at Microsoft.Exchange.MailboxReplicationService.MailboxReplicationServiceImpl.OnStartInternal(String[] args) in c:\E14\sources\sources\dev\mrs\src\ServiceHost\ServiceImpl.cs:line 227 |
Resolution
At the command prompt, Type the following:
C:\>sc.exe config NetTcpPortSharing start= auto
Note
In the above command, there's a space before auto.
- Start the Microsoft Exchange Mailbox Replication service on at least on Client Access server. For details about how to start the service, see Start, stop, pause, resume, or restart a service.
- Resume the failed move request. For details, see Complete a Move Request.
MRSProxy isn't running in the source forest
Problem
When performing remote move requests, the Mailbox Replication Proxy (MRSProxy) service must be running on all Client Access servers in the source forest. By default, MRSProxy is disabled.
Diagnosis
When you attempt to create a move request, you receive an error similar to the following :
Service 'net.tcp://bl20102ca002.contoso.com/Microsoft.Exchange.MailboxReplicationService' encountered an exception. Error: Service 'https://mail.fabrikam.com/EWS/mrsproxy.svc' encountered an exception. Error: The Mailbox Replication Proxy service is disabled.
+ CategoryInfo : NotSpecified: (0:Int32) [New-MoveRequest], MailboxReplicationPermanentException + FullyQualifiedErrorId : 6289E628,Microsoft.Exchange.Management.RecipientTasks.NewMoveRequest
Resolution
- Start the MRSProxy service on all Client Access servers in the source forest. For details, see Start the MRSProxy Service on a Remote Client Access Server.
- Resume the failed move request. For details, see Complete a Move Request.
Move request can't be cleared after the it's completed
Problem
The move request completes, but has the status of Completed With Warning. You are unable to clear the move request because the Microsoft Exchange Mailbox Replication (MSExchangeMailboxReplication) service couldn't reset the InTransit flag from the destination mailbox. If this flag isn't removed, end users won't be able to log on to their mailboxes.
Diagnosis
When you run the Get-MoveRequestStatistics with the IncludeMoveHistory parameter, the move report returns an error similar to the following:
Failed to reset the destination mailbox after the move.
When you run Test-MAPIConnectivity for this mailbox, it will fail with the following error:
Error : [Microsoft.Exchange.Data.Storage.MailboxInTransitException]: Cannot open mailbox /o=microsoft/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=MBX01/cn=Microsoft System Attendant. Inner error [Microsoft.Mapi.MapiExceptionMailboxInTransit]: MapiExceptionMailboxInTransit: Unable to open message store. (hr=0x80004005, ec=1292)
Resolution
- Start a new move request for the mailbox. For details, see Create a Local Move Request or Create a Remote Move Request that has Exchange 2010 in Both Forests.
- Remove the move request as soon as it reaches the status of In Progress. For details, see Remove or Clear Move Requests.