Generating an MS Word Report: 'ERROR: Word has experienced a problem'

[bezzoh]

Since the latest Jan Office 365 update, I'm getting a raft of notifications that when trying to generate a MS Word based report it kicks up a SIMS .net message "ERROR: word has encountered a problem"

 

Nothing more, not a bean to the event log. This occurs for pre-existing user profiles. You wipe the profile, log in for the first time and try again it's just fine.. next log out/back in, broken again. This is happening across multiple sites, completely different domains. Seeing as I'm getting it at multiple sites, I can't be the only one??

[benp-it]

Hi Bezzoh, I also have this issue with a few of our reports - did you manage to find a fix? I have exhausted every avenue it feels!

[JobyCCN]

We have also had this issue. It appears to be issue with word list reports and the latest version of office365.

We rolled back from version 2301 (build 16026.20146) to Version 2212 (Build 15928.20216) and this fixes the issue. We have disabled updates for the moment until the next update to see if its fixed.

[ajp233]

KB0052299 - Latest Version

Reporting - "Error: Word has encountered a problem" when running Word list reports

• a day agoa day ago • 219 Views • (*) (*) (*) ( ) ( )

Description of Issue

 

When running a Word list report from SIMS, the below error shows:

 

Environmental information

 

We have found that this issue occurs on the below versions of Microsoft365:

 

Version 2212 Build 16.0.15928.20196

 

Version 2301 Build 16026.20146

 

The version of Microsoft365 in use can be checked by going to the menu route File > Account and viewing the About Word section.

 

Cause

 

If you are experiencing this issue please log a case with your usual support unit.

 

 

 

We are currently investigating the cause of this. This article will be updated with further relevant information as it is made available.

[benp-it]

Yup this fixed it, went back to 2211 Build 15831.20208 and the report works! Thank you!

[bezzoh]

Indeed a rollback works. I have found the underlying cause and implemented a temporary fix not requiring a rollback which just wasn’t feasible in my estate.

 

I’ve provided the info to ESS and discussed with one of their engineers who is looking at the problem. He is going to liaise with Microsoft directly as in short though I’ve ‘fixed’ it neither I nor ESS understand what other impact my change might have (though none has been observed yet.) As such, ESS have asked I do not propagate my fix to other customers as there may be unforeseen adverse effects.

 

Bear in mind the next update is due out Tuesday.. which may well fix the issue also but MS have documented nothing about this problem yet that we can find.

[ajp233]

ESS have now advised the following:

 

Resolution

 

After investigating this issue and based on information from Microsoft, this issue is caused by a bug in Microsoft365, as discussed here: https://answers.microsoft.com/en-us/msoffice/forum/all/word-vba-function-insertfile-is-now-failing-on-all/f5265c8e-23b9-42b6-b219-1e4cefba7752?page=5

 

Microsoft have advised that this issue will be addressed in an update to Microsoft365