This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

The message exceeds the maximum supported size., Cannot save changes made to an item to store.

Hello all-

We are seeing some rather strange errors performing a mail sync for our pilot group.

"The message exceeds the maximum supported size., Cannot save changes made to an item to store." is showing up quite frequently for some users. We've increased the project message max size to 50MB per this article:

https://support.quest.com/migration-manager-for-exchange/kb/154093/the-mail-sync-mage-fails-with-info-skipping-message-size-limit-exceeded-or-generic-item-processing-error-

Identifying the failed items using SQL per this article (https://support.quest.com/migration-manager-for-exchange/kb/154093/the-mail-sync-mage-fails-with-info-skipping-message-size-limit-exceeded-or-generic-item-processing-error-)

renders the snippet below:


3605 cohara name  OTHER 25807 NULL 0x0003240064643063386237352D343932392D343538322D386331622D333330313862333535393361004600000000008A79977BA2D37D40A6024C474AEB2D3A07004CAFACDA134B84488F01CCCFEE449F63004D57A9810A00009CE25E9A9167A04FB1A20C3535936F5A0002CAC31D920000 Error in user file for MCN Policy Manager? 1909917425 2019-04-15 16:20:34.820 The number of items in the Exchange server’s response () does not match the number of items for which uploading was attempted (4).
3605 cohara name OTHER 25807 NULL 0x0003240064643063386237352D343932392D343538322D386331622D333330313862333535393361004600000000008A79977BA2D37D40A6024C474AEB2D3A07004CAFACDA134B84488F01CCCFEE449F63004D57A9810A00009CE25E9A9167A04FB1A20C3535936F5A00027C420EA70000 MCN Policy Manager User File data and procedure 1909917425 2019-04-15 16:20:34.850 The number of items in the Exchange server’s response () does not match the number of items for which uploading was attempted (4).
3605 cohara name OTHER 25807 NULL 0x0003240064643063386237352D343932392D343538322D386331622D333330313862333535393361004600000000008A79977BA2D37D40A6024C474AEB2D3A07004CAFACDA134B84488F01CCCFEE449F63004D57A9810A00009CE25E9A9167A04FB1A20C3535936F5A00019B609D000000 Rapid7 Response 1909917425 2019-04-15 16:20:34.867 The number of items in the Exchange server’s response () does not match the number of items for which uploading was attempted (4).
3605 cohara name OTHER 25807 NULL 0x0003240064643063386237352D343932392D343538322D386331622D333330313862333535393361004600000000008A79977BA2D37D40A6024C474AEB2D3A07004CAFACDA134B84488F01CCCFEE449F63004D57A9810A00009CE25E9A9167A04FB1A20C3535936F5A0000766EC0440000 RE: Service Owners - OCM Info Session re: Change Agents & Champions 1909917425 2019-04-15 16:20:34.913 The number of items in the Exchange server’s response () does not match the number of items for which uploading was attempted (4).
3605 cohara name OTHER 25807 NULL 0x0003240064643063386237352D343932392D343538322D386331622D333330313862333535393361004600000000008A79977BA2D37D40A6024C474AEB2D3A07004CAFACDA134B84488F01CCCFEE449F63004D57A9810A00004CAFACDA134B84488F01CCCFEE449F63015BCFDDB7060000 New Logo Information 1909917425 2019-04-15 16:20:44.740 The message exceeds the maximum supported size., Cannot save changes made to an item to store.
3605 cohara name OTHER 25807 NULL 0x0003240064643063386237352D343932392D343538322D386331622D333330313862333535393361004600000000008A79977BA2D37D40A6024C474AEB2D3A07004CAFACDA134B84488F01CCCFEE449F63004D57A9810A00004CAFACDA134B84488F01CCCFEE449F63015BCFDD4C720000 New FIM files... 1909917425 2019-04-15 16:20:44.773 The message exceeds the maximum supported size., Cannot save changes made to an item to store.
3605 cohara name OTHER 25807 NULL 0x0003240064643063386237352D343932392D343538322D386331622D333330313862333535393361004600000000008A79977BA2D37D40A6024C474AEB2D3A07004CAFACDA134B84488F01CCCFEE449F63004D57A9810A00009CE25E9A9167A04FB1A20C3535936F5A00027C3F3E0F0000 Emailing: Unified Communications with Lync 1909917425 2019-04-15 16:20:47.537 The message exceeds the maximum supported size., Cannot save changes made to an item to store.

I enhanced the byte size of these failed messages. Note the tool reports back the same message size is 1.8GB. When I run a Powershell script to query this user's mailbox for top message sizes, the largest item is a calendar entry at 24MB

[PS] C:\Windows\system32>Get-MailboxFolderStatistics -Identity xxxxx -IncludeAnalysis -FolderScope All|Where-Object {($_.TopSubjectSize -GE 20000000.0)} | Select-Object Identity, TopSubject, TopSubjectSize

Identity TopSubject TopSubjectSize
-------- ---------- --------------
xxxxx\Calendar PFT Lab Security Requirements 23.91 MB (25,070,674 bytes)

How does the MAGE determine message size? Why would 7 failed messages have the exact message size that is obviously an error? I've checked the target mailbox for this user and these messages were not copied. Could this be indicative of mailbox corruption?

Any insight into this is greatly appreciated.

Regards,

Eric

Parents Reply Children
  • Thanks, Enrico. To answer your questions: No, we are not running MessageStats. Just using old-fashioned PowerShell. Yes. I've gone into both the source and target user mailbox. As for moving the mailbox to another database/server, I was thinking about doing that which would then lead me down a corrupted message path. I issued a re-sync for this user to see if anything changes. If you can find that Tweet, that would be great.