Personal book Build failed

For the first time ever I received this message the following message and log errors while trying to build a personal book. I can open the file in Word without problem. Can anyone help me? I hate to ask ANYONE to look at log files...

[Info] Starting build for PBB:11f28bc4d6c242d9a7edab9dfa3b71f7
[Info] Converting
[Info] Converting /Users/drmarkellis/Dropbox/NIV/LOGOS/Nova Versão Internacional.docx
[Warning] Field off for field bible with no field on
[Warning] Unrecognized field bible}“Ai
[Error] Error while building book: Error while reading document.
[Error] Exception: LDLS4.Panels.PersonalBookBuilderPanel.PersonalBookBuilderException: Error while reading document. ---> System.InvalidOperationException: Operation is not valid due to the current state of the object
at Libronix.Utility.XmlUtility.Wrap (Libronix.Utility.XTextRun text, Int32 index, Int32 length, System.Func`2 createReplacementNode) [0x00000] in <filename unknown>:0
at LDLS4.Panels.PersonalBookBuilderPanel.OfficeOpen.Converter.LogosUserTags.StripUserTagsFromToc (System.Xml.Linq.XElement tocEntry, IWorkState workState) [0x00000] in <filename unknown>:0
at LDLS4.Panels.PersonalBookBuilderPanel.OfficeOpen.Converter.ConvertToLogosXml.PostProcessTocEntry (Libronix.Globalization.Culture culture, System.Xml.XmlReader reader, System.Xml.XmlWriter writer, LDLS4.Panels.PersonalBookBuilderPanel.OfficeOpen.Converter.LogosUserTags logosUserTags, LDLS4.Panels.PersonalBookBuilderPanel.OfficeOpen.Converter.SermonFile.SermonFileProcessor sermonFileProcessor, LDLS4.Panels.PersonalBookBuilderPanel.OfficeOpen.Converter.ParallelPassages.ParallelPassagesProcessor parallelPassagesProcessor, IWorkState workState) [0x00000] in <filename unknown>:0
at LDLS4.Panels.PersonalBookBuilderPanel.OfficeOpen.Converter.ConvertToLogosXml.PostProcess (IPersonalBookConverterCallback converterCallback, Libronix.Globalization.Culture culture, LDLS4.Panels.PersonalBookBuilderPanel.OfficeOpen.Converter.DocumentSettings settings, System.Xml.XmlReader reader, System.Xml.XmlWriter writer, System.Collections.Generic.List`1 sermonFileMetadatas, IPersonalBookBuildLog buildLog, System.Collections.Generic.List`1 uniqueUserInputIdentifiers, LDLS4.Panels.PersonalBookBuilderPanel.OfficeOpen.Converter.ParallelPassages.ParallelPassagesProcessor parallelPassagesProcessor, IWorkState workState) [0x00000] in <filename unknown>:0
at LDLS4.Panels.PersonalBookBuilderPanel.PersonalBookConverter.ConvertOpenXmlDocumentToLogosXml (LDLS4.Panels.PersonalBookBuilderPanel.PersonalBookConverterCallback converterCallback, System.String resourceType, IEnumerable`1 filenames, LDLS4.Panels.PersonalBookBuilderPanel.TempFiles tempFiles, LDLS4.Panels.PersonalBookBuilderPanel.ResourceDocumentData data, Libronix.DigitalLibrary.PersonalBookArticleCache articleCache, IPersonalBookBuildLog buildLog, IWorkState workState) [0x00000] in <filename unknown>:0
--- End of inner exception stack trace ---
at Libronix.Utility.Threading.AsyncWorkItem.Verify () [0x00000] in <filename unknown>:0
at LDLS4.Panels.PersonalBookBuilderPanel.PersonalBookViewModel+<CreatePersonalBookWork>c__Iterator4F.MoveNext () [0x00000] in <filename unknown>:0

Find more posts tagged with

Comments

JT (alabama24)

Have you restarted your computer?

David Ames

As you did get:

[Warning] Field off for field bible with no field on
[Warning] Unrecognized field bible}“Ai

Maybe look for single { } [ ] where you want doubles {{ }} [[ ]]

Maybe just before the letters 'Ai'

Mark A. Ellis

https://community.logos.com/discussion/comment/513174#Comment_513174

Hi, David. Thanks for the clues on that. I've been looking for what what was producing that warning for weeks. I'll check it out.

Mark A. Ellis

https://community.logos.com/discussion/comment/513173#Comment_513173

Hi, Alabama24

Thanks for the suggestion, but it did not resolve the problem.

Mark Barnes

https://community.logos.com/discussion/comment/513450#Comment_513450

I've never seen this problem before, and if you're not responsible for the code, understanding stack traces is pretty tough. But, my guess would be that there's a problem with a heading in your Word document. Specifically, it would seem that one of your headings includes a Logos tag (i.e. something inside [[ ]], or perhaps { }). It also seems that there is something wrong with this tag.

So, I would follow David Ames' advice, but I would look for the problem specifically in headings, rather than the body text. To do this quickly, use Word's outline view, and make sure that Show Level is not set to All levels.

If you find the problem, do let us know, because Logos might want to fix it so that error doesn't stop a document from compiling.

Don Awalt

https://community.logos.com/discussion/comment/513454#Comment_513454

I would also suggest to make a copy of your PB source file in Word that you can play with - keep dividing the document in half roughly, and see which half causes the problem. By dividing in half repeatedly, you will quickly narrow down to the offending text, and you can either re-enter recreate the line, or better report what construct specifically causes the error. You should be able to delete the line of offending text and see the book compile without error. If at any time both halves left cause an error, just pick one and continue - you have multiple errors in that case, and finding one will make it easier to find all.

Bradley Grainger (Logos)

If you don't mind sharing the source file with us, you could email the docx file that causes the problem to logos4feedback@logos.com (referencing this thread).

We should then be able to reproduce and fix the problem.

Mark A. Ellis

https://community.logos.com/discussion/comment/513507#Comment_513507

Hi, Bradley,

Thank you, thank you, thank you for such a generous invitation! Following the advice of one of the other guys, however, I succeeded in localizing the header which was causing the problem.

I'm very excited about this project. Here in Brazil, our options are 1) versions based on João Almeida de Ferreira--the equivalent to the KJV and NKJV, 2) Linguagem de Hoje, similar to the Living Bible, and 3) the Brazilian version of the NIV, the "NVI". The first two are available on Logos, the third is not, and most younger Christians and scholars gravitate to the NVI. Unfortunately, the NVI is not available on Logos, and the holder of the copyright, the International Bible Society, shows no interest in making it available. *Fortunately*, I am good friends with two people who were on the translation committee, Luiz Sayão and Carlos Oswaldo Pinto, and they are trying to open doors for me to take this file to the IBS and persuade them to offer it through Logos. I now have all books, chapter and verses tagged, and am in the process for formatting the poetic literature and inserting headings.

When I get it done, I hope I could send you all the file and have you look it over.

All the best,

Mark A. Ellis

https://community.logos.com/discussion/comment/513457#Comment_513457

Hi, Don

Thank you for your suggestion! I kept dividing away until I arrived at the headers for Romans 11. The file is now functioning just fine. So grateful for your advice1

Sincerely,

Mark A. Ellis

https://community.logos.com/discussion/comment/513454#Comment_513454

Hi, Mark

You were spot on! The problem was the header for Romans 11. There is something very fitting in Romans 11 giving me fits.

Gratefully,

Mark A. Ellis

Mark Barnes

https://community.logos.com/discussion/comment/513589#Comment_513589

You were spot on! The problem was the header for Romans 11.

I'm glad you found it. Do you remember what the old header was? Bradley might be able to adjust the code so similar headers produced warnings rather than fatal errors. Other users might find that helpful in the future.

JT (alabama24)

https://community.logos.com/discussion/comment/513587#Comment_513587

When I get it done, I hope I could send you all the file and have you look it over.

Do you have a copy of the portion that was causing you troubles? It might be beneficial to send Logos a small portion with the trouble spot so that they can figure out how to make sure others don't experience the same issue as you did.