Logos 4.5B SR-2 opens, then Windows error message and closes

This morning, Logos will open, for about 45 seconds, then display a message from Windows that there is a problem with the program and needs to close. I've rebooted my computer, hard and soft, and am having the same issues. Anyone out there have any insight on how to help this Logos rookie fix this?

Find more posts tagged with

Comments

JT (alabama24)

Tony - Welcome to the forums! Sorry you are having troubles. The best thing to do at this point would be to submit logs for a techie to look over. I will include a link to the wiki below. If you want to try something, you could try opening to a blank layout. Hold down the control key when you first start Logos, the check the box for a blank layout.

http://wiki.logos.com/Diagnostic_Logging#PC

Tony Gerber

Program Version: 4.5b SR-2 (4.52.0.2204)

Windows Version: 5.1.2600.196608

Time: 2012-05-19 10:20:40 -04:00 (2012-05-19T14:20:40Z)

Installed memory: 3,000 MB

Install path: C:\Documents and Settings\tonyg\Local Settings\Application Data\Logos4\System\Logos4.exe

Free install space: 43,854 MB

Data path: C:\Documents and Settings\tonyg\Local Settings\Application Data\Logos4\Data\mzlhlh1m.yf3

Free disk space: 43,854 MB

Temp path: C:\Documents and Settings\tonyg\Local Settings\Temp\

Free temp space: 43,854 MB

Error ID: 5663

Error detail: SQLiteException: The database disk image is malformed

database disk image is malformed

System.Data.SQLite.SQLiteException: The database disk image is malformed

database disk image is malformed

at System.Data.SQLite.SQLite3.Reset(SQLiteStatement 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.ExecuteDbDataReader(CommandBehavior behavior)

at System.Data.Common.DbCommand.System.Data.IDbCommand.ExecuteReader()

at Libronix.Utility.Data.PoolableConnector.ExecuteReader(String strText, Object[] aobjParameterNamesAndValues)

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)

Bradley Grainger (Logos)

https://community.logos.com/discussion/comment/369012#Comment_369012

Try deleting this file, then restarting Logos 4:

C:\Documents and Settings\tonyg\Local Settings\Application Data\Logos4\Data\b1vffapa.kfb\Updates\Metadata.db

Tony Gerber

https://community.logos.com/discussion/comment/369039#Comment_369039

Thanks Bradley, deleting the "metadata.db" file seems to have done the trick. I'm extraordinarily grateful for your assistance and input.