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: Newest
  1. Anonymous
    2022-10-04T21:48:29+00:00

    Were about another month in and the most recent Office 365 update and Windows updates didn't change anything. We continue to have more and more customers from all over the world experiencing this problem. Some are new customers some are longtime customers who have had their Office 365 recently updated who are now having the problem. All are using different sets of templates as well. The only commonality is that they all have one of the more recent Office 365 builds that is failing.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2022-09-16T17:10:31+00:00

    Yes Charles, I know and I have had my issue picked up by a couple MVPs and one forwarded it to the Office 365 team this last weekend on another thread. But posting these questions in other forums like for end users has been useful when others with the same problem respond and sometimes someone has a solution or an idea that can help lead to a solution eventually. I also find the solutions to many VBA problems on user forums like this where enough people responding has sometimes led to a resolution. Its not the only avenue for trying to get an answer but it can help.

    Was this answer helpful?

    0 comments No comments
  3. Charles Kenyon 170.9K Reputation points Volunteer Moderator
    2022-09-16T17:00:02+00:00

    Ian and Nicole,

    This is an excellent spot to get some help troubleshooting an issue. However, this is not the place to get any changes made in Word nor the attention of developers at Microsoft. This is an independent user-to-user support forum. MS does not see anything you post here. The way to get their attention is through the feedback mechanisms.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2022-09-16T16:56:03+00:00

    I am experiencing a very similar issue with users at my company. A macro that has been working fine for months is suddenly having issues for only select users. Same runtime error when trying to open a file with the "Documents.Open" method. Fails for both .docm and .txt files.

    In my case though, all users are running the same windows build (according to our tech team.)

    My best hunch has been that the issue is permissions or registry key related.

    Get this: if I run the Documents,Open (or the Dir( )) command in the immediate window it works perfectly, but fails when called from a Sub.

    I hope Microsoft comes back with some answers soon--I'm about at my wit's end with this.

    Was this answer helpful?

    0 comments No comments