Personal Book Builder Broken
The personal book builder tool for Logos 10 doesn't seem to like the latest MS Word 365 *.docx files. I've tried several iterations of file, all the way down to a blank document with just three words in it, with no formatting, and I get the same error: the file "is not a valid Word document." The log file says basically the same thing. I also tried one of my previously successful personal books from a year ago, and it gives the same error, so it can't be a problem with the Word document format since it was working on the previous version of Logos. Any ideas?
I tried attaching a copy of the log in case that would help, but the attachment tool only seems to work for media.
The file output is shown below:
[Info] Starting build for PBB:a0045d8c445246a997609a54b39090cc
[Info] Converting
[Info] Converting S:\My Stuff\Christian Stuff\eBooks\Logos\Done\LSV_TitlePageBasic.docx
[Error] Error while building book: The file S:\My Stuff\Christian Stuff\eBooks\Logos\Done\LSV_TitlePageBasic.docx is not a valid Word document.
[Error] Exception: LDLS4.Panels.PersonalBookBuilderPanel.PersonalBookBuilderException: The file S:\My Stuff\Christian Stuff\eBooks\Logos\Done\LSV_TitlePageBasic.docx is not a valid Word document.
---> Ionic.Zip.ZipException: Cannot read that as a ZipFile
---> System.ArgumentException: 'IBM437' is not a supported encoding name. For information on defining a custom encoding, see the documentation for the Encoding.RegisterProvider method. (Parameter 'name')
at System.Text.EncodingTable.InternalGetCodePageFromName(String name)
at System.Text.EncodingTable.GetCodePageFromName(String name)
at System.Text.Encoding.GetEncoding(String name)
at Ionic.Zip.ZipEntry..ctor()
at Ionic.Zip.ZipEntry.ReadDirEntry(ZipFile zf, Dictionary`2 previouslySeen)
at Ionic.Zip.ZipFile.ReadCentralDirectory(ZipFile zf)
at Ionic.Zip.ZipFile.ReadIntoInstance(ZipFile zf)
--- End of inner exception stack trace ---
at Ionic.Zip.ZipFile.ReadIntoInstance(ZipFile zf)
at Ionic.Zip.ZipFile.Read(Stream zipStream, TextWriter statusMessageWriter, Encoding encoding, EventHandler`1 readProgress)
at Ionic.Zip.ZipFile.Read(Stream zipStream)
at LDLS4.Panels.PersonalBookBuilderPanel.OfficeOpen.Package.OpenXmlFile.Open(String filename)
at LDLS4.Panels.PersonalBookBuilderPanel.PersonalBookConverter.ConvertOpenXmlDocumentToLogosXml(PersonalBookConverterCallback converterCallback, String resourceType, IEnumerable`1 filenames, TempFiles tempFiles, ResourceDocumentData data, PersonalBookArticleCache articleCache, IPersonalBookBuildLog buildLog, IWorkState workState)
--- End of inner exception stack trace ---
at LDLS4.Panels.PersonalBookBuilderPanel.PersonalBookConverter.ConvertOpenXmlDocumentToLogosXml(PersonalBookConverterCallback converterCallback, String resourceType, IEnumerable`1 filenames, TempFiles tempFiles, ResourceDocumentData data, PersonalBookArticleCache articleCache, IPersonalBookBuildLog buildLog, IWorkState workState)
at LDLS4.Panels.PersonalBookBuilderPanel.PersonalBookConverter.CreatePersonalBookWork(PersonalBook book, PersonalBookBuilderViewModel model, PersonalBookViewModel bookViewModel, IPersonalBookBuildLog buildLog)+MoveNext()
at Libronix.Utility.Threading.AsyncWorkerTask`1.EnumMoveNext()
at Libronix.Utility.Threading.AsyncWorkerTask`1.EnumMoveNextWithCatch()
--- End of stack trace from previous location ---
at Libronix.Utility.Threading.AsyncWorkItem.Verify()
at LDLS4.Panels.PersonalBookBuilderPanel.PersonalBookViewModel.CreatePersonalBookWork(PersonalBook book, PersonalBookBuilderViewModel bookBuilderViewModel, PersonalBookViewModel bookViewModel)+MoveNext()
Thanks in advance!
Govi Hines
Comments
-
I am running L10 on macOS 13 (beta) and was able to successfully build a book using an old .docx file. I updated Word, made a quick change to the file, and rebuilt the book also without issue.
the attachment tool only seems to work for media.
You need to use the paperclip icon.
0 -
Hi JT,
I'm using Windows (don't get me started... ;-) ), so it probably only affects Windows Logos users. I guess we'll see if anyone else is having the same issue.
The paperclip icon is the tool that I used to attach the log, but it is for media only. When I tried it anyway, it just pasted in an inline link which doesn't go anywhere (I tried, but it's a dead link).
Thanks for you help!
Govi
0 -
Hi Govi,
I am running Windows and also have the same problem building PBs using .docx files from Word 365. These files worked in L9 three days ago, but are now being flagged as "not a valid Word document".
0 -
-
Hi JT,
I'm running Microsoft Windows 10 Home (version 10.0.19044 Build 19044) and Microsoft Word for Microsoft 365 MSO (version 2209 Build 16.0.15629.20152) 64-bit.
Logos version 10.0.0.0215
Attached is the log file from the failed PB build.5482.PBB_8d9487c56af74162911c54ed2e22b04e_2022-10-13T13_08_17Z.log
Please let me know if you can see the log file that I've attached.
Thanks
0 -
I am running Windows 10
I create PB to preach and I just tested updating one document and had no problems. But I have not yet tested creating a new PB. I am following this thread because it is of great importance to me that I can continue creating my sermons using PB.
0 -
I'm running Microsoft Windows 10 Home (version 10.0.19044 Build 19044) and Microsoft Word for Microsoft 365 MSO (version 2209 Build 16.0.15629.20152) 64-bit. (...) Please let me know if you can see the log file that I've attached.
not JT, but yes, your log is there. It says the same as the OP's copied text: the PB compiler can't unpack the XML portion of the word file, the ZIP routine missing a code page.
Someone who has this error could upload a file here for others to test - I'm not sure whether Office 365 makes an error writing the file or whether Windows or .NET or what else should supply the respective information and it is only lacking on your PC. I had no issues so far building any PBs under Verbum 10, but I use an old Word version or files from the forum.
Have joy in the Lord!
0 -
This workaround is worth a try. Install LibreOffice on your computer (it's free), open the docx file with LibreOffice Writer and make a meaningless change to it. Then save the file in docx format and try to build the book again.
0 -
Thanks for the report. We have created a case to fix this problem.
If you were able to provide an example document that demonstrates the problem, then it will help in confirming our fix.
Andrew Batishko | Logos software developer
0 -
Hi Andrew,
Attached is a Microsoft 365 Word file that fails the PB building process...
Thanks
0 -
Hi Andrew,
I've attached the basic document that I tried last, which was a clean, new Word document with only three, unformatted words in it.
Not sure if the attachment options is working, since I had trouble with the original post, but I can forward to you by e-mail if this doesn't work.
The document I was trying to load originally was the Literal Standard Version from lsvbible.com.
Just for completeness, my current Windows version is 10.0.22000 Build 22000, and Word 365 version 2209 Build 15629.20156 Click-to-Run.
Thanks for your help!
Govi Hines
0 -
The paperclip icon is the tool that I used to attach the log, but it is for media only. When I tried it anyway, it just pasted in an inline link which doesn't go anywhere (I tried, but it's a dead link).
While trying to troubleshoot your issue I discovered a different bug. When I went to post logs, it dawned on me perhaps what you meant. When you are posting the logs, it will appear that there is a dead link... but when you finish the post, there will be an active link.
Here is my log file:
5127.LogosLogs.20221013-203040.zip
Here is what it looks like before I finish posting it:
0 -
I've attached the basic document that I tried last, which was a clean, new Word document with only three, unformatted words in it.
These two lines of text failed to build with 2 errors in Word v.2209:
And it failed when I added a few more lines with formatting.
Dave
===Windows 11 & Android 13
0 -
Hi Andrew,
Attached is a Microsoft 365 Word file that fails the PB building process...
I had no problem building this in Word 365 version 2209
Dave
===Windows 11 & Android 13
0 -
Hi Andrew,
I've attached the basic document that I tried last, which was a clean, new Word document with only three, unformatted words in it.
Could it be that this document has been saved as a "Strict Open XML-Dokument (.docx)" file? This format is apparently NOT the same as a "Word Document (docx)" file, and therefore the PBB tool would not recognize it as a correct Word docx) file??
I do not have Word 365, but opened the file in Word 2019 and when using "Save as" I noticed that it wanted to save the file as a "XML-Document" rather than a "Word Document" ... after saving it as Word docx file, the PBB was built correctly.
Wolfgang Schneider
(BibelCenter)
0 -
Hi Andrew,
Attached is a Microsoft 365 Word file that fails the PB building process...
Thanks
not for me, built great with 0 errors, 0 warnings - EDIT: I did not open and save this in Word, just pointed the PB tool to the downloaded file and let it run.
Have joy in the Lord!
0 -
Hi Andrew,
I've attached the basic document that I tried last, which was a clean, new Word document with only three, unformatted words in it.
Could it be that this document has been saved as a "Strict Open XML-Dokument (.docx)" file? This format is apparently NOT the same as a "Word Document (docx)" file, and therefore the PBB tool would not recognize it as a correct Word docx) file??
I do not have Word 365, but opened the file in Word 2019 and when using "Save as" I noticed that it wanted to save the file as a "XML-Document" rather than a "Word Document" ... after saving it as Word docx file, the PBB was built correctly.
definitely, the document is in the wrong format:
Have joy in the Lord!
0 -
I've attached the basic document that I tried last, which was a clean, new Word document with only three, unformatted words in it.
This failed for me with a different error than the one listed in your original post. Is that the case for you too? I'd like to recreate the original error if possible.
Andrew Batishko | Logos software developer
0 -
Sorry, I sent the wrong file. Here is the one that is a plain Word 365 document. The one I sent was a last ditch effort to try the other format, but it failed also. Sorry for the confusion.
I should also point out that the error I'm getting is the same for every version of document I've tried. This computer is less than 2 months old and all the software has only recently been installed, so everything should be working properly, especially since version 9 was working. All the latest updates have also been installed for everything.
I appreciate all the tips and comments!
2843.LSV_TitlePageBasicOriginal.docx
Govi
0 -
Thanks! I tested this with the fix that we have in place for 10.1 Beta 1, and it appears to compile correctly.
Andrew Batishko | Logos software developer
0 -
Thanks! I tested this with the fix that we have in place for 10.1 Beta 1, and it appears to compile correctly.
That's really awesome! I've been on here plenty in the past, but never posted a request before. I'm definitely impressed with how quickly the community offered suggestions and how quickly tech support responded with a solution. E-hugs to everyone (hopefully that's not creepy)!
Govi
0 -
Hmn ... this time the file being a Word docx file worked for me without any errors.
Seeing that the content of this Word docx file was the same as the other Strict Open XML docx file before, the problem would seem to have been the wrong file format. That actually would be expected behavior, because the PBB tool is said to currently only work with Word docx format files.
Wolfgang Schneider
(BibelCenter)
0 -
Thanks! I tested this with the fix that we have in place for 10.1 Beta 1, and it appears to compile correctly.
Andrew - what was the problem? I haven't had any problems since upgrading - just to double check I just got one of my existing docs and made a change and recompiled which it did just fine. If it is fixed then great but is there something we should avoid doing in our documents?
Scripture set to music for worship and aid memorization. https://www.youtube.com/channel/UC-DojPa0TlpCGhtUJq1e3Pw
0 -
One of the third party libraries we use dropped default support for the encoding that you were using (the IBM437 mentioned in your error message).
Andrew Batishko | Logos software developer
0 -
I am getting the exact same issue as Govi Hines, verbatim, on any and all build attempts. I have previously imported dozens of books/documents, and am used to working through various errors. I have dumbed the file down, removed metadata, back saved as .doc and then loaded as .docx. ...always get the exact same message - 2 errors, this is NOT a valid Word document.
I am running Windows 10.0.19044. There is a pending security reboot that I have not exercised. Will try that next.
When is the 10.1 beta due out, or can we sync to that if we are having problems? or is there a workaround to switch to another encoder?
0 -
As a second follow up to the fix Andrew mentions, the latest update for 10.0 SR-2 seems to have fixed the problem. I can now compile the original file as needed. Thanks again!
Thanks! I tested this with the fix that we have in place for 10.1 Beta 1, and it appears to compile correctly.
Govi
0
