Migrate exchange 2016 to Exchange 2019 - BigFunnelTransientException
السؤال
-
have margrated exchange 2010 to exch 2016 and moved all mailboxes and the decommiction exchange 2010.
the exchange 2016 is installed on windows server 2019 - we have now install a windows 2019 with exchange 2019 running 2012R2 AD envorment.
now we trying to migrate exchange 2016 mailboxes into the Exchange 2019 new database the process is very slow.
we have not managed to transfer any mailboxes away.
Data migrated: 6.099 MB (6,395,323 bytes)
Migration rate: 0 B (0 bytes)
Transient error BigFunnelTransientException has occurred. The system will retry
Exchanges server Databases have no recitations or any network card issues. we have tried to rebuild the Index on Exchange 2016 Database as we were also receiving error MigrationMRSPermanentException: Informational: The request has been temporarily postponed because Search is not up to date. however it did not help.
We have also tried to copy the mailboxes to different Exchange 2019 Databases and still does not work,
we tried moving exchange 2019 mailboxes to exchange 2016 database same issue.
we have tried it on Mailboxes with 5meg data as well as much larger mailboxes same issue.
however can export the mailboxes to PST files without any issues.
I would be grateful if you can help.
Thanks,
PJ
PJ Moka
جميع الردود
-
Hi PJ,
Do you mean you get the Exchange 2016 installed on Windows Server 2019?
If yes, that is really not a good choice and you just make your Exchange server deploy in an unsupported OS.
Since exporting to pst is working fine now, you could regard it as a workaround for this issue.
Otherwise we should troubleshoot the issue via the following steps:
1. Check the database and mailbox quota on both sides, ensure that the quota in the Exchange 2019 is larger than that in Exchange 2016.
Get-MailboxDatabase |fl *quota*
Get-Mailbox | fl name,*quota*2. Check the database status on both sides:
Get-MailboxDatabaseCopyStatus <db name>| fl name, status, contentindex*
3. Check the detailed error returned by the migration batch and also verify that migration is not stuck on a specific user.Get-MigrationStatistics Get-MigrationUser | Get-MigrationUserStatistics -Diagnostic | fl Status,Error,DiagnosticInfo
Or you could click "download the report for this user" on the right hand on EAC to generate a Migration users status report.
Please note that for security reasons, we recommend you to remove the sensitive information before finally posting in the thread or you could send the entire result to ibsexc@microsoft.com
Look forwards to your reply.
Regards,
Manu Meng
Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.
Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.
- تم التحرير بواسطة Manu Meng 12/شعبان/1440 08:02 ص
-
the mailbox from 2019 to 2016 transfer fine , however the mailbox was a test account with 1.3meg size, it taken 2 minutes to complete.
the issue with moving mailboxes from exchange 2016 CU12 to Exchange 2019 CU1 both server running win 2019 latest updates.
we are indexing the database so the stats on exchange 2016 DB is Crawling, however please find the details requested.
all Database quota are the same Unlimited.
Migration_Statistics Get-MigrationUser | Get-MigrationUserStatistics -Diagnostic | fl Status,Error,DiagnosticInfo Status : Failed Error : MigrationMRSPermanentException: Informational: The request has been temporarily postponed because Search is not up to date. The Microsoft Exchange Mailbox Replication service will attempt to continue processing the request after 17/04/2019 02:05:32. DiagnosticInfo : <MigrationJobItem name="Administrator@domain.com" guid="a80de636-d4f7-49c5-9d08-c4c8e9fd5443"> <MigrationJobItemStatusData> <status>Failed</status> <previousStatus>Syncing</previousStatus> <state>Failed</state> <stateLastUpdated>17/04/2019 01:03:56</stateLastUpdated> <error>Informational: The request has been temporarily postponed because Search is not up to date. The Microsoft Exchange Mailbox Replication service will attempt to continue processing the request after 17/04/2019 02:05:32.</error> <transientErrorCount>0</transientErrorCount> <SameStatusCount>1</SameStatusCount> <internalError> at Microsoft.Exchange.Migration.MigrationJobItemStatusData.SetFailedStatus(MigrationUserStatus failureStatus, Exception exception, String internalError, Nullable`1 state) at Microsoft.Exchange.M igration.MigrationJobItem.<>c__DisplayClass309_0.<SetStatus>b__0(IMigrationMessageItem message) at Microsoft.Exchange.Migration.MigrationJobItem.UpdatePersistedMessage(IMigrationDataProvider dataProvider, PropertyDefinition[] propertiesToUpdate, Action`1 updateAction, SaveMode saveMode, Boolean refresh) at Microsoft.Exchange.Migration.MigrationJobItem.SetStatus(IMigrationDataProvider provider, Nullable`1 state, Nullable`1 flagsToApply, Nullable`1 flagsToClear, IMigrationJobItemWorkflowPosition position, Nullable`1 actionToClear, Nullable`1 actionToApply, Boolean completedPreviousPosition, Nullable`1 delayTime, IMailboxData mailboxData, IStepSettings stepSettings, IStepSnapshot stepSnapshot, Boolean updated, Exception exception, Boolean clearResultantStateInfo, Nullable`1 processorStartTime, Boolean clearedDueToFailure, Boolean isCalledByCmdlet, Boolean skipClearingErrors) at Microsoft.Exchange.Migration.SnapshotMigrationJobI temProcessorBase.ApplyResponse(MigrationJobItemProcessorResponse response) at Microsoft.Exchange.Migration.MigrationProcessorBase`2.Process() at Microsoft.Exchange.Migration.ActiveMigrationJobProcessor.ProcessChild(MigrationJobItem child) at Microsoft.Exchange.Migration.MigrationHierarchyProcessorBase`4.InternalProcess() at Microsoft.Exchange.Migration.MigrationProcessorBase`2.Process() at Microsoft.Exchange.Migration.MigrationSessionProcessor.ProcessChild(MigrationJob child) at Microsoft.Exchange.Migration.MigrationHierarchyProcessorBase`4.InternalProcess() at Microsoft.Exchange.Migration.MigrationProcessorBase`2.Process() at Microsoft.Exchange.Migration.MigrationScheduler.ProcessCacheEntry(MigrationCacheEntry cacheEntry, Func`1 shouldStop) at Microsoft.Exchange.Migration.MigrationScheduler.Process(IMigrationJobCache cache) at Microsoft.Exchange.Migration.MigrationApplication.Process() at Microsoft.Exchange.Servicelets.SyncMigration.SyncMigrationServicelet.Work() at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state) at System.Threading.ThreadHelper.ThreadStart() | at Microsoft.Exchange.Migration.MrsAccessorBase`11.Retr ieveSubscriptionSnapshotFromRequest(TRequestStatistics request, IMailboxData localMailbox) at Microso ft.Exchange.Migration.MrsMoveRequestAccessor.RetrieveSubscriptionSnapshotFromRequest(MoveRequestStatis tics request, IMailboxData localMailbox) at Microsoft.Exchange.Migration.MrsAccessorBase`11.RetrieveSubscriptionSnapshot(Guid jobItemGuid, ISubscriptionId subscriptionId) at Microsoft.Exchange.Migration.DataMigrationJobItemStepHandler.Monitor(MigrationJobItem jobItem) at Microsoft.Exchange.Migration.ActiveMigrationJobItemProcessor.InternalProcess() at Microsoft.Exchange.Migration.MigrationProcessorBase`2.Process() at Microsoft.Exchange.Migration.ActiveMigrationJobProcessor.ProcessChild(MigrationJobItem child) at Microsoft.Exchange.Migration.MigrationHierarchyProcessorBase`4.InternalProcess() at Microsoft.Exchange.Migration.MigrationProcessorBase`2.Process() at Microsoft.Exchange.Migration.MigrationSessionProcessor.ProcessChild(MigrationJob child) at Microsoft.Exchange.Migration.MigrationHierarchyProcessorBase`4.InternalProcess() at Microsoft.Exchange.Migration.MigrationProcessorBase`2.Process() at Microsoft.Exchange.Migration.MigrationScheduler.ProcessCacheEntry(MigrationCacheEntry cacheEntry, Func`1 shouldStop) at Microsoft.Exchange.Migration.MigrationScheduler.Process(IMigrationJobCache cache) at Microsoft.Exchange.Migration.MigrationApplication.Process() at Microsoft.Exchange.Servicelets.SyncMigration.SyncMigrationServicelet.Work() at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state) at System.Threading.ThreadHelper.ThreadStart() _Microsoft.Exchange.Migration.MigrationMRSPermanentException_Informational: The request has been temporarily postponed because Search is not up to date. The Microsoft Exchange Mailbox Replication service will attempt to continue processing the request after 04/17/2019 02:05:32._|</internalError> <internalErrorTime>17/04/2019 01:03:56</internalErrorTime> <statusHistory>12:91;1:2;1:9,325;</statusHistory> <watsonHash>1c36</watsonHash> <FailureRecord> <FailureRecord> <TimeStamp>2019-04-17T01:03:56.2456972Z</TimeStamp> <DataContext></DataContext> <ExceptionTypes>Exchange</ExceptionTypes> <FailureType>MigrationMRSPermanentException</FailureType> <FailureSide /> <FailureHash>1c36</FailureHash> <FailureCode>-2146233088</FailureCode> <MapiLowLevelError>0</MapiLowLevelError> <WorkItem /> <Message>Informational: The request has been temporarily postponed because Search is not up to date. The Microsoft Exchange Mailbox Replication service will attempt to continue processing the request after 17/04/2019 02:05:32.</Message> <StackTrace> at Microsoft.Exchange.Migration.MrsAccessorBase`11.RetrieveSubscriptionSnapshot FromRequest(TRequestStatistics request, IMailboxData localMailbox) at Microsoft.Exchange.Migration.MrsMoveRequestAccessor.RetrieveSubscriptionSnapshotFromRequest(Move RequestStatistics request, IMailboxData localMailbox) at Microsoft.Exchange.Migration.MrsAccessorBase`11.RetrieveSubscriptionSnapshot(Guid jobItemGuid, ISubscriptionId subscriptionId) at Microsoft.Exchange.Migration.DataMigrationJobItemStepHandler.Monitor(MigrationJobItem jobItem) at Microsoft.Exchange.Migration.ActiveMigrationJobItemProcessor.InternalProcess() at Microsoft.Exchange.Migration.MigrationProcessorBase`2.Process() at Microsoft.Exchange.Migration.ActiveMigrationJobProcessor.ProcessChild(MigrationJobItem child) at Microsoft.Exchange.Migration.MigrationHierarchyProcessorBase`4.InternalProcess() at Microsoft.Exchange.Migration.MigrationProcessorBase`2.Process() at Microsoft.Exchange.Migration.MigrationSessionProcessor.ProcessChild(MigrationJob child) at Microsoft.Exchange.Migration.MigrationHierarchyProcessorBase`4.InternalProcess() at Microsoft.Exchange.Migration.MigrationProcessorBase`2.Process() at Microsoft.Exchange.Migration.MigrationScheduler.ProcessCacheEntry(MigrationCacheEntry cacheEntry, Func`1 shouldStop) at Microsoft.Exchange.Migration.MigrationScheduler.Process(IMigrationJobCache cache) at Microsoft.Exchange.Migration.MigrationApplication.Process() at Microsoft.Exchange.Servicelets.SyncMigration.SyncMigrationServicelet.Work() at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state) at System.Threading.ThreadHelper.ThreadStart() </StackTrace> </FailureRecord> </FailureRecord> </MigrationJobItemStatusData> <flags>None</flags> <nextProcessTime>17/04/2019 01:03:56</nextProcessTime> <WorkflowTriggeredActionData> <Action>None</Action> <ActionTriggeredTime /> </WorkflowTriggeredActionData> <MigrationJobItemWorkflowPosition> <Step>DataMigration</Step> <Stage>Processing</Stage> </MigrationJobItemWorkflowPosition> <workflow>Steps: [(Initialization. Stages: (Processing)), (DataMigration. Stages: (Discovery, Validation, Injection, Processing))]</workflow> <ResultantState /> <TimeTracker Type="MigrationJobItemState" CurrentState="Failed" LastStateChangeTimeStamp="2019-04-17T01:03:56.2416954"> <Timestamps> <Timestamp Type="Created" Time="2019-04-16T22:26:57.7906317Z" /> <Timestamp Type="Started" Time="2019-04-16T22:28:29.1356398Z" /> <Timestamp Type="Failed" Time="2019-04-17T01:03:56.2416954Z" /> <Timestamp Type="LastProcessed" Time="2019-04-17T01:03:56.2416954Z" /> <Timestamp Type="Initialized" Time="2019-04-16T22:28:29.1416426Z" /> <Timestamp Type="SubscriptionCreated" Time="2019-04-16T22:28:30.3402049Z" /> <Timestamp Type="SubscriptionChecked" Time="2019-04-17T01:03:56.2466968Z" /> </Timestamps> </TimeTracker> <version>6</version> <created>16/04/2019 22:26:57</created> <reportGuid>00000000-0000-0000-0000-000000000000</reportGuid> <BatchInputId>19483bdf-ef58-44bf-8124-fbbcfb5c59f7</BatchInputId> <IsStaged>true</IsStaged> <JobName>administrator</JobName> </MigrationJobItem> Status : Completed Error : DiagnosticInfo : <MigrationJobItem name="Test@domain.com" guid="c7c709c4-06d5-45b5-8c54-13fe7aaa505a"> <MigrationJobItemStatusData> <status>Completed</status> <previousStatus>Syncing</previousStatus> <state>Completed</state> <stateLastUpdated>17/04/2019 00:13:13</stateLastUpdated> <error /> <transientErrorCount>0</transientErrorCount> <SameStatusCount>1</SameStatusCount> <internalError /> <internalErrorTime /> <statusHistory>12:92;1:1;1:1,114;</statusHistory> <watsonHash /> <FailureRecord /> </MigrationJobItemStatusData> <flags>None</flags> <nextProcessTime>17/04/2019 00:13:13</nextProcessTime> <WorkflowTriggeredActionData> <Action>None</Action> <ActionTriggeredTime /> </WorkflowTriggeredActionData> <MigrationJobItemWorkflowPosition> <Step>DataMigration</Step> <Stage>Processing</Stage> </MigrationJobItemWorkflowPosition> <workflow>Steps: [(Initialization. Stages: (Processing)), (DataMigration. Stages: (Discovery, Validation, Injection, Processing))]</workflow> <ResultantState /> <TimeTracker Type="MigrationJobItemState" CurrentState="Completed" LastStateChangeTimeStamp="2019-04-17T00:13:13.5128049"> <Timestamps> <Timestamp Type="Created" Time="2019-04-16T23:53:07.3753007Z" /> <Timestamp Type="Started" Time="2019-04-16T23:54:39.0643403Z" /> <Timestamp Type="Completed" Time="2019-04-17T00:13:13.5128049Z" /> <Timestamp Type="LastProcessed" Time="2019-04-17T00:13:13.5128049Z" /> <Timestamp Type="Initialized" Time="2019-04-16T23:54:39.0713376Z" /> <Timestamp Type="DataMigrated" Time="2019-04-17T00:13:13.5128049Z" /> <Timestamp Type="SubscriptionCreated" Time="2019-04-16T23:54:39.4925349Z" /> <Timestamp Type="SubscriptionChecked" Time="2019-04-17T00:13:13.5158027Z" /> </Timestamps> </TimeTracker> <version>6</version> <created>16/04/2019 23:53:07</created> <reportGuid>00000000-0000-0000-0000-000000000000</reportGuid> <BatchInputId>cd402c3a-976b-4de9-9354-3edc71f218ec</BatchInputId> <IsStaged>true</IsStaged> <JobName>test e19</JobName> </MigrationJobItem> Status : Failed Error : MigrationMRSPermanentException: Informational: The request has been temporarily postponed because Search is not up to date. The Microsoft Exchange Mailbox Replication service will attempt to continue processing the request after 16/04/2019 18:59:07. DiagnosticInfo : <MigrationJobItem name="ToDoList@domain.com" guid="5d3f66c9-b762-497e-898c-8bc22280f1af"> <MigrationJobItemStatusData> <status>Failed</status> <previousStatus>Syncing</previousStatus> <state>Failed</state> <stateLastUpdated>16/04/2019 17:52:38</stateLastUpdated> <error>Informational: The request has been temporarily postponed because Search is not up to date. The Microsoft Exchange Mailbox Replication service will attempt to continue processing the request after 16/04/2019 18:59:07.</error> <transientErrorCount>0</transientErrorCount> <SameStatusCount>1</SameStatusCount> <internalError> at Microsoft.Exchange.Migration.MigrationJobItemStatusData.SetFailedStatus(MigrationUserStatus failureStatus, Exception exception, String internalError, Nullable`1 state) at Microsoft.Exchange.M igration.MigrationJobItem.<>c__DisplayClass309_0.<SetStatus>b__0(IMigrationMessageItem message) at Microsoft.Exchange.Migration.MigrationJobItem.UpdatePersistedMessage(IMigrationDataProvider dataProvider, PropertyDefinition[] propertiesToUpdate, Action`1 updateAction, SaveMode saveMode, Boolean refresh) at Microsoft.Exchange.Migration.MigrationJobItem.SetStatus(IMigrationDataProvider provider, Nullable`1 state, Nullable`1 flagsToApply, Nullable`1 flagsToClear, IMigrationJobItemWorkflowPosition position, Nullable`1 actionToClear, Nullable`1 actionToApply, Boolean completedPreviousPosition, Nullable`1 delayTime, IMailboxData mailboxData, IStepSettings stepSettings, IStepSnapshot stepSnapshot, Boolean updated, Exception exception, Boolean clearResultantStateInfo, Nullable`1 processorStartTime, Boolean clearedDueToFailure, Boolean isCalledByCmdlet, Boolean skipClearingErrors) at Microsoft.Exchange.Migration.SnapshotMigrationJobI temProcessorBase.ApplyResponse(MigrationJobItemProcessorResponse response) at Microsoft.Exchange.Migration.MigrationProcessorBase`2.Process() at Microsoft.Exchange.Migration.ActiveMigrationJobProcessor.ProcessChild(MigrationJobItem child) at Microsoft.Exchange.Migration.MigrationHierarchyProcessorBase`4.InternalProcess() at Microsoft.Exchange.Migration.MigrationProcessorBase`2.Process() at Microsoft.Exchange.Migration.MigrationSessionProcessor.ProcessChild(MigrationJob child) at Microsoft.Exchange.Migration.MigrationHierarchyProcessorBase`4.InternalProcess() at Microsoft.Exchange.Migration.MigrationProcessorBase`2.Process() at Microsoft.Exchange.Migration.MigrationScheduler.ProcessCacheEntry(MigrationCacheEntry cacheEntry, Func`1 shouldStop) at Microsoft.Exchange.Migration.MigrationScheduler.Process(IMigrationJobCache cache) at Microsoft.Exchange.Migration.MigrationApplication.Process() at Microsoft.Exchange.Servicelets.SyncMigration.SyncMigrationServicelet.Work() at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state) at System.Threading.ThreadHelper.ThreadStart() | at Microsoft.Exchange.Migration.MrsAccessorBase`11.Retr ieveSubscriptionSnapshotFromRequest(TRequestStatistics request, IMailboxData localMailbox) at Microso ft.Exchange.Migration.MrsMoveRequestAccessor.RetrieveSubscriptionSnapshotFromRequest(MoveRequestStatis tics request, IMailboxData localMailbox) at Microsoft.Exchange.Migration.MrsAccessorBase`11.RetrieveSubscriptionSnapshot(Guid jobItemGuid, ISubscriptionId subscriptionId) at Microsoft.Exchange.Migration.DataMigrationJobItemStepHandler.Monitor(MigrationJobItem jobItem) at Microsoft.Exchange.Migration.ActiveMigrationJobItemProcessor.InternalProcess() at Microsoft.Exchange.Migration.MigrationProcessorBase`2.Process() at Microsoft.Exchange.Migration.ActiveMigrationJobProcessor.ProcessChild(MigrationJobItem child) at Microsoft.Exchange.Migration.MigrationHierarchyProcessorBase`4.InternalProcess() at Microsoft.Exchange.Migration.MigrationProcessorBase`2.Process() at Microsoft.Exchange.Migration.MigrationSessionProcessor.ProcessChild(MigrationJob child) at Microsoft.Exchange.Migration.MigrationHierarchyProcessorBase`4.InternalProcess() at Microsoft.Exchange.Migration.MigrationProcessorBase`2.Process() at Microsoft.Exchange.Migration.MigrationScheduler.ProcessCacheEntry(MigrationCacheEntry cacheEntry, Func`1 shouldStop) at Microsoft.Exchange.Migration.MigrationScheduler.Process(IMigrationJobCache cache) at Microsoft.Exchange.Migration.MigrationApplication.Process() at Microsoft.Exchange.Servicelets.SyncMigration.SyncMigrationServicelet.Work() at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state) at System.Threading.ThreadHelper.ThreadStart() _Microsoft.Exchange.Migration.MigrationMRSPermanentException_Informational: The request has been temporarily postponed because Search is not up to date. The Microsoft Exchange Mailbox Replication service will attempt to continue processing the request after 04/16/2019 18:59:07._|</internalError> <internalErrorTime>16/04/2019 17:52:38</internalErrorTime> <statusHistory>12:93;1:1;1:11,933;</statusHistory> <watsonHash>1c36</watsonHash> <FailureRecord> <FailureRecord> <TimeStamp>2019-04-16T17:52:38.1124935Z</TimeStamp> <DataContext></DataContext> <ExceptionTypes>Exchange</ExceptionTypes> <FailureType>MigrationMRSPermanentException</FailureType> <FailureSide /> <FailureHash>1c36</FailureHash> <FailureCode>-2146233088</FailureCode> <MapiLowLevelError>0</MapiLowLevelError> <WorkItem /> <Message>Informational: The request has been temporarily postponed because Search is not up to date. The Microsoft Exchange Mailbox Replication service will attempt to continue processing the request after 16/04/2019 18:59:07.</Message> <StackTrace> at Microsoft.Exchange.Migration.MrsAccessorBase`11.RetrieveSubscriptionSnapshot FromRequest(TRequestStatistics request, IMailboxData localMailbox) at Microsoft.Exchange.Migration.MrsMoveRequestAccessor.RetrieveSubscriptionSnapshotFromRequest(Move RequestStatistics request, IMailboxData localMailbox) at Microsoft.Exchange.Migration.MrsAccessorBase`11.RetrieveSubscriptionSnapshot(Guid jobItemGuid, ISubscriptionId subscriptionId) at Microsoft.Exchange.Migration.DataMigrationJobItemStepHandler.Monitor(MigrationJobItem jobItem) at Microsoft.Exchange.Migration.ActiveMigrationJobItemProcessor.InternalProcess() at Microsoft.Exchange.Migration.MigrationProcessorBase`2.Process() at Microsoft.Exchange.Migration.ActiveMigrationJobProcessor.ProcessChild(MigrationJobItem child) at Microsoft.Exchange.Migration.MigrationHierarchyProcessorBase`4.InternalProcess() at Microsoft.Exchange.Migration.MigrationProcessorBase`2.Process() at Microsoft.Exchange.Migration.MigrationSessionProcessor.ProcessChild(MigrationJob child) at Microsoft.Exchange.Migration.MigrationHierarchyProcessorBase`4.InternalProcess() at Microsoft.Exchange.Migration.MigrationProcessorBase`2.Process() at Microsoft.Exchange.Migration.MigrationScheduler.ProcessCacheEntry(MigrationCacheEntry cacheEntry, Func`1 shouldStop) at Microsoft.Exchange.Migration.MigrationScheduler.Process(IMigrationJobCache cache) at Microsoft.Exchange.Migration.MigrationApplication.Process() at Microsoft.Exchange.Servicelets.SyncMigration.SyncMigrationServicelet.Work() at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state) at System.Threading.ThreadHelper.ThreadStart() </StackTrace> </FailureRecord> </FailureRecord> </MigrationJobItemStatusData> <flags>None</flags> <nextProcessTime>16/04/2019 17:52:38</nextProcessTime> <WorkflowTriggeredActionData> <Action>None</Action> <ActionTriggeredTime /> </WorkflowTriggeredActionData> <MigrationJobItemWorkflowPosition> <Step>DataMigration</Step> <Stage>Processing</Stage> </MigrationJobItemWorkflowPosition> <workflow>Steps: [(Initialization. Stages: (Processing)), (DataMigration. Stages: (Discovery, Validation, Injection, Processing))]</workflow> <ResultantState /> <TimeTracker Type="MigrationJobItemState" CurrentState="Failed" LastStateChangeTimeStamp="2019-04-16T17:52:38.1034940"> <Timestamps> <Timestamp Type="Created" Time="2019-04-16T14:32:10.9271843Z" /> <Timestamp Type="Started" Time="2019-04-16T14:33:43.8699608Z" /> <Timestamp Type="Failed" Time="2019-04-16T17:52:38.103494Z" /> <Timestamp Type="LastProcessed" Time="2019-04-16T17:52:38.103494Z" /> <Timestamp Type="Initialized" Time="2019-04-16T14:33:43.8759633Z" /> <Timestamp Type="SubscriptionCreated" Time="2019-04-16T14:33:44.2208721Z" /> <Timestamp Type="SubscriptionChecked" Time="2019-04-16T17:52:38.1134944Z" /> </Timestamps> </TimeTracker> <version>6</version> <created>16/04/2019 14:32:10</created> <reportGuid>00000000-0000-0000-0000-000000000000</reportGuid> <BatchInputId>7e60fbb9-9d0b-44af-a2f2-1589e7a0065c</BatchInputId> <IsStaged>true</IsStaged> <JobName>todolist</JobName> </MigrationJobItem> Status : Failed Error : MigrationMRSPermanentException: Informational: The request has been temporarily postponed because Search is not up to date. The Microsoft Exchange Mailbox Replication service will attempt to continue processing the request after 17/04/2019 02:40:20. DiagnosticInfo : <MigrationJobItem name="web.start@domain.com" guid="211a8442-7f32-4b25-ac48-7210db796e7e"> <MigrationJobItemStatusData> <status>Failed</status> <previousStatus>Syncing</previousStatus> <state>Failed</state> <stateLastUpdated>17/04/2019 01:39:05</stateLastUpdated> <error>Informational: The request has been temporarily postponed because Search is not up to date. The Microsoft Exchange Mailbox Replication service will attempt to continue processing the request after 17/04/2019 02:40:20.</error> <transientErrorCount>0</transientErrorCount> <SameStatusCount>1</SameStatusCount> <internalError> at Microsoft.Exchange.Migration.MigrationJobItemStatusData.SetFailedStatus(MigrationUserStatus failureStatus, Exception exception, String internalError, Nullable`1 state) at Microsoft.Exchange.M igration.MigrationJobItem.<>c__DisplayClass309_0.<SetStatus>b__0(IMigrationMessageItem message) at Microsoft.Exchange.Migration.MigrationJobItem.UpdatePersistedMessage(IMigrationDataProvider dataProvider, PropertyDefinition[] propertiesToUpdate, Action`1 updateAction, SaveMode saveMode, Boolean refresh) at Microsoft.Exchange.Migration.MigrationJobItem.SetStatus(IMigrationDataProvider provider, Nullable`1 state, Nullable`1 flagsToApply, Nullable`1 flagsToClear, IMigrationJobItemWorkflowPosition position, Nullable`1 actionToClear, Nullable`1 actionToApply, Boolean completedPreviousPosition, Nullable`1 delayTime, IMailboxData mailboxData, IStepSettings stepSettings, IStepSnapshot stepSnapshot, Boolean updated, Exception exception, Boolean clearResultantStateInfo, Nullable`1 processorStartTime, Boolean clearedDueToFailure, Boolean isCalledByCmdlet, Boolean skipClearingErrors) at Microsoft.Exchange.Migration.SnapshotMigrationJobI temProcessorBase.ApplyResponse(MigrationJobItemProcessorResponse response) at Microsoft.Exchange.Migration.MigrationProcessorBase`2.Process() at Microsoft.Exchange.Migration.ActiveMigrationJobProcessor.ProcessChild(MigrationJobItem child) at Microsoft.Exchange.Migration.MigrationHierarchyProcessorBase`4.InternalProcess() at Microsoft.Exchange.Migration.MigrationProcessorBase`2.Process() at Microsoft.Exchange.Migration.MigrationSessionProcessor.ProcessChild(MigrationJob child) at Microsoft.Exchange.Migration.MigrationHierarchyProcessorBase`4.InternalProcess() at Microsoft.Exchange.Migration.MigrationProcessorBase`2.Process() at Microsoft.Exchange.Migration.MigrationScheduler.ProcessCacheEntry(MigrationCacheEntry cacheEntry, Func`1 shouldStop) at Microsoft.Exchange.Migration.MigrationScheduler.Process(IMigrationJobCache cache) at Microsoft.Exchange.Migration.MigrationApplication.Process() at Microsoft.Exchange.Servicelets.SyncMigration.SyncMigrationServicelet.Work() at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state) at System.Threading.ThreadHelper.ThreadStart() | at Microsoft.Exchange.Migration.MrsAccessorBase`11.Retr ieveSubscriptionSnapshotFromRequest(TRequestStatistics request, IMailboxData localMailbox) at Microso ft.Exchange.Migration.MrsMoveRequestAccessor.RetrieveSubscriptionSnapshotFromRequest(MoveRequestStatis tics request, IMailboxData localMailbox) at Microsoft.Exchange.Migration.MrsAccessorBase`11.RetrieveSubscriptionSnapshot(Guid jobItemGuid, ISubscriptionId subscriptionId) at Microsoft.Exchange.Migration.DataMigrationJobItemStepHandler.Monitor(MigrationJobItem jobItem) at Microsoft.Exchange.Migration.ActiveMigrationJobItemProcessor.InternalProcess() at Microsoft.Exchange.Migration.MigrationProcessorBase`2.Process() at Microsoft.Exchange.Migration.ActiveMigrationJobProcessor.ProcessChild(MigrationJobItem child) at Microsoft.Exchange.Migration.MigrationHierarchyProcessorBase`4.InternalProcess() at Microsoft.Exchange.Migration.MigrationProcessorBase`2.Process() at Microsoft.Exchange.Migration.MigrationSessionProcessor.ProcessChild(MigrationJob child) at Microsoft.Exchange.Migration.MigrationHierarchyProcessorBase`4.InternalProcess() at Microsoft.Exchange.Migration.MigrationProcessorBase`2.Process() at Microsoft.Exchange.Migration.MigrationScheduler.ProcessCacheEntry(MigrationCacheEntry cacheEntry, Func`1 shouldStop) at Microsoft.Exchange.Migration.MigrationScheduler.Process(IMigrationJobCache cache) at Microsoft.Exchange.Migration.MigrationApplication.Process() at Microsoft.Exchange.Servicelets.SyncMigration.SyncMigrationServicelet.Work() at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state) at System.Threading.ThreadHelper.ThreadStart() _Microsoft.Exchange.Migration.MigrationMRSPermanentException_Informational: The request has been temporarily postponed because Search is not up to date. The Microsoft Exchange Mailbox Replication service will attempt to continue processing the request after 04/17/2019 02:40:20._|</internalError> <internalErrorTime>17/04/2019 01:39:05</internalErrorTime> <statusHistory>12:91;1:1;1:3,062;2:6,329;18:31;1:62;1:1,130;2:32,494;18:31;1:63;1:6,203;</statusHi story> <watsonHash>1c36</watsonHash> <FailureRecord> <FailureRecord> <TimeStamp>2019-04-17T01:39:05.6052984Z</TimeStamp> <DataContext></DataContext> <ExceptionTypes>Exchange</ExceptionTypes> <FailureType>MigrationMRSPermanentException</FailureType> <FailureSide /> <FailureHash>1c36</FailureHash> <FailureCode>-2146233088</FailureCode> <MapiLowLevelError>0</MapiLowLevelError> <WorkItem /> <Message>Informational: The request has been temporarily postponed because Search is not up to date. The Microsoft Exchange Mailbox Replication service will attempt to continue processing the request after 17/04/2019 02:40:20.</Message> <StackTrace> at Microsoft.Exchange.Migration.MrsAccessorBase`11.RetrieveSubscriptionSnapshot FromRequest(TRequestStatistics request, IMailboxData localMailbox) at Microsoft.Exchange.Migration.MrsMoveRequestAccessor.RetrieveSubscriptionSnapshotFromRequest(Move RequestStatistics request, IMailboxData localMailbox) at Microsoft.Exchange.Migration.MrsAccessorBase`11.RetrieveSubscriptionSnapshot(Guid jobItemGuid, ISubscriptionId subscriptionId) at Microsoft.Exchange.Migration.DataMigrationJobItemStepHandler.Monitor(MigrationJobItem jobItem) at Microsoft.Exchange.Migration.ActiveMigrationJobItemProcessor.InternalProcess() at Microsoft.Exchange.Migration.MigrationProcessorBase`2.Process() at Microsoft.Exchange.Migration.ActiveMigrationJobProcessor.ProcessChild(MigrationJobItem child) at Microsoft.Exchange.Migration.MigrationHierarchyProcessorBase`4.InternalProcess() at Microsoft.Exchange.Migration.MigrationProcessorBase`2.Process() at Microsoft.Exchange.Migration.MigrationSessionProcessor.ProcessChild(MigrationJob child) at Microsoft.Exchange.Migration.MigrationHierarchyProcessorBase`4.InternalProcess() at Microsoft.Exchange.Migration.MigrationProcessorBase`2.Process() at Microsoft.Exchange.Migration.MigrationScheduler.ProcessCacheEntry(MigrationCacheEntry cacheEntry, Func`1 shouldStop) at Microsoft.Exchange.Migration.MigrationScheduler.Process(IMigrationJobCache cache) at Microsoft.Exchange.Migration.MigrationApplication.Process() at Microsoft.Exchange.Servicelets.SyncMigration.SyncMigrationServicelet.Work() at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state) at System.Threading.ThreadHelper.ThreadStart() </StackTrace> </FailureRecord> </FailureRecord> </MigrationJobItemStatusData> <flags>None</flags> <nextProcessTime>17/04/2019 01:39:05</nextProcessTime> <WorkflowTriggeredActionData> <Action>None</Action> <ActionTriggeredTime /> </WorkflowTriggeredActionData> <MigrationJobItemWorkflowPosition> <Step>DataMigration</Step> <Stage>Processing</Stage> </MigrationJobItemWorkflowPosition> <workflow>Steps: [(Initialization. Stages: (Processing)), (DataMigration. Stages: (Discovery, Validation, Injection, Processing))]</workflow> <ResultantState /> <TimeTracker Type="MigrationJobItemState" CurrentState="Failed" LastStateChangeTimeStamp="2019-04-17T01:39:05.6012974"> <Timestamps> <Timestamp Type="Created" Time="2019-04-16T11:54:07.5966646Z" /> <Timestamp Type="Started" Time="2019-04-16T11:55:38.1339842Z" /> <Timestamp Type="Failed" Time="2019-04-17T01:39:05.6012974Z" /> <Timestamp Type="LastProcessed" Time="2019-04-17T01:39:05.6012974Z" /> <Timestamp Type="Initialized" Time="2019-04-16T11:55:38.1399864Z" /> <Timestamp Type="SubscriptionCreated" Time="2019-04-16T11:55:38.9356962Z" /> <Timestamp Type="SubscriptionChecked" Time="2019-04-17T01:39:05.6062977Z" /> <Timestamp Type="SyncNow" Time="2019-04-16T23:54:39.0023418Z" /> </Timestamps> </TimeTracker> <version>6</version> <created>16/04/2019 11:54:07</created> <reportGuid>00000000-0000-0000-0000-000000000000</reportGuid> <BatchInputId>5a0ff5a8-f35f-4217-9b19-70c6971878ba</BatchInputId> <IsStaged>true</IsStaged> <JobName>web</JobName> </MigrationJobItem>
PJ Moka
-
Hi,
After researching your migration user status report downloaded in EAC, I noticed that migration get failed just for one user mailbox, could you please create a new migration batch and then migrate another user to Exchange 2019?
Besides, I also noticed that you have one mailbox to crawl, please wait for sometime until the value of the ContentIndexMailboxesToCrawl drops to 0. Then migrate a new test user to Exchange 2019 as mentioned above.
Regards,
Manu Meng
Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.
Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.
-
Hi Manu,
I will, meanwhile is there any other options for me to copy the database manually to the new server and link the database with the existing mailboxes?
Thanks,
PJ
PJ Moka
@PJ, I have read your last two emails sent on Sunday, please check on the following steps:
You cannot directly move the database, create a new database and then try moving a few mailboxes.
If it doesn't help, try run New-MailboxRepairRequest before moving the mailbox.
New-MailboxRepairRequest -Mailbox "<mailbox_name>" -CorruptionType ProvisionedFolder,SearchFolder,AggregateCounts,Folderview
Then move the mailbox to the Exchange 2019 server with the parameter BadItemLimit:
New-MoveRequest -Identity "<mailbox_name>" -TargetDatabase "DB_name" -BadItemLimit 10
Regards,
Manu Meng
Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.
Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.
- تم الاقتراح كإجابة بواسطة Manu Meng 18/شعبان/1440 08:44 ص
-
have margrated exchange 2010 to exch 2016 and moved all mailboxes and the decommiction exchange 2010.
the exchange 2016 is installed on windows server 2019 - we have now install a windows 2019 with exchange 2019 running 2012R2 AD envorment.
now we trying to migrate exchange 2016 mailboxes into the Exchange 2019 new database the process is very slow.
we have not managed to transfer any mailboxes away.
Data migrated: 6.099 MB (6,395,323 bytes)
Migration rate: 0 B (0 bytes)
Transient error BigFunnelTransientException has occurred. The system will retry
Exchanges server Databases have no recitations or any network card issues. we have tried to rebuild the Index on Exchange 2016 Database as we were also receiving error MigrationMRSPermanentException: Informational: The request has been temporarily postponed because Search is not up to date. however it did not help.
We have also tried to copy the mailboxes to different Exchange 2019 Databases and still does not work,
we tried moving exchange 2019 mailboxes to exchange 2016 database same issue.
we have tried it on Mailboxes with 5meg data as well as much larger mailboxes same issue.
however can export the mailboxes to PST files without any issues.
I would be grateful if you can help.
Thanks,
PJ
PJ Moka
Make sure the values for MaxReceiveSize and MaxSendSize in the get-transportconfig command are not set to unlimited. that was causing MAJOR ISSUES in my migration. Simply change them to fixed values, reboot your servers and try again.
I know this may seem like it has absolutely no link to your issue, but I have had countless TranscientExceptions in my tests.
-
Just checking in to see if above information was helpful. Please let us know if you would like further assistance.
Regards,
Manu Meng
Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.
Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.
- تم الاقتراح كإجابة بواسطة Manu Meng 25/شعبان/1440 07:57 ص
-
Hi Manu,
Made the changes still not working, same error.
We have also changed the limit on all of the mailboxes and still not working.
We have installed anther new Windows Server 2016 with Exchange 2016 latest updates and moved the few of the mailboxes from the Windows 2019 server with Exchane 2016 and still unable to move the mailboxes from the new Exchange 2016 to Exchange 2019.
We can move new Mailboxes which has been created on Exchange 2019 to both Exchange 2016 servers, however not from Exchange 2016 servers to Exchange 2019.
am sure there must be a fault within the Exchange 2019
Please advise.
PJ Moka
-
Hi Manu,
Made the changes still not working, same error.
We have also changed the limit on all of the mailboxes and still not working.
We have installed anther new Windows Server 2016 with Exchange 2016 latest updates and moved the few of the mailboxes from the Windows 2019 server with Exchane 2016 and still unable to move the mailboxes from the new Exchange 2016 to Exchange 2019.
We can move new Mailboxes which has been created on Exchange 2019 to both Exchange 2016 servers, however not from Exchange 2016 servers to Exchange 2019.
am sure there must be a fault within the Exchange 2019
Please advise.
PJ Moka
How about setting the MaxReceiveSize and MaxSendSize to be unlimited? You have changed it from the default value of 10MB to 55MB, maybe it is not enough.
Regards,
Manu Meng
Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.
Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.
- تم التحرير بواسطة Manu Meng 27/شعبان/1440 08:45 ص
