Logos 4 will not start
I keep getting the following message:
"Logos Bible software 4 has stopped working"
Here is my log file
Program Version: 4.0c (4.03.3.9511)
Windows Version: 6.1.7601.65536
Time: 2012-10-27 22:04:29
Installed memory: 2,939 MB
Install path: C:\Users\Claude Jr\AppData\Local\Logos4\System\Logos4.exe
Data path:
Free disk space: 49,891 MB
Temp path: C:\Users\Claude Jr\AppData\Local\Temp\
Free temp space: 49,891 MB
Error ID: 2369
Error detail: DatabaseVersionException: The database schema (6) is newer than the latest schema recognized by this code (5). The database cannot be opened.
Libronix.Utility.Data.DatabaseVersionException: The database schema (6) is newer than the latest schema recognized by this code (5). The database cannot be opened.
at Libronix.Utility.Data.LocalFileDatabase.VerifySchemaVersion(Int64 nDatabaseSchemaVersion, Int64 nCurrentSchemaVersion)
at Libronix.DigitalLibrary.PreferencesManager.<.ctor>b__0(IConnector conn)
at Libronix.Utility.Data.LocalFileDatabase..ctor(String strPath, Func`2 fnCreateConnection, Func`2 fnValidateDatabase, Action`1 fnCreateDatabase)
at Libronix.DigitalLibrary.PreferencesManager..ctor(String strPreferencesManagerFolder)
at Libronix.DigitalLibrary.Utility.DigitalLibraryServices.CreateLocalUserPreferences()
at Libronix.Utility.LazyObject`1.get_Value()
at Libronix.DigitalLibrary.Utility.DigitalLibraryServices.get_LocalUserPreferences()
at LDLS4.AppStartupModel.Run()
at LDLS4.AppModel.Run()
at LDLS4.OurApp.OnStartup(StartupEventArgs e)
at System.Windows.Application.<.ctor>b__0(Object unused)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Boolean isSingleParameter)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Boolean isSingleParameter, Delegate catchHandler)
at System.Windows.Threading.Dispatcher.WrappedInvoke(Delegate callback, Object args, Boolean isSingleParameter, Delegate catchHandler)
at System.Windows.Threading.DispatcherOperation.InvokeImpl()
at System.Windows.Threading.DispatcherOperation.InvokeInSecurityContext(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.Windows.Threading.DispatcherOperation.Invoke()
at System.Windows.Threading.Dispatcher.ProcessQueue()
at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
at MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
at MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Boolean isSingleParameter)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Boolean isSingleParameter, Delegate catchHandler)
at System.Windows.Threading.Dispatcher.WrappedInvoke(Delegate callback, Object args, Boolean isSingleParameter, Delegate catchHandler)
at System.Windows.Threading.Dispatcher.InvokeImpl(DispatcherPriority priority, TimeSpan timeout, Delegate method, Object args, Boolean isSingleParameter)
at System.Windows.Threading.Dispatcher.Invoke(DispatcherPriority priority, Delegate method, Object arg)
at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam)
at MS.Win32.UnsafeNativeMethods.DispatchMessage(MSG& msg)
at System.Windows.Threading.Dispatcher.PushFrameImpl(DispatcherFrame frame)
at System.Windows.Threading.Dispatcher.PushFrame(DispatcherFrame frame)
at System.Windows.Threading.Dispatcher.Run()
at System.Windows.Application.RunDispatcher(Object ignore)
at System.Windows.Application.RunInternal(Window window)
at System.Windows.Application.Run(Window window)
at System.Windows.Application.Run()
at LDLS4.OurApp.InitializeAndRun(ReadOnlyCollection`1 listArgs, SingleInstanceManager sim)
at LDLS4.OurApp.Main(String[] astrArgs)
Comments
-
Hi Claude
Most likely you need to upgrade your software to 4.6+ : http://downloads.logos.com/LBS4/Installer/Logos4Setup.exe
That generally will get you back in business (you've got some newer databases but older software).
"If myth is ideology in narrative form, then scholarship is myth with footnotes." B. Lincolm 1999.
0 -
I get a message that says the software is up to date. The program still will not open.
0 -
Claude Brown Jr said:
I get a message that says the software is up to date.
Claude – You might have a message that says you are "up to date," but your software is more than two years old!Claude Brown Jr said:Program Version: 4.0c (4.03.3.9511)
4.0c came out in May of 2010!Here is a list of Logos releases:
0 -
0
-
Claude Brown Jr said:
I see what you mean. Here is the crash file and it indicates that the version is up to date?
Claude, please don't paste such big files. In future you should upload them.
Can you start with a blank layout (hold CTRL down whilst you start L4)? Try deleting the first Word Find Puzzle (if any) in the Files folder and restart L4
Otherwise, it would be best to wait until Monday and contact Logos Support.
Dave
===Windows 11 & Android 13
0 -
Sorry after spending hundreds of dollars for software that continually stops responding as expected and then told to make self-repairs drives me a little nuts. I will try to remember to use additional software to report to others the problems I am having with software provided by someone else.
I am very appreciative to everyone who tries to help, just frustrated as this software has been buggy and slow from initial purchase with no end of glitches in sight.
0 -
Claude Brown Jr said:
Sorry after spending hundreds of dollars for software that continually stops responding as expected and then told to make self-repairs drives me a little nuts. I will try to remember to use additional software to report to others the problems I am having with software provided by someone else.
I am very appreciative to everyone who tries to help, just frustrated as this software has been buggy and slow from initial purchase with no end of glitches in sight.
Personally Thankful for many friendly forum discussions about using Logos Bible Software; have learned a lot plus have a lot to learn.
Appreciate frustration; Logos 4 is resource intensive on Mac & PC – benefits from fast processor, graphics, and quick storage along with adequate memory (i.e. newer hardware since Logos 4 being designed for use over 5 to 8 years); Solid State Disk (SSD) is noticeably faster than hard disk.
Noticed contents of Logos4Error.log that was posted into reply shows 9 crashes with visual filters and word find. Wondering if have been using Logos 4 for awhile ? Curious if trying to copy a Logos 4 installation from one computer to another ?
For interaction with other Logos users, who volunteer their time to assist, attaching diagnostic logs file(s) would be appreciated instead of contents being pasted into a forum reply, which is challenging to read in a web browser plus a bit awkward for scrolling. The forum editor has a paper clip, which can be used to attach files.
Keep Smiling [:)]
0 -
Yes I have been using Logos 4 since July 2010.0160.Logos4Crash.txt
0 -
No have been using the same computer all of the time, however I will be looking into changing over to a portable SSD if that will really help.
0 -
Hello Claude,
I'm sorry that you're having problems with Logos 4. Can you please set up logging and repeat the behavior to cause Logos 4 to crash, and then post the logs here? Here are instructions for grabbing logs: www.logos.com/support/windows/L4/logging
0
