Cited By tool crashes Logos 9
Hello,
I am running the latest version on Windows 10. I can run every other tool no problem, but even if I launch the Cited By tool all by itself it crashes the program and quits to desktop.
Has anyone else had any similar problems?
Comments
-
Hi Morgan
Has anyone else had any similar problems?
I haven't seen this problem and don't remember seeing reports of it.
I have just tried it on my Windows 10 system and it worked fine.
Please enable diagnosting logging and post logs files in a reply to this thread (use the paperclip icon) after Logos crashes
Details at https://support.logos.com/hc/en-us/articles/360027869132
Graham
0 -
Hi Graham, thanks for the response.
I followed the steps in the link and sent an email to Logos support. I've also attached the compressed file to this post per your instructions.
Thank you!
0 -
The logos.log file shows:
2021-10-14 07:57:42.2121 INFO 1 AppCommand | (505ms) Executing command: CitedBy
2021-10-14 07:57:42.5100 INFO 29 SimpleQueryUtility | (Timed) Performing relevance search
2021-10-14 07:57:42.5150 INFO 29 SimpleQueryUtility | (2ms) Performing relevance search
2021-10-14 07:57:42.6665 ERROR 17 ApplicationUtility | Unhandled exception in async work System.Collections.Generic.KeyNotFoundException: The key was not found in the collection.This suggests to me that there is an issue with one of the collections the Cited By Tool is configured to use. But it doesn't tell me which one.
And I don't know how to open the Cited By Tool in a state where it doesn't immediately search the linked collections so you could try removing them one by one and seeing what happens
Hopefully Logos support (or someone else here) will be able to advise further
0 -
My guess is that your search index is corrupted.
I recommend using the "Rebuild index" command in the Go box. This will completely regenerate your index, which may take a while, but will hopefully clear up the problem.
Andrew Batishko | Logos software developer
0 -
Andrew, that's the solution! Thank you for the reply
Graham, thank you for looking into the issue as well. It works great now!
0
