Personal Book trouble
I am having trouble with many of my Personal Books not working in Logos 8, and many of my Personal Book docx files not working (building) when I try to recreate the Personal Book.
Anyone else having trouble with this?
"In all cases, the Church is to be judged by the Scripture, not the Scripture by the Church," John Wesley
Comments
-
Sorry about this. I've built a couple successfully recently, and I'm able to view and read them fine as well. Are you getting an error log? What does it say?
What do you mean when you say they're not working. Can you post a screenshot?
0 -
Anyone else having trouble with this?
Yes. It seems something is really wrong with my books (I get a "You don't have a license for this resource" window when I try to open one) and with building books (I get failures with error messages).
Faithlife, we need some help.
Pastor, North Park Baptist Church
Bridgeport, CT USA
0 -
Here's a builder screen:
As you can see I last successfully built this book March 27, 2017.
When I click on Open:
When I try to build the book:
This is the error log:
I get the same results with almost every personal book that I've tried this with so far. I think out of about ten I tried two opened.
Pastor, North Park Baptist Church
Bridgeport, CT USA
0 -
I did a quick spot check and couldn't find any books that would not open. Curious, the books that aren't opening, have you uploaded them to the server? If you are on the same machine that created them I know this shouldn't be necessary but I am curious if that might have something to do with it.
0 -
This is the error log:
The image is very low-res and I can't read it. Can you upload a full-res image?
0 -
What Mark describes is exactly the trouble I am having. I had rather have Logos 7 with my personal books than Logos 8 without them.Anyone else having trouble with this?
Yes. It seems something is really wrong with my books (I get a "You don't have a license for this resource" window when I try to open one) and with building books (I get failures with error messages).
Faithlife, we need some help.
A few of my personal books have compiled, but most have not. All the files had compiled in the past.
I have not uploaded my personal books? Could this be part of the problem? I have no need for my books to be on Logos servers. I have always saved my docx files, and recompiled them. Before Logos 8, no problem.
"In all cases, the Church is to be judged by the Scripture, not the Scripture by the Church," John Wesley0 -
Here it is:
[Info] Starting build for PBB:efed307a3af34b088bec590c2c2533a6
[Info] Converting
[Info] Converting C:\Users\markn\Documents\Word\3678.ESVSB Charts for notes.docx
[Info] Compiling
[Error] Article 'D1_footnote-1' has no content; articles cannot be empty.
[Error] The Compile Failed
[Error] Error while building book: Error compiling resource.
[Error] Exception: LDLS4.Panels.PersonalBookBuilderPanel.PersonalBookBuilderException: Error compiling resource.
at LDLS4.Panels.PersonalBookBuilderPanel.PersonalBookConverter.CompileResource(LicenseManager licenseManager, String manifest, ResourceDocumentData metadata, IPersonalBookBuildLog buildLog, TempFiles tempFiles, IWorkState workState)
at LDLS4.Panels.PersonalBookBuilderPanel.PersonalBookConverter.<CreatePersonalBookWork>d__2.MoveNext()
at Libronix.Utility.Threading.AsyncWorkerTask`1.EnumMoveNext()
at Libronix.Utility.Threading.AsyncWorkerTask`1.EnumMoveNextWithCatch()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at Libronix.Utility.Threading.AsyncWorkItem.Verify()
at LDLS4.Panels.PersonalBookBuilderPanel.PersonalBookViewModel.<CreatePersonalBookWork>d__137.MoveNext()Pastor, North Park Baptist Church
Bridgeport, CT USA
0 -
[Error] Article 'D1_footnote-1' has no content; articles cannot be empty.
I don't think this is an L8 issue. In your book is an empty footnote (from the file name I'm assuming you are using the file shared by Steve Clark as *.doc in 2011 in the forum, originally to be copied into Notes since there were no PBs back then) - it breaks the PB-compile under Verbum 7.19 stable version as well.
I put an attribution (not visible in the PB) into the empty footnote: 3404.3678.ESVSB Charts for notes.docx and then it compiles well under versions 7 and 8.
Note that the file contains a broken link (to "Masoretic Pointing") and the links are not always precise (since offsets in links are broken since many moons and the links are missing the ctx-parameter that one obtains by selecting the text the reference should go to).
Have joy in the Lord!
0 -
I must have a lot of the same problem because it isn't just this PB that won't compile. (The problem could go back to L7 since I haven't looked at most of these in many months.)
It did compile back in March 2017 (L7 days), and as far as I know that compilation was successful. So it seems strange the problem is in the file. But, hey, I don't have any idea what the problem is so you may be right. That doesn't explain the other books that I've tried to open and haven't been successful with.
Pastor, North Park Baptist Church
Bridgeport, CT USA
0 -
it breaks the PB-compile under Verbum 7.19 stable version as well.
I put an attribution (not visible in the PB) into the empty footnote: 3404.3678.ESVSB Charts for notes.docx and then it compiles well under versions 7 and 8.
Note that the file contains a broken link (to "Masoretic Pointing") and the links are not always precise (since offsets in links are broken since many moons and the links are missing the ctx-parameter that one obtains by selecting the text the reference should go to).
Charlie Brown's teacher
0 -
I must have a lot of the same problem because it isn't just this PB that won't compile. (The problem could go back to L7 since I haven't looked at most of these in many months.)
It did compile back in March 2017 (L7 days), and as far as I know that compilation was successful. So it seems strange the problem is in the file. But, hey, I don't have any idea what the problem is so you may be right. That doesn't explain the other books that I've tried to open and haven't been successful with.
I'm not sure exactly when (not to mention there never was a satisfying answer as to why) Faithlife introduced the change to the PB compiler that breaks the build when it finds "empty paragraphs" e.g. paragraph marks that are formatted with a Heading style. It will break the recompile of nearly all PBs where the source predates that change. This has been discussed in dozens of forum threads.
To clarify my understanding:
- An in-place-upgrade from L7 to L8 should leave all PBs undisturbed.
- A new installation of L8 will have the PB metadata but will open only those PBs that had been uploaded to the servers, all others will show the - somewhat misleading - error message "you have no license for this resource". This is not an L8 issue but happens on every new install of Logos, as the compiled resource file simply is not present for the program. To make it available you can do the following:
- If you still have the L7 installation, you can choose to upload all PBs (note there is a size limit of probably still 20MB of the compiled book, so the button may be greyed out for some overly large PBs). The L8 program will automatically download them from the server, just like newly bought books.
- Alternatively, you can use the Scan command on the folder where the compiled PBs are in your prior installation - or put them onto a USB stick/thumbdrive or something you can easily identify (such as Scan G:\ when the stick is mounted as G:)
- You can rebuild the PBs in the new installation. This requires the PB sources to be present and it will require them to follow the current acceptable compiler standards, i.e. no empty paragraphs. A quick workaround for that may be to replace all paragraph marks with space-paragraph in Word ("^p" with " ^p") and, if it still breaks, put in something before empty section breaks and into empty footnotes/endnotes.
Have joy in the Lord!
0 -
it breaks the PB-compile under Verbum 7.19 stable version as well.
I put an attribution (not visible in the PB) into the empty footnote: 3404.3678.ESVSB Charts for notes.docx and then it compiles well under versions 7 and 8.
Note that the file contains a broken link (to "Masoretic Pointing") and the links are not always precise (since offsets in links are broken since many moons and the links are missing the ctx-parameter that one obtains by selecting the text the reference should go to).
Charlie Brown's teacher
Sorry, I was explaining the issues with a specific file from 2011 to another MVP whose Logos history is much longer than mine. You did cut off the most relevant part in your quote, though: This is not a Logos 8 issue.
I hope my subsequent post is more helpful to you - otherwise please ask and we'll try to help if we can.
Have joy in the Lord!
0 -
Thanks, Mick. No L7 installation, so I'll have to go about trying to fix the .docx files for those that are worth the trouble to do so.
Pastor, North Park Baptist Church
Bridgeport, CT USA
0 -
IM having the same issue. does this mean there is no way that Logos can update their PB compiler? and i have to go scouring through all my docx files for some empty whatchacallits??
0 -
IM having the same issue.
Please clarify in more detail what you see as "having the same issue" - screenshots and logfiles will probably help.
does this mean there is no way that Logos can update their PB compiler?
Actually they did. To the best of my knowledge, the current version of Logos will not break the build when encountering "empty paragraphs" - it will document this in the PB compile log, but go on. You may safely ignore those log entries, the books will be fully functional. So: scouring through the files and changing docx that used to work in the past should no longer be necessary.
Have joy in the Lord!
0 -
I have encountered a similar problem:
Normally I use an old PC Laptop with L8 and have quite a few PBs and they all seem to be working fine.
Today I was going to travel with my wife's old MacBook Pro but when I tried to open one of my PBs I got the dreaded "You don't have a license to view this resource" notification.
I hadn't used the MacBook in a while so I have made sure I have no more notifications about resources being downloaded and made sure my indexing was complete but still get the "No License" flag.
I saw a reference in some of the other posts about the need to upload the PBs to the server; I have not done this, didn't know I needed to do this, don't know how to do this.
Do I need to upload the books from my PC in order for the MacBook to download them?
How do I do this?
0 -
I got the dreaded "You don't have a license to view this resource" notification.
That simply means that you have not compiled the resource on this particular computer. The metadata (author, title, book cover) automatically syncs. The actual resource itself, does not.
I saw a reference in some of the other posts about the need to upload the PBs to the server; I have not done this, didn't know I needed to do this, don't know how to do this.
You don't have to do so, and there are some consequences of doing so. Once you upload it, you can't delete it from the FL servers. Some users complain about this, so fair warning.
Do I need to upload the books from my PC in order for the MacBook to download them?
To download something, it first has to be uploaded... so yes. However, you do not have to upload it to view it on the other computer. You can choose to recompile it on that device. If you do, it will require that you have the source .docx file.
How do I do this?
To upload a personal book resource, you press the "upload" button in the edit view of the "personal book builder" tool.
0 -
The metadata (author, title, book cover) automatically syncs. The actual resource itself, does not.
Alternative to upload/download (or recompile that changes metadata update date) is using SCAN command on a computer to copy compiled *.lbspbb resource into your Logos library (for your use).
One process for Personal Books is compiling on one computer followed by sync of resource metadata into your other installation(s) then use SCAN command (can copy compiled *.lbspbb resource files to USB drive or use a shared network drive)
Keep Smiling [:)]
0 -
I gave up on personal books, and use Notes for everything. No formatting necessary, no import necessary, no special codes necessary, no issues with system updates.
0 -
Glad that works for you. The new Notes is quite good, quite capable.
0 -
LOL
0
