I am running Logos 9.14 SR 1 and have experienced 4 crashes today in about a 15 minute time span for various reasons according the Windows Event Log. Is there another patch available to provide some stability?
I am running on Windows 10 Pro
Welcome to the forums. Please provide the "various reasons" and/or logs. I don't have enough information to provide any guesses and my own installation is stable.
Crash One:
Application: LogosIndexer.exeFramework Version: v4.0.30319Description: The process was terminated due to an unhandled exception.Exception Info: System.Data.SQLite.SQLiteException at System.Data.SQLite.SqliteStatementPreparer.Get(Int32, System.Threading.CancellationToken) at System.Data.SQLite.SQLiteDataReader.NextResultAsyncCore(System.Threading.CancellationToken) at System.Data.SQLite.SQLiteDataReader.NextResult() at System.Data.SQLite.SQLiteCommand.ExecuteDbDataReader(System.Data.CommandBehavior) at System.Data.SQLite.SQLiteCommand.ExecuteNonQuery() at System.Data.SQLite.Utility.ExecuteNonQuery(System.Data.IDbConnection, System.Data.IDbTransaction, System.String) at System.Data.SQLite.SQLiteConnection.Open() at Libronix.Utility.Data.Connector.OpenConnection() at Libronix.Utility.Data.ExceptionHandlingConnector.OpenConnection() at Libronix.Utility.Data.PoolableConnector.get_OpenConnector() at Libronix.Utility.Data.PoolableConnector.OpenConnection() at Libronix.DigitalLibrary.Resources.NamedTexts.NamedTextsResourceCore.GetNamedTextWithPrimaryConcept(Libronix.DataTypes.Specific.BibleKnowledgebaseReference, System.String) at Libronix.DigitalLibrary.Resources.NamedTexts.NamedTextsResource.GetNamedTextWithPrimaryConcept(Libronix.DataTypes.Specific.BibleKnowledgebaseReference, Libronix.Globalization.Culture) at Libronix.DigitalLibrary.Utility.AutoComplete.AutoCompleteService.InsertTopics(Database, Libronix.DigitalLibrary.Resources.LogosControlledVocabulary.LogosControlledVocabularyResource, Libronix.DigitalLibrary.Resources.NamedTexts.NamedTextsResource, Libronix.Utility.Threading.IWorkState) at Libronix.DigitalLibrary.Utility.AutoComplete.AutoCompleteService.UpdateFromResourceManager(Libronix.DigitalLibrary.ResourceManager, Libronix.DigitalLibrary.Resources.ResourceLists, Libronix.Utility.Threading.IWorkState) at LDLS4.Indexer.IndexerProgram.DoUpdateResourceManagerClients(Libronix.Utility.Threading.IPausableWorkState) at LDLS4.Indexer.IndexerProgram.UpdateResourceManagerClients(Libronix.Utility.Threading.IPausableWorkState, IndexThreadData) at Libronix.Utility.Threading.WorkStateThreadOwner`1[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].ThreadProc(System.Object) at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean) at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean) at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object) at System.Threading.ThreadHelper.ThreadStart(System.Object)
----------------
Faulting application name: LogosIndexer.exe, version: 9.13.0.18, time stamp: 0xfcdb0eb4Faulting module name: KERNELBASE.dll, version: 10.0.19041.1741, time stamp: 0xe9b4a91bException code: 0xe0434352Fault offset: 0x0000000000034fd9Faulting process id: 0x5168Faulting application start time: 0x01d885863ec9bf8eFaulting application path: C:\Users\mmfen\AppData\Local\Logos\System\LogosIndexer.exeFaulting module path: C:\Windows\System32\KERNELBASE.dllReport Id: 221ecbc4-846c-4699-84c9-4b0c967ea744Faulting package full name: Faulting package-relative application ID:
Crash 2:
Faulting application name: LogosIndexer.exe, version: 9.13.0.18, time stamp: 0xfcdb0eb4Faulting module name: KERNELBASE.dll, version: 10.0.19041.1741, time stamp: 0xe9b4a91bException code: 0xe0434352Fault offset: 0x0000000000034fd9Faulting process id: 0x578cFaulting application start time: 0x01d88586c8064a87Faulting application path: C:\Users\mmfen\AppData\Local\Logos\System\LogosIndexer.exeFaulting module path: C:\Windows\System32\KERNELBASE.dllReport Id: a6f2e705-fd57-4726-9479-1a8f26f6a928Faulting package full name: Faulting package-relative application ID:
Crash 3:
Application: Logos.exeFramework Version: v4.0.30319Description: The application requested process termination through System.Environment.FailFast(string message).Message: Unhandled exception in async workStack: at System.Environment.FailFast(System.String, System.Exception) at Libronix.Utility.Threading.AsyncWorkerTask`1[[System.Boolean, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].EnumMoveNext() at Libronix.Utility.Threading.AsyncWorkerTask`1[[System.Boolean, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].ContinueExecution(System.Object) at Libronix.Utility.Threading.GroupedThreadPool.ExecuteNextCallback(System.Object) at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean) at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean) at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem() at System.Threading.ThreadPoolWorkQueue.Dispatch()
---------------
Faulting application name: Logos.exe, version: 9.13.0.18, time stamp: 0xa56b7ffeFaulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000Exception code: 0x80131623Fault offset: 0x00007ff8aedc13c9Faulting process id: 0x4eb4Faulting application start time: 0x01d885862d3ddd9cFaulting application path: C:\Users\mmfen\AppData\Local\Logos\System\Logos.exeFaulting module path: unknownReport Id: a2eb7a9b-92e2-49c2-b949-ce31774854fbFaulting package full name: Faulting package-relative application ID:
Crash 4:
------------
Faulting application name: LogosIndexer.exe, version: 9.14.0.26, time stamp: 0xf5b0169eFaulting module name: KERNELBASE.dll, version: 10.0.19041.1741, time stamp: 0xe9b4a91bException code: 0xe0434352Fault offset: 0x0000000000034fd9Faulting process id: 0x3778Faulting application start time: 0x01d885872f97c51aFaulting application path: C:\Users\mmfen\AppData\Local\Logos\System\LogosIndexer.exeFaulting module path: C:\Windows\System32\KERNELBASE.dllReport Id: a6a382e4-876a-4392-a2aa-26564ecaa386Faulting package full name: Faulting package-relative application ID:
=====================
Wasn't doing much at anyone of these moments other than open up the NIV Bible and navigate around a bit
To better understand the context of what was happening we need to see the logos.log file (if one was created).
And it needs to one created after Logos crashed and before restarting it.
If you have one, please upload using the paperclip icon (please don't paste the contents)
If one wasn't created, please enable full diagnostic logging - details at https://support.logos.com/hc/en-us/articles/360027869132 - and then upload one if Logos crashes again.
EDIT: And picking up on MJ's point below, please upload the indexer.log file as well
Thank you for the information. It is the background indexing that is failing not the main application. I would need full logs to determine if there is a particular resource in your installation that is causing the problem or if there is a corrupt indexing file causing the problem. There are a couple of people in the forums who may recognize the problem more quickly than I who can identify the file(s) that need to be removed (and rebuilt) to fix the problem.
This should be the Logos error folder
8686.Logos.zip
It looks as though, as MJ suggested, one of the databases has become corrupt - with the log having:
System.BadImageFormatException: Could not load file or assembly 'Faithlife.LibraryReportsApi.v1
I don't have access to my Windows computer at the moment to advise where this is so it can be deleted (and the software should recreate it)
Hopefully someone else wil be able to advise further.
If not, try contacting Customer Services and they should be able to help
It looks as though, as MJ suggested, one of the databases has become corrupt - with the log having: System.BadImageFormatException: Could not load file or assembly 'Faithlife.LibraryReportsApi.v1 I don't have access to my Windows computer at the moment to advise where this is so it can be deleted (and the software should recreate it) Hopefully someone else wil be able to advise further. If not, try contacting Customer Services and they should be able to help
That error comes from March 2022 and is not related to the current crash which is connected with the sequence of updating Auto Complete from Resource Manager. I'm not sure what database is responsible so I would also advise contacting Customer Services.
This should be the Logos error folder 8686.Logos.zip
Hi Michael,
As others have noted your logs are very old, but your crash text log which is recent indicates that it is a corrupted database. You'll need to contact Customer Service because they have some tools that might be able to isolate the problem.
Blessings,
Philana
