How to Solve the Error: A Corrupted Item Was Encountered Folder ACL?
This error “a corrupted item was encountered folder acl” arise when public folder migration fails. This may be because of large Exchange public folders. Don’t worry, this write-up will provide the solution to fix the error.
But before moving towards the solution to solve this issue let’s go through th user query:
“I have signed to migrate my company public folder to O365 environment but after performing the migration, it failed and the user report state that a corrupted item was encountered folder acl. Does anyone encounter with this error before? Please suggest me how to fix the issue given below”
5/08/2017 8:22:05 PM [DB3PR08MB0107] A corrupted item was encountered: Folder ACL
5/08/2017 8:22:10 PM [DB3PR08MB0107] A corrupted item was encountered: Folder ACL
5/08/2017 8:22:10 PM [DB3PR08MB0107] A corrupted item was encountered: Folder ACL
5/08/2017 8:23:10 PM [DB3PR08MB0107] A corrupted item was encountered: Folder ACL
5/08/2017 8:23:11 PM [DB3PR08MB0107] A corrupted item was encountered: Folder ACL
Users can avoid this error by using the Exchange Database Repair Tool provided by SysTools which easily migrates private mailboxes and public folders of any size to Office 365 in a simplified manner.
How to Fix the Error: A Corrupted Item Was Encountered Folder ACL?
It is difficult to troubleshoot the error because the procedure is supported by Microsoft which involves number of scripts & it depends on various Exchange Server factors. Additionally, there are so many point of failures which takes time for users to understand the error:
Users have to consider some limitation while migrating the public folders to MS O365.
- MAX Public Folders – 250000
- Max Sub-folder in Public Folder – 10000
- Max item/folder – 1000000
- Max Exchange Public Folder mailboxes – 1000
You have to consider the item size which cannot be more that 49 MB. In migration, the entire process may stop if the large items isn’t skip.
Microsoft Exchange Public folder is highly used in various IT organization. Also, it may arise issue then they are of large size. But nowadays, it seems that MS is eliminating it when they launch the Exchange Shared mailboxes, Microsoft Groups as well as Teams, which is awesome.
Another solution is to export the Exchange public folder to Outlook data file and import PST to MS O365 via blog storage for the import & XML file to start the migration. Sadly, users cannot use the Exchange PowerShell New-MailboxExportRequest to export Exchange public folder to PST file. In spit of that, you can use Microsoft Outlook to export it. For this users need to have install the Outlook and other resources but here also this manual solution have some limitations that waste users precious time and effort.
Instead of it users can use the alternative solution to easily perform the migration of public folders directly to the MS O365 in a hassle freeway.
An Automated Solution
There is no alternative to avoid the error but there is an alternative solution i.e. Exchange Database Repair Tool which supports both offline / dismounted public folders & private mailboxes and users can easily migrate offline EDB to Office 365 along with public folders automatically without using any command.
This software provides Quick and Advance scan mode which removes corruption from Exchange database file and repair Exchange mailbox with no data loss. Users can use the Quick scan to remove minimal corruption and if the EDB file is highly corrupted then select the advance scan.
After recovery, users can extract mailbox from EDB file Exchange 2016/2013 to the Live Exchange Server mailboxes, O365 and multiple file formats. It also auto-creates the export report which contains the success and fail count of exported Exchange mailbox data. The utility supports all versions of Exchange Server, Microsoft Outlook and Windows OS.
Bringing It All Together
To avoid the error “a corrupted item was encountered folder acl”, now users have use the simple and quickest solution described in the above method that migrates the Exchange public folders to the O365 in a hassle freeway and by using this method you don’t need to worry about Outlook data file size limitation or MS public folders size. It is the perfect solution for migration than other.