Error ID: 5234

Hi,
Logos will open up briefly, then give a stopped working message
Any thoughts on a fix? I've already uninstalled and reinstalled once.
Thanks
Error code:
Error ID: 5234
Program Version: 4.0d (4.04.4.1385)
Windows Version: 6.1.7600.0
Time: 2010-07-05 07:11:49
Installed memory: 1,790 MB
Install path: C:\Users\Dan\AppData\Local\Logos4\System\Logos4.exe
Data path: C:\Users\Dan\AppData\Local\Logos4\Data\lrd53wbd.hgy
Free disk space: 110,332 MB
Temp path: C:\Users\Dan\AppData\Local\Temp\
Free temp space: 110,332 MB
Error ID: 5234
Error detail: SEHException: External component has thrown an exception.
System.Runtime.InteropServices.SEHException: External component has thrown an exception.
at System.Data.SQLite.UnsafeNativeMethods.sqlite3_step(IntPtr stmt)
at System.Data.SQLite.SQLite3.Step(SQLiteStatement stmt)
at System.Data.SQLite.SQLiteDataReader.NextResult()
at System.Data.SQLite.SQLiteDataReader..ctor(SQLiteCommand cmd, CommandBehavior behave)
at System.Data.SQLite.SQLiteCommand.ExecuteReader(CommandBehavior behavior)
at System.Data.SQLite.SQLiteCommand.ExecuteNonQuery()
at System.Data.SQLite.SQLiteTransaction..ctor(SQLiteConnection connection, Boolean deferredLock)
at System.Data.SQLite.SQLiteConnection.BeginDbTransaction(IsolationLevel isolationLevel)
at System.Data.Common.DbConnection.System.Data.IDbConnection.BeginTransaction()
at Libronix.Utility.Data.Connector.BeginTransaction()
at Libronix.Utility.Data.PoolableConnector.BeginTransaction()
at LDLS4.ResourceMetadataUpdateServiceClient.SetNextStatusFromLibraryCatalog(Object state)
at Libronix.Utility.Threading.DelegateAsyncWorkItem.<ExecuteCore>b__0(Object o)
at System.Threading.ExecutionContext.runTryCode(Object userData)
at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at Libronix.Utility.Threading.DelegateAsyncWorkItem.ExecuteCore()
at Libronix.Utility.Threading.AsyncWorkItem.Execute()
at Libronix.Utility.Threading.ThreadPoolAsyncWorkItem.<StartCore>b__0(Object o)
at Libronix.Utility.Threading.GroupedThreadPool.ExecuteNextCallback(Object state)
at System.Threading._ThreadPoolWaitCallback.WaitCallback_Context(Object state)
at System.Threading.ExecutionContext.runTryCode(Object userData)
at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading._ThreadPoolWaitCallback.PerformWaitCallbackInternal(_ThreadPoolWaitCallback tpWaitCallBack)
at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback(Object state)
Comments
-
It looks like corruption with one of your preferences files to me. Possibly it's catalog.db in %localappdata%\Logos4\Data\{random}\LibraryCatalog. You can safely delete that file (it will be re-created) if you want. Re-creating it takes 10-30 minutes when you start Logos.
Alternatively, turn on full logging, and then post the log (see 'How to ask for help?', below). That way we should be able to see for certain which file it is.
This is my personal Faithlife account. On 1 March 2022, I started working for Faithlife, and have a new 'official' user account. Posts on this account shouldn't be taken as official Faithlife views!
0 -
This crash is happening to others. I'll add this thread to the wiki for the developers.
Dave
===Windows 11 & Android 13
0 -
If my suggested fix doesn't work, the other thread suggests the problem may be related to passage lists. Have you tried opening to a blank layout?
This is my personal Faithlife account. On 1 March 2022, I started working for Faithlife, and have a new 'official' user account. Posts on this account shouldn't be taken as official Faithlife views!
0 -
Hi Mark and Dave,
I deleted the catalog.db and it crased again, then i rebuilt index and am following the thread with Bill Feiss who had the same error code. Thanks for trying to address this. I suppose the best thing now is to see if Bradley can do wonders with a fix.
Thanks again
Dan
0 -
Dan Langston said:
I deleted the catalog.db and it crased again, then i rebuilt index and am following the thread with Bill Feiss who had the same error code. Thanks for trying to address this.
The error details are slightly different than Bill's. Can you enable logging and post a full Logos4.log file as well?
Thanks,
Melissa0 -
I enabled logging, and then I reindexed. After I did that it has not crashed so if it does I will send you what I have.
0