Link to home
Start Free TrialLog in
Avatar of pchettri

asked on

Exchange 2013 large items error

I need to find a PowerShell command to find any email larger than 40 mb and delete them PowerShell. From outlook I have already archived large but Exchange still reporting two items

 4/17/2017 5:32:22 AM [CY4PR02MB2855] Copy progress: 25210/36229 messages, 4.703 GB (5,050,116,854 bytes)/7.07 GB (7,591,246,652 bytes), 30/806 folders completed.
 4/17/2017 5:37:28 AM [CY4PR02MB2855] Stage: CopyingMessages. Percent complete: 72.
 4/17/2017 5:37:28 AM [CY4PR02MB2855] Copy progress: 29463/36229 messages, 4.835 GB (5,191,627,564 bytes)/7.07 GB (7,591,136,366 bytes), 51/806 folders completed.
 4/17/2017 5:42:01 AM [CY4PR02MB2855] A large item was encountered: Item (IPM.Note) Subject:"Tomorrow's Meeting at Noraxon", Size: 233.5 MB (244,875,768 bytes), Folder:"Deletions"
 4/17/2017 5:46:49 AM [CY4PR02MB2855] A large item was encountered: Item (IPM.Note) Subject:"FW: PowerPoint Template", Size: 388.5 MB (407,340,052 bytes), Folder:"Deletions"
 4/17/2017 5:46:49 AM [CY4PR02MB2855] Stage: CopyingMessages. Percent complete: 79.
Avatar of pchettri

Link to home
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Do you still need any help?
Avatar of pchettri


Is there any command that could be run to simulate new-moverequest and find error about possible report before moving? It is annoying get error after 94% and test process or simulation would be nice and useful
Unfortunately, there is no such option. Best to skip corrupted items.
Have you attempted to use the "WhatIf", "AllowLargeItems" or other parameters for the New-MoveRequest command when moving mailboxes?

I have used allowlargeitems and baditemslimit unlimited on all my command. The best way to do it faster is resume cmdlets but it does not complete the request, if the previous one stopped with error, therefore, the best bet is to delete previous request batch and start from scratch and wait for another error to show up or hope for the best.
Personally and technically, I see it was design flaw and I did give feedback to MS portal after discussing this issue with MS support. They should create script or shell command to run test for migration success. Specially, if there is a test that can pre-access the situation it will really be good for planning larger mailboxes.
I have already added details on Your Comment
ID: 42096398

I found large items on deleted item retention using powershell and deleted all those email which fixed the issue
fixed on my own