A family of Microsoft word processing software products for creating web, email, and print documents.
Great news. The 2302 patch just came out, tested it on a couple computers here and the InsertFile function is now working properly.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
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.
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
A family of Microsoft word processing software products for creating web, email, and print documents.
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.
Great news. The 2302 patch just came out, tested it on a couple computers here and the InsertFile function is now working properly.
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.
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.
Yep, we just crossed paths with that last test. See my response above (just posted that as yours came in), I just tried that but found that if I closed everything between tests and reopened the test doc containing the macro from scratch every test it went back to failing even after using the Info screen conversion. I actually live about a half mile from MSFT campus in Redmond. My wife works for Microsoft and she's up in the mountains picking huckleberries today and my neighbor works for Microsoft and I was giving him waterski lessons this morning between rounds of debugging this problem.
Hi Doug,
Yep, still fails. I took the failing ExecSummaryA.docx and using Words toolbar Save As ExecSummaryC.doc (2003-2007 format .doc file) and closed the document. Then opened the ExecSummaryC.doc and did a Save As ExecSummaryC2.docx (back to current format Word document).
Then ran the test insert script 3 times.
ExecSummaryA.docx fails, ExecSummaryC.doc works, ExecSummaryC2.docx fails.
I also opened the ExecSummaryC.doc file, then the Info screen and converted the document to the current format before doing the Save As ExecSummaryC3.docx
That file also fails the same as if just doing a Save As without converting it.
But I did notice that I had to close all the files between test runs including the document containing the macro. There were some times when something worked that normally was failing and I thought I was onto something. But I was just closing the CoverLetter.docx after the failed test, changing the code and rerunning the script to import a different file without closing the macro enabled document. Once I started closing everything between tests it went back to consistently failing on every variation of the .docx files.