Crash after prioritizing lectionary
I was reading a post about someone wanting the 3 year Luther lectionary to show up on his homepage. I advised him to prioritize it. Just to double check I...
- Prioritized the Lutheran 3 year lectionary to the top of my priority list
- Opened my Homepage
- Clicked on the Title of the upcoming Sunday (the Lectionary opened as expected)
I then Alt-Tabed over to Firefox to hit post on my advice and while I was still in my browser (2ish seconds) Logos crashed.
Prov. 15:23
Comments
-
So I'm a little confused: the Error is "OurApp Unhandled exception: System.InvalidOperationException: Error reading postings. Document id out of range." which is the corrupt index error, only I haven't had any of the start-up problems that this error seems to have been causing people lately. Also, I don't think I've had a recent merge b/c I have a supplemental index from the IVP OT dictionaries that just came out. Finally, I haven't experienced any problems with search, why would this error come up?
Prov. 15:23
0 -
Since this error can happen when loading the home page, too, do you have L4 set to startup without the home page? If you find that loading the home page was the culprit, rebuilding the index is the fix. You may want to wait until RC 1 comes out before rebuilding.
0 -
Melissa Snyder said:
Since this error can happen when loading the home page, too, do you have L4 set to startup without the home page? If you find that loading the home page was the culprit, rebuilding the index is the fix. You may want to wait until RC 1 comes out before rebuilding.
Based on this I went back to Logos and hit the Homepage button, Logos crashed. Ok... so I was able to hit the Lectionary link before Logos encountered the index corruption. Thanks, I'll rebuild overnight.
Prov. 15:23
0 -
Kevin Becker said:
Thanks, I'll rebuild overnight.
Kev, you have my sympathy. It hits the best of us...
Dave
===Windows 11 & Android 13
0
