Posts tagged ‘Outlook’

Outlook Message Body Blank

Suddenly many users alerting that the message body of their e-mails, using Outlook desktop app, are blank. Also they cannot type in the body of a new e-mail or reply. Microsoft has released the following statements:

Latest message, May 11, 2021 7:24 PMView historyTitle: Issue affecting viewing email content in Outlook User Impact: Users may be unable to view email message content within Outlook. More info: Impact is specific to the Outlook client and users with access to other protocols, such as Outlook on the web or the Outlook mobile app, can view message content in those platforms as a potential workaround while our fix is applied. Current status: We’ve identified the underlying cause of impact and are applying a fix. This fix will reach all affected users incrementally over the course of the next four-to-five hours. Once users receive the fix, they will need to restart their email client to apply the fix. In some circumstances, users may need to restart their client a second time for the changes to take effect. We expect to complete this process and restore service for all affected users by May 12, 2021, at 3:00 AM UTC. We encourage affected users who are able to do so to leverage the workarounds described above in the “more info” section of this post while we complete the process of fixing this problem. Scope of impact: This issue could affect any user attempting to view an email message in the Outlook client. Root cause: A recent change to systems that facilitate text display management for content within the Outlook client caused impact. Next update by: Wednesday, May 12, 2021, 12:00 AM (3:00 AM UTC)

“May 11, 2021 6:19 PMView historyTitle: Issue affecting viewing email content in Outlook User Impact: Users may be unable to view email message content within Outlook. More info: Initial reports indicate that impact is specific to the Outlook client and users with access to other protocols, such as Outlook on the web or the Outlook mobile app, can view message content in those platforms as a potential workaround. Current status: We’re continuing to analyze recent updates to the environment and the associated code as we work to isolate the cause of impact. Our efforts are focused on determining the most expedient means of remediating this issue. Scope of impact: This issue could affect any user attempting to view an email message in the Outlook client. Next update by: Tuesday, May 11, 2021, 7:30 PM (10:30 PM UTC)

May 11, 2021 5:28 PMView historyTitle: Issue affecting viewing email content in Outlook User Impact: Users may be unable to view email message content within Outlook. More info: Initial reports indicate that Outlook on the web is unaffected and users with access to Outlook on the web can view email messages there while we work on a solution. Current status: We’re gathering and analyzing data in an effort to isolate the cause of impact. Initial reports indicate that impact is specific to the Outlook client and users with access to other protocols, such as Outlook on the web or the Outlook mobile app, can view message content in those platforms as a potential workaround. Scope of impact: This issue could affect any user attempting to view an email message in the Outlook client. Next update by: Tuesday, May 11, 2021, 6:30 PM (9:30 PM UTC)”

Ping command…..needs to close

I had a client today advise they were unable to send or receive e-mail using Outlook.  Upon initial inspection this was the case and Outlook showed as disconnected (using Exchange).  There were no other obvious issues, web browsing and all network services “seemed” to be working properly.  However, there were frequent pop-ups with the message:   

TCP/IP ping command has encountered a problem and needs to close

Pinging did work fine, for the record. While doing a quick search for possible solutions I came across many others with a similar problem, so I thought I would take a moment to post my findings. 

The Event logs had additional errors the key one being:  Event ID: 4226,  Source: Tcpip,  TCP/IP has reached the security limit imposed on the number of concurrent TCP connect attempts.

Though there could be other causes, this usually indicates some sort of malware, as confirmed by EventID.net 

Kaspersky’s Anti-rootkit utility TDSSKiller located 2 viruses, and AVG a third as shown in the image below. Keep in mind other viruses could present themselves in the same way.  Clearing all temp folders and a full scan by multiple other malware detection apps did not reveal any other issues, but one must always be concerned that “once infected, always suspected”.   Outlook now worked properly with no repairs required to the application or networking.

image

Cannot open the Outlook window. Invalid XML

I recently came across an instance of Outlook 2007 which would not open.  A popup reported; “Cannot start Microsoft Office Outlook. Cannot open the Outlook window.  Invalid XML, the view cannot be loaded”.  This was only occurring on 1 PC, for one user, in an SBS 2008 environment.  If the user ran Outlook on another PC, there was no problem so it was obviously a local problem.  Doing a repair install of office did not resolve, nor did the diagnostics suggested when Googling the issue.  Assuming it was a problem with the Xml file; I closed Outlook, renamed the Outlook.xml file (safer than deleting), and restarted Outlook to find the problem was resolved.  Should you wish to try the same solution, the file path with Office 2007/2010, on Vista\Win 7 is C:\Users\<user name>\AppData\Roaming\Microsoft\Outlook\Outlook.xml   You will need to enable “Show hidden files, folders, and drives” and “Hide extensions of known file types” to view.

image

Tag Cloud