Logos 4 start up Issue in Windows XP
Can't start Logos 4 in Windows XP. Please advice.
Comments
-
Yin Fung said:
Can't start Logos 4 in Windows XP. Please advice.
Yin, welcome to the forums. In the other thread you posted to you even gave more information than here and have received the first initial answers. Have you checked and upgraded your XP service pack level (Logos seems to require SP 3 and you told you are on SP 2)?
Which version of Logos do you have? 4.3 SR-1 should be current - reinstall from the support page or from Logos.com/4ways
Run Logos with diagnostic logging (search the wiki for it) enabled and post the logs here
A lot of people here will try to help you, but we need to have information and you need to work with us to nail this down step by step (or you may as well call Customer Service, who may be able to log on remotely onto your machine).
Mick
Have joy in the Lord!
0 -
Thanks Mick, my XP is actually SP3. According to the following config file info:
# This script installs the .NET Framework 3.5 SP 1 (version 3.5.30729.00), Logos4Prerequisites.msi version 4.21.10099 and Logos4.msi version 4.22.51109|result=success
# The Logos 4 prerequisites version is 4.21.5.0099, the Logos 4 version is 4.22.5.1109 the version title is "4.2b SR-1"|result=success
# The Help About version is "4.2b SR-1"|result=success
It seems I am using 4.2b DR-1. Can you please send me the link for 4.3 SR-1 download?
0 -
Yin Fung said:
It seems I am using 4.2b DR-1. Can you please send me the link for 4.3 SR-1 download?
Yin,
I hope it's at http://downloads.logos.com/LBS4/LDLS4Installer/Logos4Setup.exe (see http://www.logos.com/windows/support/install for instructions). Until last week I would have been very confident that this loads always the latest version, but you should make sure during installation, as someone claimed just recently that he/she received an old 4.2 installer from the Logos site (maybe there was glitch at the server).
Wish you all the best!
Mick
Have joy in the Lord!
0 -
Yin Fung said:
It seems I am using 4.2b DR-1. Can you please send me the link for 4.3 SR-1 download?
Try http://downloads.logos.com/LBS4/LDLS4Installer/Logos4Setup.exe
Graham
Edit: Apologies for the duplicate post!
0 -
Thanks All for the info. I downloaded the exe but after I ran it, it said I am up to date
Any file that I can check to make sure I am in 4.3 SR-1. I suspect that I download the 4.2 instead ... Regards.
0 -
I tried to re-install but came across the same error ....
0 -
Hi Yin
You need to read the wiki to get more information on Logos4, but here's a start --> http://wiki.logos.com/How_can_I_tell_what_version_I%27m_running$3f
If you have problems it's necessary to post some logs so this article will tell you all about it (click on the blue words).
Dave
===Windows 11 & Android 13
0 -
Maybe they had a server problem over at Logos and put a backup back up?
I don't know how far along the software tries to start - fire it up while holding the CTRL key and turn on logging (see http://wiki.logos.com/Diagnostic_Logging for details) and post the log files here.
If all else fails, you may need to wait for Customer Service to start their day aand give them a call.
Mick
Edit: Just so you know, it's the same article that Dave just linked to. I got to run into my workday now over here in Europe, hope you'll be fine when I check back into the forum.
Have joy in the Lord!
0 -
Here is the crash log file:
Program Version: 4.3 SR-1 (4.30.0.1553)
Windows Version: 5.1.2600.196608
Time: 2011-08-22 00:12:55
Installed memory: 2,031 MB
Install path: F:\Logos4\System\Logos4.exe
Data path:
0 -
Thanks, hope u have a great day!
0 -
This seems to be just part of the file - please try to attach it as a file and also try to run Logos in "diagnostic logging"-mode and upload this extensive log as explained in the wiki page Dave and I have referred you to. The verbose logs generated by the application will allow the "gurus" here to nail down your error.Yin Fung said:Program Version: 4.3 SR-1 (4.30.0.1553)
Windows Version: 5.1.2600.196608
Time: 2011-08-22 00:12:55
Installed memory: 2,031 MB
Install path: F:\Logos4\System\Logos4.exe
Data path:
One thing you probably saw yourself: Now you do have the latest version installed.
Mick
Have joy in the Lord!
0 -
Thanks for your information, I will run the log and attached it tmr. Have a good day!
0 -
Here is the log ... It looks like we have System.BadImageFormatException:
2011-08-23 23:50:46.6718 1 Info OurApp Starting application (4.3 SR-1, version 4.30.0.1553 on Microsoft Windows NT 5.1.2600 Service Pack 3) at 1.115 seconds.
2011-08-23 23:50:47.6562 1 Info OurApp WPF rendering tier 2; targeting 20 FPS.
2011-08-23 23:50:47.8281 1 Info OurApp Auto-detected UI language: en-US
2011-08-23 23:50:47.8281 1 Info OurApp Culture.Current.LanguageName: en-US
2011-08-23 23:50:47.8281 1 Info OurApp Loading application XAML.
2011-08-23 23:50:52.6718 1 Info OurApp Running application.
2011-08-23 23:50:52.9843 1 Info OurApp Creating AppModel.
2011-08-23 23:50:53.2500 1 Error OurApp Unhandled exception: System.BadImageFormatException: Invalid access to memory location. (Exception from HRESULT: 0x800703E6)
at Libronix.DigitalLibrary.UserManager..ctor(String strUserManagerFolder)
at Libronix.DigitalLibrary.UserManager.CreateCommon()
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)
0 -
Yin Fung said:
Here is the log ... It looks like we have System.BadImageFormatException:
Yin, if you do not receive a reply from Logos in the next 24 hrs I would advise you to contact Technical Support (phone or email tech@logos.com) and quote this thread.
Dave
===Windows 11 & Android 13
0 -
Great, thanks!
0 -
Yin, it would probably be best if you could call Customer Support, like Dave suggested.
1-800-875-6467 M-F 6am-5pm Pacific Time
0
