"One word" in length Personal Book crashes Verbum every time I build it!

See attached one word docx file - I narrowed down a new PB I created to just one word and it still crashes in Verbum 6.6 SR-3 - WIndows 10 Pro, Word 2016. I tried the trick of maintaining compatibility with prior versions - I tried copying and pasting into a new document - something is broken, any ideas?

3324.Test.zip

Find more posts tagged with

Comments

Don Awalt

Crashes when trying to build on Mac Verbum 6.6 SR-3 as well.

HJ. van der Wal

https://community.logos.com/discussion/comment/775257#Comment_775257

Shalom Don!

I tried to build the book using Logos 6.6 SR-2 (Windows 10).

Logos doesn't crash but the build failed because of an "error while discovering resource":

[Info] Starting build for PBB:ac97f779e3c340408f75731b4e7a1697
[Info] Converting
[Info] Converting C:\Users\H.J\Desktop\Morning Homilies.docx
[Info] Compiling
[Info] Discovering
[Error] Error while building book: Error while discovering resource.
[Error] Exception: LDLS4.Panels.PersonalBookBuilderPanel.PersonalBookBuilderException: Error while discovering resource.
   at LDLS4.Panels.PersonalBookBuilderPanel.PersonalBookConverter.DiscoverResource(String filename, ResourceManager resourceManager, LibraryCatalog libraryCatalog, KeyLinkManager keyLinkManager, IWorkState workState)
   at LDLS4.Panels.PersonalBookBuilderPanel.PersonalBookConverter.<CreatePersonalBookWork>d__c.MoveNext()
   at Libronix.Utility.Threading.AsyncWorkerTask`1.EnumMoveNext()
   at Libronix.Utility.Threading.AsyncWorkerTask`1.EnumMoveNextWithCatch()
   at LDLS4.Panels.PersonalBookBuilderPanel.PersonalBookViewModel.<CreatePersonalBookWork>d__a.MoveNext()

HJ. van der Wal

https://community.logos.com/discussion/comment/775265#Comment_775265

I've succeeded in building the book by adding the words "Morning Homilies" at the start of the Word document:

Don Awalt

https://community.logos.com/discussion/comment/775265#Comment_775265

Thanks for the reply! The difference between my crash in SR-3 and this exception is whether or not the exception is caught and handled - maybe some change occurred in SR-3 that affects this. As you can see below my exception in SR-3 is different. (I did not attach logs as this seems to reproducible, in fact opening Word 2016 in a new document, typing one word, saving, and building a PB crashes too; if anyone needs logs from me let me know).

Error ID: 4958

Error detail: InvalidOperationException: The Writer is closed or in error state.

System.InvalidOperationException: The Writer is closed or in error state.
at System.Xml.XmlWellFormedWriter.AdvanceState(Token token)
at System.Xml.XmlWellFormedWriter.WriteEndElement()
at System.Xml.XmlWellFormedWriter.WriteEndDocument()
at Libronix.Utility.Scope.Dispose()
at LDLS4.Panels.PersonalBookBuilderPanel.ResourceDocumentData.WriteMetadataDocument(XmlWriter writer)
at LDLS4.Panels.PersonalBookBuilderPanel.PersonalBookConverter.CreateResourceDocument(ResourceDocumentData metadata)
at LDLS4.Panels.PersonalBookBuilderPanel.PersonalBookConverter.<CreatePersonalBookWork>d__c.MoveNext()
at Libronix.Utility.Threading.AsyncWorkerTask`1.EnumMoveNext()
at Libronix.Utility.Threading.AsyncWorkerTask`1.EnumMoveNextWithCatch()
at LDLS4.Panels.PersonalBookBuilderPanel.PersonalBookViewModel.<CreatePersonalBookWork>d__a.MoveNext()
at Libronix.Utility.Threading.AsyncWorkerTask`1.EnumMoveNext()

Don Awalt

https://community.logos.com/discussion/comment/775269#Comment_775269

Which version of Word are you using?

HJ. van der Wal

https://community.logos.com/discussion/comment/775271#Comment_775271

Which version of Word are you using?

I'm using LibreOffice 5

Don Awalt

https://community.logos.com/discussion/comment/775273#Comment_775273

Which version of Word are you using?

I'm using LibreOffice 5

That's likely the difference then! Something in Word 2016 is not being handled by Logos/Verbum...

Don Awalt

https://community.logos.com/discussion/comment/775277#Comment_775277

It's not Word 2016! Something is seriously broken. I went to another computer running Windows 10 but with Word 2013. I created a new blank document and typed the word "Test" in it - and got the attached crash. I have no reason to believe I can compile anything with the latest Verbum 6.6 SR-3. Help!

6175.Verbum Log Files.zip

Don Awalt

https://community.logos.com/discussion/comment/775286#Comment_775286

Just tried doing a File Save As in Libre 5.0.2 and rebuilding - immediate crash as before. Something is terribly wrong, this is unuseable now. :-(

Don Awalt

https://community.logos.com/discussion/comment/775340#Comment_775340

Crash happens in 6.7 RC-1 too.

Dave Hooton

I narrowed down a new PB I created to just one word and it still crashes in Verbum 6.6 SR-3 - WIndows 10 Pro, Word 2016. I tried the trick of maintaining compatibility with prior versions - I tried copying and pasting into a new document

I built a docx file with the one word "Contents" and it compiled OK as a monograph. Then I saved your file without maintaining compatibility and it also compiled ok (your file has a "empty arrow head" before the word. When clicked it changes orientation).

Using Word 2016

Don Awalt

https://community.logos.com/discussion/comment/775404#Comment_775404

OK, so I posted my log files - what is wrong? I understand others can compile PBs, I cannot. I posted log files - crashes are really happening. Not sure if anyone believes it. Maybe they don't from the lack of response.

I am sorry, I have spent most of this day trying to find a workaround, and I have gotten little help other than it works for others. It does not work for me. Is there any advice? Can anyone from Faithlife look at this?

I am sorry, I am quite upset - it seems like almost every day a crash, a bug occurs, and it is getting harder and harder to get work done. I am starting to think a software release every 6 weeks is making Verbum buggier and buggier. I know I am just very frustrated from unsupported problems, but I feel very close to just stopping with this product entirely and going with something else much more stable.

Let me know if you can help, if so thanks in advance. If not I'll take the hint.

Error ID: 4958

Error detail: InvalidOperationException: The Writer is closed or in error state.

Don Awalt

https://community.logos.com/discussion/comment/775439#Comment_775439

Verbum crashed .NET runtime too (from event viewer)

Application: Verbum.exe
Framework Version: v4.0.30319
Description: The application requested process termination through System.Environment.FailFast(string message).
Message: Unhandled exception in async work
Stack:
at System.Environment.FailFast(System.String, System.Exception)
at Libronix.Utility.Threading.AsyncWorkerTask`1[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].EnumMoveNext()
at Libronix.Utility.Threading.AsyncWorkerTask`1[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].ContinueExecution(System.Object)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
at System.Windows.Threading.DispatcherOperation.InvokeImpl()
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
at System.Windows.Threading.DispatcherOperation.Invoke()
at System.Windows.Threading.Dispatcher.ProcessQueue()
at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
at MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
at MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32)
at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr)
at MS.Win32.UnsafeNativeMethods.DispatchMessage(System.Windows.Interop.MSG ByRef)
at MS.Win32.UnsafeNativeMethods.DispatchMessage(System.Windows.Interop.MSG ByRef)
at System.Windows.Threading.Dispatcher.PushFrameImpl(System.Windows.Threading.DispatcherFrame)
at System.Windows.Application.RunDispatcher(System.Object)
at System.Windows.Application.RunInternal(System.Windows.Window)
at LDLS4.OurApp.InitializeAndRun(System.Collections.ObjectModel.ReadOnlyCollection`1<System.String>, Libronix.Utility.Threading.SingleInstanceManager)
at LDLS4.OurApp.Main(System.String[])

Don Awalt

https://community.logos.com/discussion/comment/775472#Comment_775472

This happens on two separate Windows 10 computers and one Mac OS X computer, Verbum 6.6 SR-3 and 6.7 RC-1.

Dave Hooton

https://community.logos.com/discussion/comment/775474#Comment_775474

This happens on two separate Windows 10 computers and one Mac OS X computer, Verbum 6.6 SR-3 and 6.7 RC-1.

I indicated how I was able to compile it - and it works in both Verbum and Logos on Win 10. What is the metadata you are using (show a screen shot of the Personal Books tool)?

Don Awalt

https://community.logos.com/discussion/comment/775495#Comment_775495

That was the clue Dave! Thank you!!!!

I deleted the "Description" metadata, and it built! I did some experimentation, and could not find what was bad in the text. I did this by copying it all, pasting in Word, and then using pieces at a time. And then I went back to the web site where I got it from, copied the while thing, and pasted it in, and the crash reappeared!

So what makes it crash is NOT the document - it is this description - go to this site:

http://www.orbisbooks.com/morning-homilies.html

And under the Description tag copy the word "offer" from the word "offers" in the first line of the second paragraph. Paste it into the Description. It will crash. I tried it with Chrome and Edge, and I also did View Source to see if there were any unusual characters in that area and there were not. There could be other words later in the description, I narrowed it down to find the first word that made it crash.

But - if you copy it all and paste into Word (or Notepad, or something else) and then recopy from there it will not. So there is something about what is put on the clipboard (but by two browsers, not just a single browser bug). (Note - I could not get ANYTHING to paste into the Mac description box, from anywhere - it just did not paste - must be a bug I Never do PB development work on the Mac; I'll report it.)

OR - it could be a bug in the Verbum "paste" function? (since it doesn't seem to work on the Mac at all in that description box)?

Jack Caviness

https://community.logos.com/discussion/comment/775530#Comment_775530

Note - I could not get ANYTHING to paste into the Mac description box, from anywhere - it just did not paste - must be a bug I Never do PB development work on the Mac; I'll report it.)

OR - it could be a bug in the Verbum "paste" function? (since it doesn't seem to work on the Mac at all in that description box)?

Logos 6.7 RC-1 Mac OS 10.11.1

Copied a couple of paragraphs from your post. Had no problem pasting into the Description field on 2 different PBs. Is this a Verbum issue?

Dave Hooton

https://community.logos.com/discussion/comment/775530#Comment_775530

And under the Description tag copy the word "offer" from the word "offers" in the first line of the second paragraph. Paste it into the Description.

From Firefox, the whole word pastes into Word as off-ers (regular hyphen) and from Word into this response as off‑ers (not a regular hyphen). When I copy from Firefox it pastes into this response as offers. Anyway, it appears that the PB tool doesn't cope with it.

Randy W. Sims

https://community.logos.com/discussion/comment/775540#Comment_775540

It's an ASCII control character, the record separator (0x1E). It will show it if you copy the text from html source into notepad++.

NB.Mick

https://community.logos.com/discussion/comment/775548#Comment_775548

Wow, master sleuthing going on!

Hope Faithlife fixes this issue.

Dave Hooton

https://community.logos.com/discussion/comment/775638#Comment_775638

Wow, master sleuthing going on!

The Sherlock Holmes precept that "when you have eliminated the impossible, whatever remains, however improbable, must be the truth"...

Dylan Rondeau

https://community.logos.com/discussion/comment/775762#Comment_775762

There is a case for this issue. Thanks all for your work in narrowing it down to the illegal character in the description!

Don Awalt

https://community.logos.com/discussion/comment/775939#Comment_775939

Squash it Dylan! [:)]