BUG:Repeated "Could not remove" Personal Book Errors

When editing the docx document and rebuilding a personal book, this error will occur after 2-4 Build Book commands without a restart of Logos. This appears to be a regression, but not as bad as the original bug.

For me, the quickest way to clear the error is to restart Logos. These logs are from three failures earlier this week. I did not archive logs of the latest failure which occurred a few minutes ago.

8446.LogosLogs.jackcav.20160519-145615.zip

5633.LogosLogs.jackcav.20160519-154109.zip

6470.LogosLogs.jackcav.20160519-155236.zip

Find more posts tagged with

Comments

Philana R. Crouch

When editing the docx document and rebuilding a personal book, this error will occur after 2-4 Build Book commands without a restart of Logos. This appears to be a regression, but not as bad as the original bug.

For me, the quickest way to clear the error is to restart Logos. These logs are from three failures earlier this week. I did not archive logs of the latest failure which occurred a few minutes ago.

8446.LogosLogs.jackcav.20160519-145615.zip

5633.LogosLogs.jackcav.20160519-154109.zip

6470.LogosLogs.jackcav.20160519-155236.zip

Jack I'm unable to reproduce this, could you post the Personal Book you are using?

Andrew Batishko

Jack, it's possible that sometimes the personal book is in the middle of being indexed when you try to rebuild it. Next time this happens, can you check to see if the indexer is running when you get the error?

Jack Caviness

https://community.logos.com/discussion/comment/823563#Comment_823563

Jack, it's possible that sometimes the personal book is in the middle of being indexed when you try to rebuild it. Next time this happens, can you check to see if the indexer is running when you get the error?

Interesting possibility. I will check next time.

Jack Caviness

https://community.logos.com/discussion/comment/823561#Comment_823561

"Jack I'm unable to reproduce this, could you post the Personal Book you are using?"

This failure is not resource specific, and it has not been predictable thus far.

Jack Caviness

https://community.logos.com/discussion/comment/823563#Comment_823563

Jack, it's possible that sometimes the personal book is in the middle of being indexed when you try to rebuild it. Next time this happens, can you check to see if the indexer is running when you get the error?

Just had another failure in building a PB. I had just made a successful build. then saw the need for some minor editing—increasing the heading level of a half-dozen lines. the repeat build failed with the same error. The Indexer was inactive at the time.
2474.LogosLogs.jackcav.20160530-133836.zip
If it is of any assistance, here is the docx file
6746.NT211 Introducing the Gospels and Acts.zip
Took a look at the archived logs. The Indexer ends with this:
[quote]
2016-05-30 13:36:54.7425 | INFO | 1 | IndexerProgram | Shutting down services.
2016-05-30 13:36:54.7612 | INFO | 1 | WebCache | Beginning WebCacheDownloader.Dispose()
PBB log does not include time stamps, but I exited the app at 13:38, so it is possible that WebCacheDownloader.Dispose—whatever that is—was still active.