PB tool always crashes on 2nd try of re-Build the resource
I've been making PB's for a couple of years now...so I'm not sure what is going on. I've been getting errors consistently since recently, where the first build is fine...I look for errors (I was surprised that Mt 5:2,3 doesn't work as a nice clean reference...but hey, that's just me.) fix them, click build and it always halts with the pesky error: Couldn't remove existing book.....
My source library is not on a Drive/Dropbox/Gdrive. I would sometimes get this before when it was. So I would have to wait for the sync to be done and then the rebuild would actually work.
Closing all panels doesn't help. Only restarting Logos. Which is so annoying. Not to mention the unnecessary sync before closing and opening. As it can easily sync once it opens the app.
Using: Logos Bible Software 25.2.56 on Win 11
Anyone else having the same problems?
Comments
-
Yes, it does and has for years. There have been attempts to fix the problem but it always slips back in. If you close and reopen the application, the problem will be resolved and you can compile it 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."
0 -
Haha, thx...cause I know there was a period when it didn't ;-)
0 -
Just a rant here...can't believe how low life this PB tool is. You can basically only build once, after fixing errors only Logos restart helps.
0 -
Just a rant here...can't believe how low life this PB tool is. You can basicaly on
0 -
I'm only here to support you to get the fix.
Logos we need this fix, plus the others I reported regarding PB issues.
Χριστὸς ἐν ὑμῖν, ἡ ἐλπὶς τῆς δόξης·
0 -
-
The PB tool is on life support.
It's ironic in a way, the threads about "What do you want to see...", surveys etc., and yet a feature like this that people have been SCREAMING for improvements in for YEARS, gets ignored. It's another feature that I add to my list that I only use out of necessity any more since it's so broken. And I have 331 of my own personal books.
0 -
-
I like the tool and wish for it to be improved, have mobile sync, etc. It just doesn’t make business sense for Logos.
I don't know about that attitude.... if we use it to the fullest... Logos is going to be a very simple bible program. I hope Logos is not thinking that way. I can understand putting some things back until they get all the "good stuff" working... but without the "frills" Logos will loose customers in the long run. And the longer the run, the more "frills" Logos will have to have. Just look at the work being done with Search...
xn = Christan man=man -- Acts 11:26 "....and the disciples were first called Christians in Antioch".
Barney Fife is my hero! He only uses an abacus with 14 rows!
0 -
I like the tool and wish for it to be improved, have mobile sync, etc. It just doesn’t make business sense for Logos.
I don't know about that attitude.... if we use it to the fullest... Logos is going to be a very simple bible program. I hope Logos is not thinking that way. I can understand putting some things back until they get all the "good stuff" working... but without the "frills" Logos will loose customers in the long run. And the longer the run, the more "frills" Logos will have to have. Just look at the work being done with Search...
You lost me.
For God and For Neighbor
0 -
It just doesn’t make business sense for Logos.
Oh I disagree. Putting our own resources in enhances the functionality of the features already in Logos. why go to all the trouble of allowing me to enter my hard-copy library, and not enhance this? They seem very similar - I have actually had PBs that the Logos version finally came out for, and since I liked the book I bought the Logos one and retired the PB since I wanted the new Logos functionality in the resource. How does spending tons of time revamping the UI, importing past sermons, or improving any of the tools make any more business sense? They are all features that if enhanced/improved make the user experience better and richer - none directly sell a new book.
People like personal books - they use them - it keeps them in Logos and not in Kindle. Why not enhance it instead of building a bunch of features that 1% of the audience will use.
0 -
It just doesn’t make business sense for Logos.
They are essential until Logos greatly expands its lectionary/sanctoral support ... which would be much more expensive to maintain.
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."
0 -
It just doesn’t make business sense for Logos.
Oh I disagree. Putting our own resources in enhances the functionality of the features already in Logos. why go to all the trouble of allowing me to enter my hard-copy library, and not enhance this? They seem very similar - I have actually had PBs that the Logos version finally came out for, and since I liked the book I bought the Logos one and retired the PB since I wanted the new Logos functionality in the resource. How does spending tons of time revamping the UI, importing past sermons, or improving any of the tools make any more business sense? They are all features that if enhanced/improved make the user experience better and richer - none directly sell a new book.
People like personal books - they use them - it keeps them in Logos and not in Kindle. Why not enhance it instead of building a bunch of features that 1% of the audience will use.
I'm with Don here. PBs are especially a good way to lure and keep users in that are underserviced by the current Logos library (thinking of RM people or languages other than English and Spanish right now). My experience is that PBs help to create the userbase needed for Logos to later go into that specific community - and most of those users will rebuy PBs in Logos editions, should Logos ever produce them.
Have joy in the Lord!
0 -
Logos knows how the tool is being used. When the announcement was made that they would stop developing it, they stated that the majority of personal books were not "personal" at all, but instead multiple copies of 1) public domain books, many of which FL offers themselves and 2) copyrighted material from other sources.
#1 means that people aren't buying the sources from FL.
#2 could be a legal liability for FL
Outside of those issues, there is an actual cost to FL to keep these resources on their servers (when uploaded... and the metadata for all others) which FL is not remunerated for.
0 -
Logos knows how the tool is being used. When the announcement was made that they would stop developing it, they stated that the majority of personal books were not "personal" at all, but instead multiple copies of 1) public domain books, many of which FL offers themselves and 2) copyrighted material from other sources.
#1 means that people aren't buying the sources from FL.I wonder if this still holds true in the same way it may have been the case years ago. Since then, more books have become available in Logos which were not available earlier, and - as various users indicated - once available they did buy the Logos editions in order to get more Logos functionality.
[quote]
#2 could be a legal liability for FL
Not sure if this holds actually true, since Logos is not (mis)using the tool, but the user would be the culprit. Actually, there may be other tools in Logos which a user could utilize to produce documents or materials in which copyright violations may be present.
[quote]
Outside of those issues, there is an actual cost to FL to keep these resources on their servers (when uploaded... and the metadata for all others)which FL is not remunerated for.
What's the difference in cost to Logos for keeping such an uploaded document resource on their server and keeping other kinds of documents on their server? In all cases we have documents produced by a tool available inside Logos software ... in other words, the tool was initially paid for as being part of the software, and the cost for storing any documents produced with these tools on Logos servers was already calculated into the price of the initial Logos software product purchased.
If the problem is storing copyright violating documents possibly causing legal liability, then one must consider that other kinds of documents could also contain copyright violations ... with possibly far reaching consequences such as doing away with a central storage of documents and resources on Logos servers and making the user responsible to have his/her documents solely stored on their local computer or own private cloud solution. I would hope that the copyright concerns of Logos liability for user caused violations are actually are in reality not as valid as it is made to look.
And I would be in favor of dealing with the PBB tool in the same manner as with other tools in regards to further development.
Wolfgang Schneider
(BibelCenter)
0 -
2) copyrighted material from other sources.
#2 could be a legal liability for FL
So if the tool vendor (Logos) has legal liability for how users uses Personal Books in an illegal manner, how is that different than me using Logos to extract text form copyrighted materials, creating my own Word document, and publishing/selling it as my own work? Or creating my own Alas for sale using pictures from one of the copyrighted Atlases in Logos? I couldn't do either of those things without Logos. It seems to me that there are 100 ways to use any software product illegally, if that was a serious concern there wouldn't be much software around. It seems to me similar arguments were made to Bob when he announced this new lack of support for PBs years ago.
0 -
At this point I would be ok if it only worked without restarting ;-)
I never upload my PB's since they can't be used on Mobile...not to mention that I woulnd't mind if they killed the upload (if storage or copyright is a concern) and have some sort of local wifi sync :-)
Maybe in L15. [<:o)]
0 -
I never upload my PB's since they can't be used on Mobile...not to mention that I woulnd't mind if they killed the upload (if storage or copyright is a concern) and have some sort of local wifi sync :-)
Agreed. I never used Upload because the last time it was discussed, it's not encrypted (nor are things like prayer lists etc.), and also, once you upload it, there is no way to "un" upload it - it's on the server forever.
I agree with Daniel - imho kill the Upload - it's an incomplete implementation anyway. The compiled personal books get sync'd along with every other resource, just put the source documents in a cloud somewhere that a person can get access to amongst their computers if they want to edit/modify one of them.
You don't need the source to move the personal books and their metadata (title, book cover image, etc.) to a new installation, just have a copy of the compiled files somewhere you can get access to, and from within Logos do a "Scan" - metadata and resource goes right into the new library! I have a Dropbox account, I have one folder for personal book source files (Word files and jpg image files of the book cover), and one folder for compiled personal books. I copy the .lbspbb (personal book) compiled files from my Resources folder to the Dropbox folder before moving to a new computer - works great.
0 -
I moved away from online storage as it would give me errors while syncing and I would have to restart Logos. Now that all my files are local...Logos PB only works by restarting. lol
0 -
I moved away from online storage as it would give me errors while syncing and I would have to restart Logos. Now that all my files are local...Logos PB only works by restarting. lol
The folders kept online in the scenario I described are only for (a) loading a word doc to make changes to a PB (b) to scan compiled PBs to get them into your library, a one time event for a given installation. Unless you are speaking about sync errors within the tool, so online solutions work way better than others - I have not experienced that with Dropbox or Apple iCloud and I use both extensively.
0 -
I've been getting errors consistently since recently, where the first build is fine...I look for errors (I was surprised that Mt 5:2,3 doesn't work as a nice clean reference...but hey, that's just me.) fix them, click build and it always halts with the pesky error: Couldn't remove existing book.....
Thanks for the report on this. We recently introduced a bug that affected this. We should have a fix in an upcoming release.
Andrew Batishko | Logos software developer
0 -
-
I thought this bug is fixed. But I get
[Info] Erstellen starten für PBB:9905fac546e24c09a053c3e6368cb3c4
[Error] Error while building book: Vorhandenes Werk kann nicht entfernt werden. Bitte schließen Sie alle anderen offenen Fenster und versuchen Sie es noch einmal.
[Error] Exception: LDLS4.Panels.PersonalBookBuilderPanel.PersonalBookBuilderException: Vorhandenes Werk kann nicht entfernt werden. Bitte schließen Sie alle anderen offenen Fenster und versuchen Sie es noch einmal.
at LDLS4.Panels.PersonalBookBuilderPanel.PersonalBookConverter.CreatePersonalBookWork(PersonalBook book, PersonalBookBuilderViewModel model, PersonalBookViewModel bookViewModel, IPersonalBookBuildLog buildLog)+MoveNext() in /Volumes/Code/Jenkins/workspace/Logos-Desktop-Mac-Beta-Ship/LogosDesktop/src/LDLS4/Panels/PersonalBookBuilderPanel/PersonalBookConverter.cs:line 113
at Libronix.Utility.Threading.AsyncWorkerTask`1[[Libronix.Utility.VoidType, Libronix.Utility, Version=17.8.0.0, Culture=neutral, PublicKeyToken=null]].EnumMoveNext()
at Libronix.Utility.Threading.AsyncWorkerTask`1[[Libronix.Utility.VoidType, Libronix.Utility, Version=17.8.0.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/Jenkins/workspace/Logos-Desktop-Mac-Beta-Ship/LogosDesktop/src/LDLS4/Panels/PersonalBookBuilderPanel/PersonalBookViewModel.cs:line 727If I try to rebuild the resource.
I would be keen on a fix.
Χριστὸς ἐν ὑμῖν, ἡ ἐλπὶς τῆς δόξης·
0 -
I thought this bug is fixed. But I get
No. Restarting Logos is the only solution.
Dave
===Windows 11 & Android 13
0 -
-
-
I thought this bug is fixed. But I get
No. Restarting Logos is the only solution.
Hello Dave, thanks.
Hello Andrew Batishko, please improve Logos. If I want to reimport in A a resource, I can do it multiple times without a restart every time. If the resource is open, A gives a warning, which is to agree and then the resource get closed and the reimport runs through.
Χριστὸς ἐν ὑμῖν, ἡ ἐλπὶς τῆς δόξης·
0 -
Hello
Unfortunately I got still
[Info] Erstellen starten für PBB:bd0570295b2546e28387b29bf0d2b24f
[Error] Error while building book: Vorhandenes Werk kann nicht entfernt werden. Bitte schließen Sie alle anderen offenen Fenster und versuchen Sie es noch einmal.
[Error] Exception: LDLS4.Panels.PersonalBookBuilderPanel.PersonalBookBuilderException: Vorhandenes Werk kann nicht entfernt werden. Bitte schließen Sie alle anderen offenen Fenster und versuchen Sie es noch einmal.
at LDLS4.Panels.PersonalBookBuilderPanel.PersonalBookConverter.CreatePersonalBookWork(PersonalBook book, PersonalBookBuilderViewModel model, PersonalBookViewModel bookViewModel, IPersonalBookBuildLog buildLog)+MoveNext() in /Volumes/Code/Jenkins/workspace/Logos-Desktop-Mac-Stable/LogosDesktop/src/LDLS4/Panels/PersonalBookBuilderPanel/PersonalBookConverter.cs:line 113
at Libronix.Utility.Threading.AsyncWorkerTask`1[[Libronix.Utility.VoidType, Libronix.Utility, Version=17.8.2.0, Culture=neutral, PublicKeyToken=null]].EnumMoveNext()
at Libronix.Utility.Threading.AsyncWorkerTask`1[[Libronix.Utility.VoidType, Libronix.Utility, Version=17.8.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/Jenkins/workspace/Logos-Desktop-Mac-Stable/LogosDesktop/src/LDLS4/Panels/PersonalBookBuilderPanel/PersonalBookViewModel.cs:line 727I have to say the book was open as I ran the update process. Logos should close first the book, maybe ask to do it and the update it.
Thanks for the fix.
Χριστὸς ἐν ὑμῖν, ἡ ἐλπὶς τῆς δόξης·
0 -
After I closed it.
[Info] Erstellen starten für PBB:bd0570295b2546e28387b29bf0d2b24f
[Error] Error while building book: Vorhandenes Werk kann nicht entfernt werden. Bitte schließen Sie alle anderen offenen Fenster und versuchen Sie es noch einmal.
[Error] Exception: LDLS4.Panels.PersonalBookBuilderPanel.PersonalBookBuilderException: Vorhandenes Werk kann nicht entfernt werden. Bitte schließen Sie alle anderen offenen Fenster und versuchen Sie es noch einmal.
at LDLS4.Panels.PersonalBookBuilderPanel.PersonalBookConverter.CreatePersonalBookWork(PersonalBook book, PersonalBookBuilderViewModel model, PersonalBookViewModel bookViewModel, IPersonalBookBuildLog buildLog)+MoveNext() in /Volumes/Code/Jenkins/workspace/Logos-Desktop-Mac-Stable/LogosDesktop/src/LDLS4/Panels/PersonalBookBuilderPanel/PersonalBookConverter.cs:line 113
at Libronix.Utility.Threading.AsyncWorkerTask`1[[Libronix.Utility.VoidType, Libronix.Utility, Version=17.8.2.0, Culture=neutral, PublicKeyToken=null]].EnumMoveNext()
at Libronix.Utility.Threading.AsyncWorkerTask`1[[Libronix.Utility.VoidType, Libronix.Utility, Version=17.8.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/Jenkins/workspace/Logos-Desktop-Mac-Stable/LogosDesktop/src/LDLS4/Panels/PersonalBookBuilderPanel/PersonalBookViewModel.cs:line 727After a new try.
Restart Logos open the book, closed the book, and press update.
Result = Crash again. So it doesn't matter if the book was open by update. It must not have opened before the update. That means no difference than before.
MacBook Pro i7 2018 T2
Χριστὸς ἐν ὑμῖν, ἡ ἐλπὶς τῆς δόξης·
0 -
Logos should close first the book,
It should close the book if it is open before attempting to recompile the book. Are you able to take a screen recording (video) of all of your Logos application window(s) and the process steps you go through to get this error?
Mac Developer
Faithlife0
