PB Build Failed and then Verbum CRASH Building OT PB-Denver Seminary file

Don Awalt
Don Awalt Member Posts: 3,521 ✭✭✭
in Beta Desktop App Forum

I just went to build the new file for PB-Seminary Annotated Bios....

https://community.logos.com/forums/p/63727/1299284.aspx#1299284

and the build failed with this:

[Info] Starting build for PBB:647430bbb85448bc9c81382e5fb47763
[Error] Error while building book: Could not remove existing book. Please close all other open panels and try again.
[Error] Exception: LDLS4.Panels.PersonalBookBuilderPanel.PersonalBookBuilderException: Could not remove existing book. Please close all other open panels and try again.
at LDLS4.Panels.PersonalBookBuilderPanel.PersonalBookConverter.CreatePersonalBookWork(PersonalBook book, PersonalBookBuilderViewModel model, PersonalBookViewModel bookViewModel, IPersonalBookBuildLog buildLog)+MoveNext() in /Volumes/Code/ghe_actions-2.301.1/Logos/_work/LogosDesktop/LogosDesktop/src/LDLS4/Panels/PersonalBookBuilderPanel/PersonalBookConverter.cs:line 113
at Libronix.Utility.Threading.AsyncWorkerTask`1[[Libronix.Utility.VoidType, Libronix.Utility, Version=17.10.2.0, Culture=neutral, PublicKeyToken=null]].EnumMoveNext()
at Libronix.Utility.Threading.AsyncWorkerTask`1[[Libronix.Utility.VoidType, Libronix.Utility, Version=17.10.2.0, Culture=neutral, PublicKeyToken=null]].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() in /Volumes/Code/ghe_actions-2.301.1/Logos/_work/LogosDesktop/LogosDesktop/src/LDLS4/Panels/PersonalBookBuilderPanel/PersonalBookViewModel.cs:line 727

Then I clicked to add file to the NT version, and Verbum exited - it crashed per the Console app on the Mac.

I inadvertently opened the OT book before I built it - but I closed it - but that bug has been around forever, that something is left open. But ow instead of a fail there is more on both the build error message, and it crashes all of Verbum.

Attached are logs before I restarted; after I got the logs, I reopened Verbum, and both built fine:

8272.Archive.zip

Comments

  • MJ. Smith
    MJ. Smith MVP Posts: 53,386

    weekly bump of unanswered posts hoping to get a response

    Orthodox Bishop Alfeyev: "To be a theologian means to have experience of a personal encounter with God through prayer and worship."; Orthodox proverb: "We know where the Church is, we do not know where it is not."

  • Savanna Lineberger
    Savanna Lineberger Member, Community Manager, Logos Employee Posts: 766

    Thanks Don. I haven't been able to reproduce just yet, but will keep taking a look at this.

  • Tim Hensler
    Tim Hensler Member Posts: 1,532 ✭✭✭
    https://community.logos.com/discussion/comment/1300294#Comment_1300294

    Savanna Lineberger said:

    will keep taking a look at this

    Hi Savanna.

    Please, look through the forums for posts on the PB Build failures.  There are many, reported for years.  A common error message includes, "while building book: Could not remove existing book. Please close all other open panels and try again."  Even after closing everything, it will still fail and the only way to overcome the problem is to close and re-launch Logos.  

    I build my own Bible translation as part of my study/teaching workflow.  There are times when I add a passage to my PB Bible and while studying I need to make updates to the text and rebuild the PB Bible. This often happen multiple times as I work though a passage. The build failure happens well over 50% of the time.  Sometimes over 80% of the time.

    I have reported the problem many times, included many logs, and even sent copies of my DOCX files. Other users have done the same thing.  Yet, year after year, version after version, the problem is not fixed and no news provided about the situation - it feels like the problem is being ignored.  

    If this problem has a low priority because its not used very much, maybe if it worked better the usage would increase.  It will never be a top-used tool, but it is so important and strategic for those of us who not only use it, but rely on it because of it's importance to our workflow.

    Please, can we have someone research the history of this problem and take a serious look at the tool?  I, and others, would really appreciate it.

  • MJ. Smith
    MJ. Smith MVP Posts: 53,386
    https://community.logos.com/discussion/comment/1300294#Comment_1300294

    Savanna Lineberger said:

    Thanks Don. I haven't been able to reproduce just yet, but will keep taking a look at this.

    Savanna, this problem was once corrected but later snuck back in. At that time we were told that the basic problem was that the a file was not properly released so it could not be opened when one tried to compile again.

    Orthodox Bishop Alfeyev: "To be a theologian means to have experience of a personal encounter with God through prayer and worship."; Orthodox proverb: "We know where the Church is, we do not know where it is not."

  • Savanna Lineberger
    Savanna Lineberger Member, Community Manager, Logos Employee Posts: 766

    I apologize for the confusion, I meant to indicate I was specifically looking into the crash you were experiencing in this situation. The failure issue we have an open case for, but the crash appears to be a new issue. I will report back here when I have an update on either of the two problems being encountered. 

  • Tim Hensler
    Tim Hensler Member Posts: 1,532 ✭✭✭

    Hi @Savanna Lineberger,

    The crash problem for building Personal Books either has dozens of cases on it or one HUGH case where all the reports for this problem have been joined. Literally, this crash problem has been around for at least 10 years (I saw a report on this dated 2014!) and has been reported periodically by me and other users during that time.

    PLEASE, either have someone mine both the Logos and Verbum English forum and the Logos and Verbum Beta forum for reports of the Persona Book Builder. If you don't have someone who can do that, please let me know and I'll do it. Among the reports you'll find a LOT of log files included. In addition, I emailed DOCX and log files to people at Faithlife who requested them on at least two times.

    If the problem is on my end (corrupt file or …) I need to know so I can fix it. If it is a but, I really need it fixed.

    ►This seriously hampers my Bible study workflow.

    FYI, I create my own translation as part of my studies. As I do that, I often build the work I have done and as I review it and continue to translate, I rebuild it to make sure I have no XML errors and my formatting is as I want it. I used be able to close all windows in Logos, launch the PB Builder and it would one two or three times out of five tries. When it failed I had to re-launch the Logos app.

    For well over a month now, when I want to build a PB Bible, I always have to re-launch the Logos app to a blank layout or to a layout with only the PB Builder open. If the PB book is open in Logos, even if I close it, the PB Builder will fail.

    What can I do to help move this issue forward to a solution?

  • MJ. Smith
    MJ. Smith MVP Posts: 53,386

    Tim, they fixed it once and it broke again quite quickly. I suspect that the actual solution is sufficiently complex that we are unlikely to see this fixed anytime in the current development schedule which I suspect is kept in pencil about a year out.

    Orthodox Bishop Alfeyev: "To be a theologian means to have experience of a personal encounter with God through prayer and worship."; Orthodox proverb: "We know where the Church is, we do not know where it is not."

  • Tim Hensler
    Tim Hensler Member Posts: 1,532 ✭✭✭

    Hi @MJ. Smith. Yes, I remember when they tried to fix it, only for it to digress in performance later. Unfortunately I think you're probably right regarding its future. I am frustrated that Faithlife has not indicated any interest, let alone effort, to resolve this problem. I think this is a powerful tool that could be a great help to the people who invest the most in Logos (Pro & Max subscribers). It is so frustrating to use, that over the years I gave up a few times, only to return to the frustration because there is no substitute for it. At this point, with the advancement in programing options, they probably need to start from scratch and make a better mouse trap, so to speak, rather than try to fix the old one. A bigger project than they seem to be willing to tackle. 😒

Categories