Logos 4 doesn't start

Hi there,

This morning my Logos4 didn't start. I run the programm, I got directly a message 'Logos4 doesn't work any longer.'

So I uninstalled Logos4 and re-installed it with Logos4Setup.exe. But after re-install nothing changed.

I also uninstalled my antivir-programms, but till now Logos4 doesn't work.

This is what I get:

Beschrijving:
Stopped working

Probleemhandtekening:
Gebeurtenisnaam van probleem:    CLR20r3
Probleemhandtekening 01:    logos4.exe
Probleemhandtekening 02:    4.61.0.3380
Probleemhandtekening 03:    50b553eb
Probleemhandtekening 04:    Logos4
Probleemhandtekening 05:    4.61.0.3380
Probleemhandtekening 06:    50b553eb
Probleemhandtekening 07:    2a7
Probleemhandtekening 08:    154
Probleemhandtekening 09:    System.IO.FileLoadException
Versie van besturingssysteem:    6.0.6002.2.2.0.768.3
Landinstelling-id:    2067

Lees onze privacyverklaring:
http://go.microsoft.com/fwlink/?linkid=50163&clcid=0x0413

Any suggestion?

Find more posts tagged with

Comments

Graham Criddle

Hi RRH

Can you enable diagnostic logging and update logs as per http://wiki.logos.com/Diagnostic_Logging?

Graham

RRH

https://community.logos.com/discussion/comment/439313#Comment_439313

Hi Graham,

I tried this, but it didn't work. Holding CTRL+Opening the program gives the same error.

I also tried to start the program in Windows Safety-mode, but same error.

Really strange.

Graham Criddle

https://community.logos.com/discussion/comment/439315#Comment_439315

I tried this, but it didn't work. Holding CTRL+Opening the program gives the same error.

Yes, it will give the same error but hopefully it will generate some logs.

Have you checked whether any have been created?

RRH

https://community.logos.com/discussion/comment/439318#Comment_439318

Hi Graham,

I found this Log:

Program Version: 4.6a SR-4 (4.61.0.3380)
Windows Version: 6.0.6002.131072
Time: 2012-12-10 12:53:07 +01:00 (2012-12-10T11:53:07Z)
Installed memory: 2,813 MB
Install path: \Programmas Bijbel\Logos4\System\Logos4.exe
Free install space: 111,162 MB
Temp path: C:\Users\Raymond\AppData\Local\Temp\
Free temp space: 189,472 MB

Error ID: 4759
Error detail: FileLoadException: Could not load file or assembly 'System.ServiceModel, Version=3.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' or one of its dependencies. Signature specified is zero-sized. (Exception from HRESULT: 0x80131237)

System.IO.FileLoadException: Could not load file or assembly 'System.ServiceModel, Version=3.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' or one of its dependencies. Signature specified is zero-sized. (Exception from HRESULT: 0x80131237)
File name: 'System.ServiceModel, Version=3.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' ---> System.Runtime.InteropServices.COMException (0x80131237): Signature specified is zero-sized. (Exception from HRESULT: 0x80131237)
   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)

Logos4Error.zip

RRH

https://community.logos.com/discussion/comment/439322#Comment_439322

Anyone?

RRH

https://community.logos.com/discussion/comment/439360#Comment_439360

Ok, I restored my Windows Vista to an earlier recovery-point.

After launching Logos4, I got the login-screen. Everything, till there went fine.

Now Logos is downloading resources.

Hopefully I do not come to a dead end after download-proces (8GB!).

Graham Criddle

https://community.logos.com/discussion/comment/439392#Comment_439392

Ok, I restored my Windows Vista to an earlier recovery-point.

After launching Logos4, I got the login-screen. Everything, till there went fine.

Now Logos is downloading resources.

Hopefully I do not come to a dead end after download-proces (8GB!).

Glad things are moving forward - hope everything works.

If you need to upload logs again please load the full logs using the paperclip icon as opposed to posting an extract. It makes it so much easier to work out what is going on

Graham

RRH

https://community.logos.com/discussion/comment/439399#Comment_439399

No, not working...

First it was possible to start Logos4. But there were no books inside. So I restarted my PC. After this, following things happen:

I click on the Logos4 icon. A window appears that my Logos4 should be updated. I click update and a message pops up: 'Logos4 is up-to-date'. Then Logos4 starts, but it is no longer possible for me to login. In the meantime Logos4 start indexing. But then, again a Windowsmessage appears after some seconds: 'Logos Bible Software Indexer no longer works'. The directly Logos4 starts. But without any books

I will include the files in attachment6567.Logos4Indexer.zip.

RRH

https://community.logos.com/discussion/comment/439444#Comment_439444

...now Logos4 is indexing longer then first, without error.

Dave Hooton

https://community.logos.com/discussion/comment/439452#Comment_439452

You've rolled back to a really old version 4.0a and you need to update to the latest --> http://downloads.logos.com/LBS4/Installer/Logos4Setup.exe

RRH

https://community.logos.com/discussion/comment/439519#Comment_439519

I discovered that an old and new version of Logos4 was installed in different folders. Renamed/Deleted the old one and now everything works fine. But this double installation was not the problem from the beginning. It appeared after recovering Windows. Then I forgot to de-install Logos4.

So only solution was: recover windows to an earlier time. De-install Logos4. Re-install Logos4.