Crash Upon Creating a Reading Plan
I was hoping for a change with the last update, but Logos still crashes when attempting to create a reading plan with the Russian bible. I've made reading plans with other translations, so maybe some specific to the Russian?
Comments
-
Hello Andrew,
I've tested this successfully in the Mac and Windows versions with the "Russian Synodal Bible Translation" without a crash. Are you using a different translation?
0 -
Yes, I'm using the Russian Synodal, in Logos 4 for Mac. I have the latest updates in everything, both Mac OS and Logos.
I created a log file that might help someone. Keeps crashing!
0 -
Andrew Raatz said:
Yes, I'm using the Russian Synodal, in Logos 4 for Mac. I have the latest updates in everything, both Mac OS and Logos.
I created a log file that might help someone. Keeps crashing!
Thanks, we'll review the logs.
Edit: Andrew ~ Have your Language & Text preferences been modified?
0 -
No, my language and text shouldn't have been modified in any way.
0 -
Andrew Raatz said:
I was hoping for a change with the last update, but Logos still crashes when attempting to create a reading plan with the Russian bible. I've made reading plans with other translations, so maybe some specific to the Russian?
Andrew, could you clarify which Russian Synodal resource you're creating the reading plan for? On the resource's information page at the bottom there is a "Support Info" section. Could you post that info? For example I have the following resources:
LLS:1.0.651
2010-01-07T22:38:23Z
rst.logos4
and
LLS:BB_SBB_RUSBT
2010-01-07T22:29:04Z
BB_SBB_RUSBT.logos4
Next, we may be able to solve the issue by recreating the milestone index for whichever resource is having the problem. Please follow these steps:- Make sure Logos 4 is closed. If the indexer is running, wait until it is finished.
- Open the folder with the milestone indexes: <user_home_folder>/Library/Application
Support/Logos4/Data/<random_characters>/ResourceManager/logos - Find all of the files that begin with the resource id you found in the support info, where the colons and periods are replaced by underscores, e.g. LLS_1_0_651_2010_01_07T22_38_23Z.mstidx
- Please post all of these files so we can determine what caused the problem.
- Rename these files with a .bak extension, or move them to a different folder.
- Open Logos 4, and open the resource. (When Logos 4 realizes the milestone index is missing, it should decide to recreate it the next time the program is started.)
- Close Logos 4.
- Reopen Logos 4. You should see the message that Logos 4 is preparing your library, and the indexer message on the tray icon should say something about discovering your resources.
- (You may optionally verify that the milestone index file was recreated successfully.)
- Try to create the reading plan.
Thanks, and sorry for the inconvenience.
0 -
Here is the resource info page that I have:
LLS:1.0.651
2010-01-07T22:38:23Z
rst.logos4
I am not sure how to post any other files. Which do you mean?
0 -
There should be files with names like "LLS_1_0_651_2010_01_07T22_38_23Z.mstidx" in this folder: <user_home_folder>/Library/Application Support/Logos4/Data/<random_characters>/ResourceManager/logos
0 -
I renamed and let Logos recreate it. It worked this time!
What is the issue? A corrupt index? I had the same reading plan error happen another time, but I can't remember the resource. It was an odd resource and I forgot to note the resource. I've had this issue for months, but just chose to ignore it.
thanks for the help.
0 -
It wouldn't let me post those files. Stated "file type not allowed".
0 -
Andrew Raatz said:
It wouldn't let me post those files. Stated "file type not allowed".
It may let you if you zip them up or if you rename the extension to something like txt.
0 -
Andrew Raatz said:
What is the issue? A corrupt index? I had the same reading plan error happen another time, but I can't remember the resource. It was an odd resource and I forgot to note the resource. I've had this issue for months, but just chose to ignore it.
I think the milestone index was corrupt. We can't know exactly what went wrong without the file.
Let us know if you experience this problem with any other resources.
0 -
Renamed to .txt
0 -
Thanks for posting the file. I don't think the milestone index was corrupt after all. We made a change to the bible+rst data type before we shipped the resource. However, it appears that the Mac build available at that time didn't have the change, so it created a milestone index that became unusable after the update.
As of the latest release (4.2a) Windows and Mac are synchronized, which will avoid future problems like this.
Again, I apologize for the inconvenience.
0
