Word VBA function InsertFile is now failing on all builds from 15427.20194 Aug 3, 2022 and later

Anonymous
2022-09-11T17:03:40+00:00

We have a product that assembles custom templates that has been around for about 20 years that operates on a library of about 1 million Word .docx format templates.  With users across the world.  Its been in use on every version of Word since 2003 (currently only supported on all versions of Office 365 but it also still works on Word 2010).   We use the Word VBA function InsertFile to append pages together to create custom documents from the template library.

Recently all of our installations started failing with the InsertFile function returning error 5097 - "Word has encountered a problem".  And customers have started reporting the same error.

We traced it down to being introduced in the Aug 3 Build of Word and verified it on multiple computers (both Windows 10 and Windows 11).   If we roll back our Word builds through the last 7 builds we found that in every case the June 14, June 29, July 6, July 18 builds of Word work fine.   But all 3 builds after that which are Aug 3, Aug 9 and the current Aug 31 fail.

Something appears to have been recently broken by Microsoft in the Aug 3 Build that causes the Word's InsertFile function to fail.    This happens on almost all of our Word .docx template we have tested.    But when inserting the file via the Word toolbar's Insert > Text From File > browse to the file it works.  But it always fails now when calling the InsertFile function via VBA.   Again, this is not a new macro or templates.  This code has been in use for almost 2 decades and the templates have been in use for for many years.   Its only since the recent builds of Word in the last month that installations are now starting to fail everywhere.

This zip file linked below contains the macro vba test function and some example files to reproduce the problem.

InsertFile Failure Test

When we save those templates that are failing to insert as legacy Word 2003-2007 .doc files they do insert without failing.   And if we save them in Word 2003-2007 XML or as an OpenDocument .odt file they insert correctly.   But if we save them as Word XML .xml or Strict Word XML .xml they also fail.  So there is nothing corrupt in the files, it appears to be inserting current format files of various file formats are failing, but saving those failing files as legacy formats they insert correctly.

How do we submit this problem to Microsoft's Office 365 team as a bug report? This is a serious problem that breaks our product and requires us to have everyone roll back their Office 365 to the July 18, 2022 build and we're in the process of having to update our product to provide instructions when the error occurs on how to roll back Office 365.

The code in the test script is also here. But it needs the .docx files from the ZIP file to operate on.

Sub InsertTest()

Dim DocRng As Range  
Dim FileToInsert As String  
Dim SourceFile As String  
Dim MsgStr As String  
Dim MsgResult As Long  
          
On Error GoTo ErrHandler  
 
SourceFile = "c:\temp\CoverLetter.docx"  
  
FileToInsert = "c:\temp\ExecSummaryA.docx"      ' This file fails to insert  

' FileToInsert = "c:\temp\ExecSummaryB.doc" ' This file works (this was the ExecSummaryA.docx Saved As a .doc file in Word 2003-2007 format)
' FileToInsert = "c:\temp\AccessoriesA.docx" ' This file fails to insert
' FileToInsert = "c:\temp\AccessoriesB.doc" ' This file works (this was the AccessoriesA.docx Saved As a .doc file in Word 2003-2007 format)

Documents.Open FileName:=SourceFile  

ActiveWindow.ActivePane.View.Type = wdPrintView  
  
Set DocRng = ActiveDocument.Content  

DocRng.Collapse (wdCollapseEnd)  
              
DocRng.InsertFile FileName:=FileToInsert, Range:="", ConfirmConversions:=False, Link:=False, Attachment:=False  

Exit Sub  
  

ErrHandler:

MsgStr = "Error: " & Err.Number & " - " & Err.Description  

MsgResult = MsgBox(MsgStr, vbSystemModal + vbMsgBoxSetForeground, "Insert Error")  

End Sub

Microsoft 365 and Office | Word | For home | Windows

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments
Answer accepted by question author
Anonymous
2023-03-01T15:20:19+00:00

Great news. The 2302 patch just came out, tested it on a couple computers here and the InsertFile function is now working properly.

Was this answer helpful?

1 person found this answer helpful.
0 comments No comments

66 additional answers

Sort by: Most helpful
  1. Anonymous
    2022-10-06T01:06:47+00:00

    Doug - do bribes work? If you want to pass along to the 365 team I'll give someone foil surfing lessons in exchange for helping me out. Seriously - I live a few blocks from Microsoft campus in Redmond on the lake. Already taught my neighbor who works there how to foil surf.

    Also, you just gave me another idea for a workaround I can try adding. Instead of copy/paste from the templates that are failing maybe I can make a new temporary document and copy/paste from the failing .docx files into a new file copying the body content, headers and footers. Then import the temporary newly created .docx. Then I can look into adding a library rebuild tool that can run through all 2200 templates each customer has and rebuild them using the create new doc and copy/paste.

    Still doesn't solve the problem for half the people, but if it resolves the problems with some background graphics and footer problems using the other temporary workarounds it will help.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2022-10-05T23:33:15+00:00

    Nope, never had a need for support plans. I'm more than willing to work on the problem with someone, but not going to buy a support plan for it if its someone elses stuff that broke.

    Was this answer helpful?

    0 comments No comments
  3. Doug Robbins - MVP - Office Apps and Services 323.6K Reputation points MVP Volunteer Moderator
    2022-10-05T23:13:59+00:00

    Hi Ian,

    If you have a Support Agreement with Microsoft, I would suggest that you attack it form that end as well.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2022-10-05T20:19:37+00:00

    Also, these patch workarounds in the software are only good for some of the people running into the problem. Brand new customers will now get the workaround kick in automatically with instructions to rollback their Office if things like missing footers are a problem.

    Only customers in the last 10 months can download a quick patch since we can't put in this patch into older versions of our software.

    Everyone else in the field with older editions of our software are faced with having to do a full version upgrade of our software and that's not always possible for companies with very customized systems and customized copies of our templates. And that's just to get the workaround options we put in, that still doesn't work for everyone. So for them they have had to rollback their Office 365 to a July build. And I've had to write up troubleshooting guides on our web site for how to rollback Office for all of them.

    Half the companies who have had this problem crop up have had to disable their Office updates and roll it back.

    Was this answer helpful?

    0 comments No comments