Public Folder Migration - Exchange 2013 > Office 365 - Stuck at 95% - MailEnabling Public Error

Question

Public Folder Migration - Exchange 2013 > Office 365 - Stuck at 95% - MailEnabling Public Error

AM_ADM 21

Hello

I am trying to migrate our public folder to Office365 following this guide:

[https://learn.microsoft.com/en-us/exchange/collaboration/public-folders/migrate-to-exchange-online?view=exchserver-2019

Everything runs through fine, there are no errors found in an validation scripts etc. But after creating the migration batch, it fails with:

Error: FailedToMailEnablePublicFoldersException: There are 2 Public Folders that could not be mail-enabled. Please, check the migration report starting at 1/13/2023 2:37:13 PM for additional details. This may indicate that mail public folder objects in Exchange Online are out of sync with your Exchange deployment. You may need to rerun the script Sync-MailPublicFolders.ps1 on your source Exchange server to update mail-enabled public folder objects in Exchange Online Active Directory.

The migration batch is still at 95% in powershell.

Following this guide:

[https://learn.microsoft.com/en-us/exchange/troubleshoot/public-folders/public-folder-migration-fails

Returns no results.

Re-running the sync-mailenabledmodernpublic folders script finds 0 mail enabled public folders.

I've deleted the batch, new PF mailbox created in Exchange 365, and started the whole process again from the beginning but it fails at the same stage with the same error.

I have no idea what 2 folders it's trying to mail-enable as none of them are mail enabled.

Can anyone help?

Thank you

Yuki Sun-MSFT 41,341 Reputation points

2023-01-16T05:56:35.3566667+00:00

Hi @AM_ADM ,

Following this guide: [https://learn.microsoft.com/en-us/exchange/troubleshoot/public-folders/public-folder-migration-fails Returns no results.

By this, do you mean you've already tried following the steps offered in both methods in the article above but no luck?

If this is the case, could you have a look at the MESO container in AD and see if there are still any orphaned public folders listed there?
AM_ADM 21 Reputation points

2023-01-16T08:37:00.88+00:00

Hello.

Yes, following the steps in the guide returned nothing that needed 'fixing'.

The MESO container in AD just has 3 system mailboxes and quite a few 'health' mailboxes. No reference to any public folder mailbox.
Yuki Sun-MSFT 41,341 Reputation points

2023-01-19T01:48:41.0333333+00:00
Noticed that the guide was mainly intended for Exchange 2010, could you manually run the following command and see if there would be any output?

$pf=Get-PublicFolder \NON_IPM_Subtree -recurse -ResultSize Unlimited | ? { $_.MailEnabled }; ForEach ($i in $pf) {$mesoObj = Get-MailPublicFolder $i.identity; if ($mesoObj -eq $null) {$i }}
Yuki Sun-MSFT 41,341 Reputation points

2023-01-23T08:33:55.56+00:00

Hi @AM_ADM ,

Just checking to see if there are any updates. Should you need more help on this, you can feel free to post back.
AM_ADM 21 Reputation points

2023-03-09T15:43:48.07+00:00

Hello. Apologies, I was on holiday for quite a few weeks after my last comment. I followed your command on 19th January in the Exchange Management Shell, but is also returned no results.

I have a case open with Microsoft for this issue too as I am now very conscious that Exchange 2013 EOL is next month.

Deleted the entire migration batch and tried to do things again but I get exactly the same error as previous. I'm not finding any objects anywhere where mail enable public folder is set to true, but something must think it is set somewhere.

1 answer

Your answer

Yuki Sun-MSFT 41,341 Reputation points

2023-01-16T05:56:35.3566667+00:00

Hi @AM_ADM ,

Following this guide: [https://learn.microsoft.com/en-us/exchange/troubleshoot/public-folders/public-folder-migration-fails Returns no results.

By this, do you mean you've already tried following the steps offered in both methods in the article above but no luck?

If this is the case, could you have a look at the MESO container in AD and see if there are still any orphaned public folders listed there?
AM_ADM 21 Reputation points

2023-01-16T08:37:00.88+00:00

Hello.

Yes, following the steps in the guide returned nothing that needed 'fixing'.

The MESO container in AD just has 3 system mailboxes and quite a few 'health' mailboxes. No reference to any public folder mailbox.
Yuki Sun-MSFT 41,341 Reputation points

2023-01-19T01:48:41.0333333+00:00

Noticed that the guide was mainly intended for Exchange 2010, could you manually run the following command and see if there would be any output?

$pf=Get-PublicFolder \NON_IPM_Subtree -recurse -ResultSize Unlimited | ? { $_.MailEnabled }; ForEach ($i in $pf) {$mesoObj = Get-MailPublicFolder $i.identity; if ($mesoObj -eq $null) {$i }}
Yuki Sun-MSFT 41,341 Reputation points

2023-01-23T08:33:55.56+00:00

Hi @AM_ADM ,

Just checking to see if there are any updates. Should you need more help on this, you can feel free to post back.
AM_ADM 21 Reputation points

2023-03-09T15:43:48.07+00:00

Hello. Apologies, I was on holiday for quite a few weeks after my last comment. I followed your command on 19th January in the Exchange Management Shell, but is also returned no results.

I have a case open with Microsoft for this issue too as I am now very conscious that Exchange 2013 EOL is next month.

Deleted the entire migration batch and tried to do things again but I get exactly the same error as previous. I'm not finding any objects anywhere where mail enable public folder is set to true, but something must think it is set somewhere.

Answer 1

Amit Singh 5,231

Similar thread, " Mailbox Move failed Microsoft.Exchange.MailboxReplicationService.ProxyService did not receive a reply within the configured timeout (00:00:50) ", the issue could be caused because the DataImportTimeout value is set too low, so you could try to increase the value in the file "MsExchangeMailboxReplication.exe.config" in the path "C:\Program Files\Microsoft\Exchange Server\V15\Bin", then perform the migration again to check the result.

AM_ADM 21 Reputation points

2023-01-16T14:44:38.2266667+00:00

Hello

Don't think this is the same issue I'm having but tried it anyway. It didn't make any difference sadly when I tried to re-sync again.
Ricardo Costa da Silva 0 Reputation points

2025-04-30T09:40:17.49+00:00
hi, have you ever came across a solution for your issue? We are actually experiencing the same behavior. We are working on this for some time now, but we are not able to get it sort. From the prerequisites we believe we pass everything, when it comes to the migration process all PF Mailboxes pass the sync except the primary one. It keeps failing with the error below.

thanks,

Ricardo

Error: There are 100 Public Folders that could not be mail-enabled. Please, check the migration report starting at for additional details. This may indicate that mail public folder objects in Exchange Online are out of sync with your Exchange deployment. You may need to rerun the script Sync-MailPublicFolders.ps1 on your source Exchange server to update mail-enabled public folder objects in Exchange Online Active Directory.

Share via

Public Folder Migration - Exchange 2013 > Office 365 - Stuck at 95% - MailEnabling Public Error

1 answer

Your answer