I got an error re-uploading a PB.

Kristin · 2025-08-05T03:45:02+00:00

There was an error rendering this rich post.

So I have a PB called something like Translation NT, and the file was Translation NT since I was nervous.

This time, however, since I think I understand it better, I figured as long as I keep the PB called Translation NT, the file can be whatever, so the file is Translation Aug 25 NT

I am not sure if that matters or not.

So I went to the PB and pressed "edit" and left the title and everything the same. I then deleted the document and only after that I added the new file of Translation Aug 25 NT

However, when I clicked build I got an error report saying that it could not remove the old file and I needed to close all windows. Yet all windows were closed except for this.

The one thing I thought of is that I have shortcut panels on the "Dashboard" of some of my class layouts which contain this PB. The class layout is not open, but is it a problem for it to be a panel on the Dashboard?

Thank you for any help anyone can provide.

Bildschirmfoto 2025-08-04 um 22.36.57.png

Find more posts tagged with

Personal Books

Desktop App

Accepted answers

All comments

Kristin

Never mind, I figured it out. The issue is that I had Logos open on my phone. I shut it on my phone and restarted Logos on the computer and it uploaded fine. :)

So then I tried uploading the OT without deleting the Dashboard shortcut, and that worked fine. So the issue was the phone.

John

Strange that the mobile app would do that, as it is a common disappointment when people find out that the mobile app cannot view their personal books. ?

Kristin

Hi @John, to be honest, I found the whole thing strange too, as the only thing open on Logos on my phone was the ESV with no parallels or anything.

On a side note, did you just say that PBs are only viewable on the computer and not the mobile app? I didn't know that.

John

@Kristin

On a side note, did you just say that PBs are only viewable on the computer and not the mobile app?

If you search the forum you will find numerous threads requesting support for PB on the mobile app. Only desktop app supports them AFAIK.

Bernhard

https://community.logos.com/discussion/comment/1376037#Comment_1376037

The phone did not cause this. This error has been around for a long time. Somehow Logos is still using the resource and and can therefore not replace it. The only solution to this is to close Logos and restart it before recompiling the book. If you search for the error message on the forum you will find many threads about this (I think at one time Logos made some changes, but that hasn't really helped).

Dave Hooton

https://community.logos.com/discussion/comment/1376037#Comment_1376037

The problem arises because the app cannot remove the existing PB (not the docx file) and the only fix is to restart (desktop) Logos.

You can add or remove docx files without issue. Multiple docx files are compiled in the order you list them.

Fabian

Would love to see a fix for this issue.

Kristin

Hi @Bernhard and @Dave Hooton, ok, thanks for clarifying this. I guess I had never experienced this before since although I have created a few of these, this was the first time I tried replacing one.

So if I understand correctly, Logos needs to be completely restarted, so closing it on my phone would be part of that, but then also closing it on my computer, and then trying.

That said, I am still supposed to delete the old file first. Is this correct? So I go to the PBs and edit it to delete the docx. Then I close the program completely, then I go back to the PB and add the new docx?

Or by contrast, am I supposed to delete the old docx, then add the new docx, and then close the program before I click "build book"?

NB.Mick

https://community.logos.com/discussion/comment/1376059#Comment_1376059

I think you are making it more complicated than needs be. This error happens when you try to recompile a PB that is "open" somewhere for the desktop instance (which often closes the in-your-face-open resource panel without issue, but can't handle the passage guide or search running elsewhere). You can leave open Logos on any other machine, especially mobile, and you don't need to change the file at all.

If you just want to recompile a PB (i.e. due to changes in the source document or changes you make to the metadata) which is not open anywhere, you don't need to close Logos.

Actually I try the recompile, see if it works , and if I get the error restart the desktop app and recompile subequently. No big deal (it would be nicer without, no question), a restart is a thing of a few seconds anyway.

Kristin

I think you are making it more complicated than needs be. This error happens when you try to recompile a PB that is "open" somewhere for the desktop instance…If you just want to recompile a PB (i.e. due to changes in the source document or changes you make to the metadata) which is not open anywhere, you don't need to close Logos.

Hi @NB.Mick, what you said had been my original thought as well, which is what I did before I posted. In case it helps, here are the steps I took:

Pressed the "Close all panels" button on the toolbar
From the Dashboard, I pressed the 9-dotted "Tools" on the toolbar and scroll down to Personal books.
Went to the PB in question and pressed "edit"
Clicked "delete" on the docx file
Clicked to add the new docx file
Clicked "build book"
Received the error message above
Closed the PB panel
Pressed "Close all panels"
Did steps 2-6 again and received the same error

I then posted this thread and error picture and then after doing so I completely closed Logos on both the phone and my computer and tried again. This time when I went to the PB it showed only the new docx, so I clicked "build book" and it worked.

So given this, if completely closing the program on my phone and computer was not necessary, any ideas what happened?

Bernhard

Nothing to do with your phone - you only need to restart on the device where you are building the Personal Book. Also nothing to do with the docx file. You can rebuild the Personal Book using the same unchanged docx file (something that you would only do when changing metadata), using the same, but changed docx file, using the same docx file and adding another file to the end of the book, or compiling from a new docx file and deleting the original one from the PB tool. All of that should work without a problem, but using all of those ways will sometimes have that error message come up.

Kristin

Hi @Bernhard, I see, thank you for clarifying that the issue was the computer.

Also, regarding the rest of what you said… the issue is that I am actively working on a translation, and because of that I am constantly making changes to it. Every so often, normally once a month, I duplicate the file I am working on (which is for sure not a docx) and rename it in order to preserve older versions.

In Logos, however, I only care about it being the most recent version. So I had previously created a PB in Logos called "Translation NT" or whatever, and the docx under it was my translation for July.

Now I have a new version of my translation which is for August, so I went to the PB and left it as the same name and all the info about it the same, and then just sought to delete the July docx and replace it with the Aug docx, for which I went through the steps above.

After restarting Logos and going back to the PB, it showed the Aug docx and I just clicked build book (again) and it worked.

So then next month I will go through the process again with my Sept version, and I am wondering at what point I need to close Logos completely. If I am understanding correctly, I shouldn't have to do that at all. So I guess I will go through the steps I did above, and then if I get an error I will close Logos, open it, and press build book again.

MJ. Smith

I have been going through personal books shared on Logos and adding them to my library to make a catalogue of them - about 1300 PB's in the past 4 weeks. I run into the file not closed, restart Logos less than 10% of the time and am getting close to identifying the errors that keep it from being closed. It is enough of a nuisance that it feels like it happens more often than it actually does, As long as you know that restarting Logos clears the error, you'll be fine.