{"id":1915,"date":"2018-06-19T01:00:00","date_gmt":"2018-06-19T01:00:00","guid":{"rendered":"http:\/\/inswwdev.azurewebsites.net\/au\/insights\/uncategorized\/rage-against-the-corrupted-item\/"},"modified":"2018-06-19T01:00:00","modified_gmt":"2018-06-19T01:00:00","slug":"rage-against-the-corrupted-item","status":"publish","type":"post","link":"https:\/\/www.insentragroup.com\/nz\/insights\/geek-speak\/migrations\/rage-against-the-corrupted-item\/","title":{"rendered":"Rage Against the Corrupted Item"},"content":{"rendered":"

By now you would\u2019ve read my previous blogs where I walked you through completing cross forest mail migrations, setting up cross forest mail flow and implementing this thing called multi-tenancy. If you haven\u2019t read those blogs, stop reading this one, click on the links below and come back:<\/p>\n

The Mother of All Cross Forest Migrations<\/a><\/p>\n

Exchange Cross Forest Mail Flow\u2026Wait What?<\/a><\/p>\n

The Beast That Is Multi-Tenancy<\/a><\/p>\n

If you have read my previous works of art, you\u2019re awesome, you can collect $200 and pass go! AKA please continue reading the next instalment of \u201cWhat else can pure awesomeness tell us that will help me get some sleep at night during my next mail migration project?\u201d<\/p>\n

Read on my loyal apprentice\u2026<\/strong><\/p>\n

I know what you\u2019re thinking\u2026after cross forest mail flows and migrations and setting up multi tenancy, what on earth is there to talk about this time? I\u2019ll tell you\u2026the one thing that had me scratching my head and trying to pull out whatever hair I had left on my head\u2026the infamous migration batch failures where Microsoft says, \u201cyou know what, we\u2019re just going to throw you a random error message but not tell you what caused it.\u201d I know I said I was I was scratching my head, but when this happened (and of course it was late at night) the reality was, I\u00a0<\/span>was<\/em>\u00a0<\/span>performing violent knocks of my head against something solid, otherwise known as the head bang!<\/p>\n

(if you don\u2019t want to read the entire blog, I have found this approach to be useful for such situations although it doesn\u2019t actually resolve the technical problem \u2013 just causes a different type of headache).<\/p>\n

\"\"<\/p>\n

However, if you want to save yourself let\u2019s keep reading\u2026.<\/p>\n

WHAT THE BEEP WAS THE ERROR MESSAGE?<\/span><\/h3>\n

What was the error message I hear you asking? I\u2019ll tell you and then you be the judge whether the violent knocks of the head were justified\u2026Error Message: FailedOther<\/p>\n

Now when you\u2019re in the middle of a change window and have limited time, the last thing you want is to see such a cryptic error message, but I guess anything is better than 0x000440535 error codes where not even Dr Google can help you!<\/p>\n

As I was saying, FailedOther! And what made this even more cryptic was the mailbox migrations for this particular batch had already completed up to 95%! See! Head bang = justified!<\/p>\n

So now the change window I was in was nearing the end and after running a ridiculous amount of PowerShell cmdlets trying to figure out what was going on, because you know, who needs to scour through a 6MB text file trying to find the words FailedOther, I was at my wits end when a little Ewok appeared on my shoulder and whispered in my ear\u2026Bad Items! Jumping out of my seat like someone was trying to imprint the hashtag #OTOD (If you want to know what OTOD is read this awesome\u00a0<\/span>blog<\/a><\/strong>\u00a0<\/span>by our CEO Ronnie Altit) \u00a0onto me using a branding iron, I grabbed my phone, called the Project Manager and asked him to extend the change window by just a fraction as I knew at that point, I found the root cause!<\/p>\n

So, you mad man made of pure awesomeness, how did you get this fixed?? As with my previous blogs, you\u2019re going to find out by following 3 easy steps listed below (and yes in this order):<\/p>\n