L4 Fails to open and crashes
I get this message: Logos Bible Software 4 has encountered a problem and needs to close. Send Error Report
Here is the Error Signature
Event Type: clr20r3 P1: logos4.exe P2: 4.1.3.5180 P3: 4B4Ba820 P4: libronix search engine P5: 4.1.3.5180 P6: 4B4Ba6F9 P7:23c 8: 74 P9:system.invalidoperationexception
Here's the Log File:
Comments
-
Gary, it appears your log didn't upload correctly. Could you try to upload it again?
or if you want to confirm a hunch of mine...
Most people having this problem are suffering from a corrupt index. To confirm, open your log file, search for the Error message if it reads: "Error OurApp Unhandled exception:
System.InvalidOperationException: Error reading postings. Document id
out of range" you have a corrupt index. The way to fix this is to
make a new index.To do this: delete the contents of this folder:
C:\Users\<UserName>\AppData\Local\Logos4\Data\<random>\LibraryIndex (Vista/Win7)
and then start Logos, it will see that it doesn't have an index and
then will begin to build a new one.[Note: the AppData folder is hidden
so you will have to enable the viewing of hidden files and folders in your Folder Options to
navigate to this folder.]If your error is different re-upload your logs and someone around here should be able to recognize the error.
Prov. 15:23
0 -
Thanks Kevin. You're advice about deleting the index worked. Had to track it down via a different path in XP, however, it is now fixed. Thanks for doing this. Gary
0 -
I am having a similar problem - this is the 2nd time... both are (I think) following a standard Win XP update. I have tried starting offline and w/blank layout, but L4 crashes before opening. Also tried deleting contents of index folder - no different.
Logfile is attached... one error that stands out to me reads:
Error OurApp Unhandled exception: System.Collections.Generic.KeyNotFoundException: The key was not found in the collection.
Last time around, could not find a fix and finally decided the shorter course was a complete uninstall and re-install of L4 (I have a HUGE library, so this was a pain). I am willing to try a few things this time around if anyone has suggestions.
Thanks for any help!
Robert Austell - robert@gspc.net
0 -
Robert, I am not familiar with that error. However, since it mentions the Keylink manager I'm going to guess that database might be corrupt. Try renaming C:\Documents and Settings\<UserName>\Local Settings\Application Data\Logos4\Data\<Random>\KeyLinkManager\keylinkmanager.db to oldkeylinkmanager.db (or something like that) and then try starting Logos to see if it can start and build a new database.
Prov. 15:23
0 -
Kevin Becker said:
Robert, I am not familiar with that error. However, since it mentions the Keylink manager I'm going to guess that
database might be corrupt. Try renaming C:\Documents and
Settings\<UserName>\Local Settings\Application
Data\Logos4\Data\<Random>\KeyLinkManager\keylinkmanager.db to
oldkeylinkmanager.db (or something like that) and then try starting
Logos to see if it can start and build a new database.Kevin - thanks for the suggestion... it sounded promising, but still had a crash. I've attached a new logfile, slightly different than the last.
Robert
0 -
Well, I'm stumped. [:^)]
All I can say is try a call to tech support, be certain to direct them to the info and the stuff you've tried in this thread.
Prov. 15:23
0 -
Thanks for trying, Kevin. I just wrangled an update out of it... left the XP crash notice open and then went to the LogosUpdate.exe file and clicked it a few times... it managed to install some minor update and then on re-start it worked. It seems really sluggish - but maybe just needs to re-index or something now. I'm just glad to get it going.
0 -
It was a fault on the server - see my last post at http://community.logos.com/forums/t/12879.aspx . The path to your folders is at
\My Documents\Logos4\Data\fwnmia5l.uqb\ But this is history if your installation is now working OK.
Dave
===Windows 11 & Android 13
0
