Forum Discussion
Email body blank for some messages in Outlook with Exchange accounts in cache mode
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
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.
- Update: Another user on a Microsoft thread did some research and found that Outlook has changed the way it interprets CR without LF in a text email. Without a LF after a CR, it gets interpreted as end of text. Another workaround that we have applied to our systems that are generating these text emails is to add CHAR(10) after every CHAR(13) and it fixed the issue (or at least now Outlook continues processing the text).
See this thread for more detail:
https://learn.microsoft.com/en-us/answers/questions/1220974/some-outlook-text-emails-are-blank-in-preview-pane- We are still working with MS support on this but have narrowed it down to flagged messages, they are getting us try try various things including making sure the user is signed in to to do. I will update further if we get any additional information or a resolution.
