Return
-
Title
The folder '[folder_name]' was not processed. Messages in folder: '[# of messages]'. Probably the given folder does not exist in target mailbox. If the problem is persistent, please resync mailbox with ClearAllSyncDataOnResync -
Description
MMEX 8.13 Public Update 20161024EX is installed, Migration Agent for Exchange is set up to synchronize mailboxes and you see error "The folder '[folder_name]' was not processed. Messages in folder: '[# of messages]'. Probably the given folder does not exist in target mailbox. If the problem is persistent, please resync mailbox with ClearAllSyncDataOnResync" in the Most Recent Error field of the Statistic pane.
-
Cause
The issue can be caused by one of the following reasons:1) Source mailboxes added to MAGE collections before installing MMEX 8.13 Public Update 20161024EX had duplicate folders or subfolders2) Duplicate folders or subfolders appeared in source mailboxes added to MAGE collections after installing MMEX 8.13 Public Update 20161024EXThe issues can occur if any of the below listed type of duplicate folders or subfolders is found in the source mailbox:- Source mailbox contains duplicate folders. (Folders having the same name.) One of these folders being the default well-known folder, like Contacts, Calendar, etc. another one being a non-default folder with exactly the same name.- Source mailbox contains folders of the same folder class in different languages, like both Agenda and Calendar, where Agenda being a default folder and Calendar being its non-default duplicate in English.- Source mailbox contains duplicate subfolders of any of the default folders, for example, two subfolders with the same name under Inbox, Sent Items, Calendar, etc. folder.- Source mailbox contains two or more folders having the same name and different index, for example, Calendar and Calendar1, Calendar2. etc. -
Resolution
RESOLUTION I. If MMEX is set to use "EWS as source" (please see UseEwsProtocolForSourceIfAvailable parameter at https://support.quest.com/technical-documents/migration-manager-for-exchange/8.13/user-guide/configuring-migration-using-powershell)To resolve the issue, please delete the target mailbox contents with Search-Mailbox -Identity -DeleteContent commandlet as described in https://support.quest.com/migration-manager-for-exchange/kb/153020 and resynchronize mailbox in the mailbox collection with the ClearAllSyncDataonResync parameter.RESOLUTION II: If MMEX is set to use MAPI as sourceTo resolve the issue, please resynchronize such mailboxes with the ClearAllSyncDataonResync parameter. The parameter can be set for a mailbox or calendar collection as described in Configuring Migration Using PowerShell at https://support.quest.com/technical-documents/migration-manager-for-exchange/8.13/user-guide/configuring-migration-using-powershellIn both cases (EWS as source and MAPI as source) source duplicate folders or subfolders will be copied to the target in the following way:If the source mailbox has two folders or subfolders with the same name, both duplicate folders will be copied to the target mailbox. One folder will have its original name, another one will be named as '[Folder_Name]_[Source_key]' where [Source_key] will be the actual PR_SOURCE_KEY property value.For example:If the source mailbox has got two Calendar folders, target mailbox will have Calendar folder and Calendar_[Source_key] name.