Forum Discussion
PeterWhitehouse
Feb 12, 2023Iron Contributor
Email body blank for some messages in Outlook with Exchange accounts in cache mode
As per the thread title we have a user that has random messages in their Outlook exchange accounts showing no information in the message body for random emails, the emails are fine in online mode, OW...
Compumat
Apr 07, 2023Copper Contributor
Did you have any solution on that?
Same problem with only 1 user.
Exactly the same, uninstaller, Eset uninstaller, rebuild,...
thanksPeterWhitehouse
- JHardwoodApr 12, 2023Copper Contributor
Any learnings/fix for this issue? We started having this issue late last week for several, but not all users. What is really puzzling, is that the email body is blank when opened, but if the user clicks to forward, or reply, or print, all of the text then displays.
Jeff
- CompumatApr 14, 2023Copper ContributorNot yet. I will continue to look for a solution. If there is any solution by you, I would like to hear it.
- JHardwoodApr 14, 2023Copper Contributor
We don't have a fix, but we do have a workaround. In our case, this issue seems to have been caused by some recent Microsoft updates. We were able to work around the problem by switching the update channel for the user from "Curent" to "Semi-Annual". This backs out recent fixes, and the problem goes away (for now). The hope is that the updates will curate over the next few months and when they eventually do hit the computer, the issue will since have been resolved.
In Outlook, click File, Office Account, and then look under "About Outlook". If you see "Current Channel", you can try the following to switch the user to "Semi Annual" channel.
Close MSOutlook and all other MS apps
Run cmd window as Administrator
cd C:\Program Files\Common Files\Microsoft Shared\ClickToRun
OfficeC2RClient.exe /changesetting Channel="SemiAnnual"
OfficeC2RClient.exe /update user
After the last command is run, a Window will popup and MS will install/switch updates accordingly. When done, go into MSOutlook and check to see if problem is resolved.
Again, I do not consider this a fix, but simply a workaround.