I Have to Login to Microsoft Exchange Again Mojave

During my solar day to solar day piece of work every bit a part of back up arrangement, I work with and help troubleshoot mailbox migrations very often. 1 type of migrations that nosotros see quite often is IMAP migrations. I wanted to put together an overview of IMAP migration good practices as well every bit troubleshooting tips related to IMAP migrations. Hopefully, you lot discover this useful! I realize that the second part of the post is a flake dry and might not be relevant unless you actively demand to troubleshoot. A few things to go out of the way beginning:

• Nosotros back up migrations from IMAP servers to Office 365 Exchange Online using IMAP4 protocol.
• We don't back up IMAP migrations between two Office 365 tenants. Our documentation for this scenario tin can be found here.
• We also don't support offboarding dorsum to an IMAP server from Substitution Online using IMAP. Offboarding is only possible using Mailbox Replication Service (MRS) migrations using an MRSProxy endpoint.
• We don't recommend IMAP migrations from Commutation on-premises servers. In such scenarios, we recommend using a native migration method (Cutover or Minimal / Express Hybrid). We too don't recommend Staged migration from Commutation 2007 or Commutation 2003 servers if you intend to keep directory synchronization in place after mailbox migration to Office 365. The recommended migration method when migrating from these old Commutation Servers when Directory Synchronization is required for your organization is Minimal Hybrid Configuration; this requires inserting an Exchange 2010 (for Substitution 2003 servers) or Exchange 2013 (for Exchange 2007 servers) and running Minimal HCW. This will requite you a gratuitous Hybrid license and will let you lot to perform an MRS migration (this means there is no need to recreate Outlook profiles). The Minimal HCW will also permit yous to exist in a supported scenario when you take Exchange Online Mailboxes and the AD users synced to Azure Advertisement and yous will demand to manage your Function 365 Mailboxes using on-bounds Exchange 2010 / Exchange 2013 Management tools (Exchange Admin Center and Exchange Management Shell). This is due to directory synchronization which requires administration of Substitution Online Mail Attributes from on-premises Exchange for your synced users. Managing Exchange Online Mailboxes from Substitution 2007 or Exchange 2003 servers after mailbox migration is non supported. More than about Minimal and Limited Migrations can be institute here.

Here are some considerations that you need to accept into the business relationship when you lot perform an IMAP Migration:

• Merely items in a user'south inbox or other post folders tin be migrated. You can't migrate contacts, calendar items, or tasks. (Note that we are working on a richer migration experience for Thousand Suite to Exchange Online migrations, equally mentioned here.)
• By default, the maximum message size that can be migrated is 35 MB. This can be increased up to 150 MB.

There are 2 ways to perform an IMAP migration to Function 365:

1. Using a graphical user interface: either Commutation Admin Center or Office 365 Admin Center
2. Using PowerShell

Either method you choose, the IMAP migration needs an IMAP Migration Endpoint created showtime. Hither are some screenshots from Office 365 Substitution Admin Center that show where to locate and create Migration Endpoints: And this is a PowerShell view of an IMAP Endpoint (from get-migrationendpoint) established with remote IMAP server on port 993 and using SSL: If you take bug with creating the IMAP Endpoint, you can apply Test-MigrationServerAvailability command while continued to Exchange Online PowerShell to test IMAP connectivity:

Exam-MigrationServerAvailability -Imap -RemoteServer <Your IMAP server> -Port 993
Exam-MigrationServerAvailability -Imap -RemoteServer <Your IMAP server> -Port 143

When you create the migration batch and specify the Office 365 user mailboxes where y'all will migrate content via IMAP, the migration service will create Migration Users and respective Sync Requests for each user you lot specified in the CSV File. Similarly, for Hybrid Remote Moves (Full or Minimal Hybrid Configurations), you would have Move Requests created for the users. This is how you would create the Migration Batch via Commutation Admin Middle based on a CSV File where you specify the mailboxes you would migrate to: Yous can optionally exclude folders in the IMAP Migration Batch if you don't want to migrate specific folders, or if you find yourself in scenarios where nosotros have a corrupted IMAP binder. When troubleshooting failed IMAP migrations, Microsoft back up will need at to the lowest degree one of the post-obit XML reports from you:

Go-MigrationBatch -IncludeReport -DiagnosticInfo "showtimeslots, showtimeline, verbose" | Consign-Clixml C:\temp\EXO_All_Batches.xml
Get-MigrationBatch <Specific Migration Batch Name> -IncludeReport -DiagnosticInfo "showtimeslots, showtimeline, verbose" | Export-Clixml C:\temp\EXO_Batch_X.xml
Get-MigrationUserStatistics <affected user SMTP> -IncludeSkippedItems -IncludeReport -DiagnosticInfo "showtimeslots, showtimeline, verbose" | Export-Clixml C:\temp\EXO_MigUserStats1.xml
Get-SyncRequest -Mailbox <affected user SMTP> | Become-SyncRequestStatistics -IncludeReport -DiagnosticInfo "showtimeslots, showtimeline, verbose" | Consign-Clixml C:\temp\EXO_SyncReq.xml

However, depending on when (in which stage) things accept failed, we might not always have a Sync Request for the user or even have a Migration Batch. In that case, you would run commands like to these:

Become-MigrationEndpoint |FL
Test-MigrationServerAvailability -Endpoint <Identity of the IMAP endpoint from above>
Test-MigrationServerAvailability -Imap -RemoteServer <IMAP server> -Port 993
Examination-MigrationServerAvailability -Imap -RemoteServer <IMAP server> -Port 143
Get-MigrationBatch
Get-MigrationUser
Get-SyncRequest -Mailbox <affected user>

If you do take a Sync Request created for the user that failed migration, then you should run Get-SyncRequestStatistics command, equally described above, to export the XML report in order to remember more data on the cause of the issue. If you don't have a Sync Request created, but yous have a Migration User, you would run Become-MigrationUserStatistics command, as described above. Usually, when customers open back up cases with back up, for whatever migration to Office 365, this is because of 2 main reasons:

• Migration failed, and they are unable to migrate one or more than users to Office 365. Errors pause down in ii categories:
  • Permanent – the error that actually made the migration fail
  • Transient – errors which might ho-hum down the migration to the point where it might fail at the stop
• Migration is irksome or stalled due to Office 365 Resource Throttling or IMAP Server performance problems. These depend on many factors like source server functioning and network related configurations, capabilities or issues. More info here. It can besides happen that Office 365 will stall the migrations to protect Office 365 Servers wellness and also because migrations have a lower priority assigned than things similar mail service-flow tasks or client connectivity. More info on that tin be establish here.

Based on the failure y'all got in the Sync Request Statistics or Migration User Statistics, y'all tin find out what is causing the issue and become more details on the migration error. When troubleshooting an IMAP Migration, detect out if you have a Sync Request created for the user. If there is one, you would recollect the Sync Asking Statistics for information technology and store it in a variable or directly consign it in an XML report to await at it into detail. To come across if the sync request is created for the user, run the following command in Exchange Online PowerShell:

Get-SyncRequest -Mailbox <Affected User SMTP>

Bank check the STATUS of the Sync Request, is it Failed / Synced / Syncing? Supposing it is Failed, you would then shop the Sync Request Statistics into a variable, I used $syncstats in my case below.

$syncstats = Get-SyncRequestStatistics crystal@contoso.com -IncludeReport -DiagnosticInfo "showtimeslots, showtimeline, verbose"

We would and then await at the failures. Here are some examples of commands to check various failures:

• Retrieve Last Failure: $syncstats.Report.Failures[-one]
• Retrieve the Last two Failures: $syncstats.Report.Failures | select -Concluding two
• Retrieve First Failure: $syncstats.Study.Failures[0]
• Count all failures and grouping them by failure type: $syncstats.Report.Failures | group failuretype | ft -autosize
• Listing all the failures with their details: $syncstats.Report.Failures

Similarly, if yous don't accept a Sync Request simply exercise have a Migration User created and we failed to create a Sync Request, we would need to gather the Migration User Statistics for that user in lodge to get more details. If you run Go-MigrationUser, yous would listing all migration users: their Identity, Name of the Migration Batch user is role of, Condition and Last Synced fourth dimension. Instance (Become-MigrationUser): We would then shop the Migration User Statistics into a variable or consign to XML.

# Store into a variable:
$ustats = Get-MigrationUserStatistics crystal@contoso.com -IncludeSkippedItems -IncludeReport -DiagnosticInfo "showtimeslots, showtimeline, verbose"
# Export to an .xml file:
Get-MigrationUserStatistics crystal@contoso.com -IncludeSkippedItems -IncludeReport -DiagnosticInfo "showtimeslots, showtimeline, verbose" | Export-Clixml C:\temp\EXO_MigUserStats1.xml

Next, we would use similar commands as we did to recollect failures and internal failures from Sync Request Statistics. For example, to recall Last Failure from a Migration User Statistics, you would run a command similar to this: $ustats.Report.Failures[-1] Notation that for troubleshooting IMAP failures, we prefer Sync Request Statistics instead of Migration User Statistics (if we have a Sync Request in place for the user). Side by side upwards, I have gathered some of more common (that we see in back up) IMAP Migration Errors / Failures and what you can practice to fix them.

1. Error: Imap server sent NO response to SelectCommand

Message : Imap server sent NO response to SelectCommand. Response lawmaking: '', bulletin: 'Invalid mailbox name: Junk/'.
Message : Imap server sent NO response to SelectCommand. Response code: '', message: 'Invalid mailbox name: Sent/'.

This tin be because we have invalid folder names with Forward Slash Characters. Reference here. If you lot don't demand to migrate these folders, you can exclude the folders from migration also.

2. Error: Mailbox folder hierarchy contains multiple roots: FolderHierarchyContainsMultipleRootsTransientException

Mistake: Mailbox binder bureaucracy contains multiple roots: [Folder1: EntryID: [len=54, data=563D313B503D494D41503B46503D37393145423136314534463244383234433438443433413634463936393641354444333942383235], ParentID: [len=54, data=563D313B503D494D41503B46503D33304134424342304331383135314645423643353933414244423837374630393933413432393135], Type: Generic], [Folder2: EntryID: [len=54,

The "duplicate root" parent folder is the "SomeHiddenFolder" that is non returned past IMAP LIST control. So, when MRS runs Listing to enumerate folder hierarchy, it gets something like this: Inbox SentItems TopLevelFolder TopLevelFolder/NormalSubfolder SomeHiddenFolder/ Folder1 SomeHiddenFolder/ Folder2 Note that SomeHiddenFolder is *not* returned as a separate entry in the LIST command output. You would wait in report.Failures to see the Folder Names impacted. In this instance, information technology is Folder1 and Folder2. Yous would check the Folder Hierarchy of the affected user by this error, paying attention to folder names and their parent folder. Problem tin can also exist duplicated folder names or parent folder to be a Public / Shared Binder (for those raising eyebrows correct about now – access to public folders through IMAP was a affair in legacy versions of Exchange, for example Exchange 2003). You lot tin can also run the following script to Listing IMAP Folders for that mailbox: Get-ImapFolders.ps1 from GitHub and send us the output to see the IMAP Folders List together with the Sync Request Statistics XML. Another thing you tin practice is run Remote Connectivity Analyzer for IMAP exam and select Exchange Server Tab (fifty-fifty if source IMAP server is not an Exchange server) and so IMAP Email nether INTERNET E-mail Tests, make full in the afflicted user settings and then SAVE report as HTML and send us the file in order to encounter the IMAP Folders list. Ultimately, our support can't do much for yous in this situation other than identifying problematic folders. It is up to you to make the Folder "SomeHiddenFolder" a SELECTABLE folder and if needed, talk over with your vendor where original data is located. Yous could too endeavour to create a new folder, selectable in IMAP and move the content from "SomeHiddenFolder" to this New Binder, including its subfolders, example Folder1 and Folder2.

3. Error TooManyLargeItemsPermanentException has occurred

As per our current documentation, the message size limit that we can movement to Office 365 Exchange Online during an IMAP Migration is maximum 35MB. However, for IMAP migrations, where we need to accept mailboxes created in Role 365 before we tin migrate with IMAP, we can increment the bulletin size limit upward to 150MB on the target mailbox and this will allow email messages up to 150 MB size to be moved to Office 365 during IMAP Migrations.

Fix-Mailbox -Identity allonym@domain.com -MaxReceiveSize 150MB

This setting volition also allow the user to receive larger email messages via transport (if the sender is capable). We don't recommend lowering this limit back to 35 MB if you already migrated emails larger than 35MB. The Fault "Fatal Error TooManyLargeItemsPermanentException has occurred." suggests that nosotros reached the Large Item limit attack migration batch. Usually large item limit is set to 0 and if we encountered at least ane email message in the source mailbox bigger than 35MB (default MaxReceieveSize on the Function 365 Mailbox), the limit would have been reached and migration is failed for that user. So you need to either Increase MaxReceiveSize (maximum 150MB) on the afflicted O365 User Mailbox to exist able to migrate email letters larger than 35MB or increase the LargeItemLimit on the migration batch from GUI or from PowerShell with set-migrationbatch -LargeItemLimit 20 or on the Sync Asking (Fix-SyncRequest -LargeItemLimit Xx) so that we tin skip migration of these large items and migration won't fail considering of this.

4. Error: Imap server sent NO response to LoginCommand. Response code: '', bulletin: 'LOGIN failed.'.

MigrationPermanentException: Unable to log into business relationship. --> Unable to log into business relationship. --> The username or password for this account is incorrect, or IMAP admission is disabled. --> Imap server sent NO response to LoginCommand. Response code: '', message: 'LOGIN failed.'.

This error suggests bad login (wrong username or password) or that IMAP protocol is disabled. If more than or all users are affected, in that location might exist issues with IMAP server certificate. Suggestions for this issue: 1) Check if you are able to configure IMAP profile in Outlook Desktop for the user ii) Check if yous are able to connect to the IMAP Source Mailbox and List folders with one of these two methods:

• Run Become-ImapFolders.ps1 Script from GitHub
• Get to Remote Connectivity Analyzer for IMAP test and select Exchange Server Tab (even if source IMAP server is not an Commutation server) and so IMAP Email under Internet Email Tests, make full in the affected user settings as mentioned in the CSV file you used for Migration Batch and see if you are able to connect

three) Test-MigrationServerAvailability control in EXO PowerShell

Exam-MigrationServerAvailability -Imap -RemoteServer <IMAP server> -Port 993
Test-MigrationServerAvailability -Imap -RemoteServer <IMAP server> -Port 143

iv) If you apply a Super User / Admin password, brand sure the CSV file is created properly. See this and this. 5) If the source server is Gmail, this error message might happen because 2 footstep verification process/ app password which is required when migrating from it.

5. Errors that suggest RFC non-compliant source IMAP Servers.

For example, we might get a Permanent Failure after these transient failures which would brand migration to neglect for a specific user or more than.

MigrationMRSPermanentException: Mistake: The task encountered likewise many transient failures ‎(61)‎ and is quitting. The most common failure is ImapCouldNotParseResponseException/ImapUnexpectedTokenFormatException with the hit count 57. --> Imap server sent a response that we could non sympathise. Command: ‎'WIR01992 UID FETCH 16967 ‎(INTERNALDATE UID Body.PEEK[])‎ ‎'. Response: ‎'‎' >>‎'‎'. --> Unexpected response format - expected ‎')‎‎', bodily ‎' ‎'.

This error suggests that the IMAP server returned a bad response format, it was expected a parenthesis after Date / Time of the letters received. In this situation, yous would need to discuss with vendor where at the mailbox source to aid y'all ready this issue.

6. Errors that suggest Source IMAP Server Bugs or Internal Errors

Message : Imap server reported an fault during SelectCommand indicating that it encountered some bug: 'Internal error occurred. Refer to server log for more information. [2018-11-29 ten:forty:44] (0.002 + 0.000 + 0.001 secs).'.
DataContext : --------
Operation: ImapMailbox->GetFolderInternal<T>() for folder < >

The error message is generated at the selection of one or perchance more than folders on the Source IMAP server (SELECT command) and co-ordinate to the failure, the admin should bank check the logs that are generated on that IMAP server effectually the timestamp of the failure. To remember the Last Failure or the previous one before concluding, yous can use the commands below:

$syncstats = Get-SyncRequestStatistics user@domain.com -IncludeReport
$syncstats.Report.Failures[-1]
$syncstats.Report.Failures[-2]

You can use 1 of these 2 methods beneath to Listing the Source IMAP Folders for the user and come across their names:

• Run Become-ImapFolders.ps1 Script from GitHub
• Go to Remote Connectivity Analyzer for IMAP exam and select Exchange Server Tab (fifty-fifty if source IMAP server is not an Exchange server) and then IMAP Email under INTERNET Email Tests, fill in the IMAP User Details and bank check the List of folders.

If the folder referenced in the error is establish in the Sync Request Failure, y'all can endeavour to Exclude information technology from IMAP migration batch when retrying migration. Many thanks to all that contributed to this web log post: Nino Bilic, Brad Hughes and Cristian Dimofte.

hinkleforgerbours.blogspot.com

Source: https://techcommunity.microsoft.com/t5/exchange-team-blog/troubleshooting-imap-migrations-to-office-365/ba-p/608832

Share this post