Forum Discussion
Public Folder Migration Failed
We have a problem migrating public folders from an Exchange 2019 OnPremise to an Exchange Online. We followed the Microsoft guide:
Batch migrate Exchange Server public folders to Microsoft 365 or Office 365 | Microsoft Learn
We get to step 7. When completing the PublicFolderMigration job, the status changes to “Completing” and then to “Failed”. The error message in the EXO Shell is:
Status: Failed
Message: Error calling “net.tcp://be1p281mb2001.deup281.prod.outlook.com:9821/Microsoft.Exchange.MailboxReplicationService BE1P281MB2001.DEUP281.PROD.OUTLOOK.COM (15.20.8207.17 ServerCaps:FFFFFFFF, ProxyCaps:1FFFFFFFFFFFFFFFC7DD2DFDBF5FFFFFCB07EFFF, MailboxCaps:, legacyCaps:FFFFFFFF)”. Error details: The communication object System.ServiceModel.Channels.ServiceChannel cannot be used for communication because it is in a Faulted state. --> The communication object System.ServiceModel.Channels.ServiceChannel cannot be used for communication because it is in a Faulted state.
Does anyone have an idea what this error means? We have already removed and restarted the entire migration, but the same error occurs again.
- SKNAFLOCopper Contributor
This is the StackTrace Message from the Migration Batch:
Microsoft.Exchange.ServiceHost.Core
StackTrace : at Microsoft.Exchange.Net.WcfClientBase`1.CallService(Action serviceCall, String context)
at Microsoft.Exchange.Connections.Common.WcfClientWithFaultHandling`2.CallService(Action
serviceCall, String context)
at Microsoft.Exchange.MailboxReplicationService.WcfClientWithVersion`2.CallService(Action
serviceCall, String context)
at Microsoft.Exchange.MailboxReplicationService.MailboxReplicationServiceClient.ArePublicFolders
ReadyForMigrationCompletion(String serverFqdn, PSCredential credential)
at Microsoft.Exchange.Migration.SyncAndCompleteJobActionHandler.<>c__DisplayClass14_0.<LockdownS
ourceForPublicFolderMailboxesMigration>b__0()
at Microsoft.Exchange.Migration.MigrationUtil.RetryOnTransientException(Action operation, Int32
maxRetryAttempts)
at Microsoft.Exchange.Migration.SyncAndCompleteJobActionHandler.LockdownSourceForPublicFolderMai
lboxesMigration(IMailboxReplicationServiceClient mrsClient, Fqdn remoteServer, PSCredential
credential)
at Microsoft.Exchange.Migration.SyncAndCompleteJobActionHandler.LockdownSourceForPublicFolderMai
lboxesMigration(PublicFolderEndpoint endpoint)
at Microsoft.Exchange.Migration.SyncAndCompleteJobActionHandler.Process(Func`1 shouldStop)
at Microsoft.Exchange.Migration.ActiveMigrationJobProcessor.ProcessObject()
at Microsoft.Exchange.Migration.MigrationHierarchyProcessorBase`4.InternalProcess(MigrationObjec
tProcessingReason reason)
at
Microsoft.Exchange.Migration.MigrationProcessorBase`2.Process(MigrationObjectProcessingReason
reason)
- Dan_SnapeSteel Contributor
Probably best to log a ticket with Microsoft through the M365 portal. I've not seen that particular error previously