Logos Bible Software 5 has stopped working - .Net Exceptions preventing access to software during st
I've tried opening Logos and keep getting "Logos Bible Software 5 has stopped working". This has occured since the latest update installed. I tried all recommendations on correcting the issue under article "What to do is Logos Crashes" however of course that is limited as I cannot actually get into the program to rebuild the index etc. I have also followed the "Report a Problem in Logos for Windows" and unfortunately no "Logos Log Files" are created so I cannot give them to you either.
To rule out issues I uninstalled Logos and reinstalled. When it had reinstalled, downloaded resources and reindexed the problem reoccured. I have updated all Windows Updates to rule out an issue there. Below are the exceptions provided, and you will note each time it opens I get a different exception number:
An unhandled Microsoft .Net Framework exception occured in Logos.exe [6612]
An unhandled Microsoft .Net Framework exception occured in Logos.exe [800]
An unhandled Microsoft .Net Framework exception occured in Logos.exe [4868]
An unhandled Microsoft .Net Framework exception occured in Logos.exe [4164]
An unhandled Microsoft .Net Framework exception occured in Logos.exe [2588]
There is no static response so I moved to checking the Event Logs. Below are two copies of the events that occur:
Event 1025:
Application: Logos.exe
Framework Version: v4.0.30319
Description: The application requested process termination through System.Environment.FailFast(string message).
Message: Unhandled exception in async work
Stack:
at System.Environment.FailFast(System.String, System.Exception)
at Libronix.Utility.ApplicationUtility.FailFast(System.String, System.Exception)
at Libronix.Utility.Threading.AsyncWorkerTask`1[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].EnumMoveNext()
at Libronix.Utility.Threading.AsyncWorkerTask`1[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].ContinueExecution(System.Object)
at Libronix.Utility.Threading.GroupedThreadPool.ExecuteNextCallback(System.Object)
at System.Threading.QueueUserWorkItemCallback.WaitCallback_Context(System.Object)
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
at System.Threading.ThreadPoolWorkQueue.Dispatch()
at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback()
Event 1000:
Faulting application name: Logos.exe, version: 5.2.2.1584, time stamp: 0x544a7515
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0x80131623
Fault offset: 0x0fecb34f
Faulting process ID: 0x1304
Faulting application start time: 0x01cffb38ae86677b
Faulting application path: C:\Users\Stephen\AppData\Local\Logos5\System\Logos.exe
Faulting module path: unknown
Report ID: 4e61094a-672c-11e4-bebc-00400510bfa1
Faulting package full name:
Faulting package-relative application ID:
Event 1000:
Faulting application name: Logos.exe, version: 5.2.2.1584, time stamp: 0x544a7515
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0x80131623
Fault offset: 0x0e334d1f
Faulting process ID: 0x1044
Faulting application start time: 0x01cffb3921b865c2
Faulting application path: C:\Users\Stephen\AppData\Local\Logos5\System\Logos.exe
Faulting module path: unknown
Report ID: 8af1c4ac-672c-11e4-bebc-00400510bfa1
Faulting package full name:
Faulting package-relative application ID:
Event ID 1025:
Application: Logos.exe
Framework Version: v4.0.30319
Description: The application requested process termination through System.Environment.FailFast(string message).
Message: Unhandled exception in async work
Stack:
at System.Environment.FailFast(System.String, System.Exception)
at Libronix.Utility.ApplicationUtility.FailFast(System.String, System.Exception)
at Libronix.Utility.Threading.AsyncWorkerTask`1[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].EnumMoveNext()
at Libronix.Utility.Threading.AsyncWorkerTask`1[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].ContinueExecution(System.Object)
at Libronix.Utility.Threading.GroupedThreadPool.ExecuteNextCallback(System.Object)
at System.Threading.QueueUserWorkItemCallback.WaitCallback_Context(System.Object)
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
at System.Threading.ThreadPoolWorkQueue.Dispatch()
at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback()
Comments
-
I forgot to mention that I use the Windows 8.1 operating system. The computer uses an Intel Pentium Core2 6420 2.13Ghz CPU and has 8GB of DDR2 667Mhz RAM which is fully tested. It has no problems with any other programs and is operating without any other issues. I have MS Visual Studio 2012 on the system if that proves helpful in any way.
0 -
Stephen Challen said:
I have also followed the "Report a Problem in Logos for Windows" and unfortunately no "Logos Log Files" are created so I cannot give them to you either.
Did you try step 4 at https://www.logos.com/support/logos6/windows/report-problem - and, if so, what happened?
We really need to be able to see some Logos logs for this one.
0 -
Step 4: "Setup" Logging (Installation Problems)
As you will note I have had no problems with installing Logos. The problem experienced was experienced after many months of usage, and not related to installation. I chose to reinstall and the re-installation worked fine. The problem unfortunately just rebuilt itself after re-installation.That said I suppose you're suggesting that the problem is that the update did not install correctly and that the latest installation has repeated the same installation problem.
I will give it a go but I have to get on and struggle to get preparation done today using http://biblia.com. I will have to give time to resolving this issue during the coming week.
I have only used this program for 1 year and a lot of money has been invested in it. Unfortunately our other Pastor has had problems himself with different issues as a consequence of the same update which the team has spent a couple of days sorting through remote control. So at this point as we were looking at upgrading to Logos 6 I have to say my faith in the system has dropped dramatically, and my heart drops seeing the Logos 6 crashing reports being posted too.
I gave up posting reports on problems experienced with Proclaim due to the amount of time it was taking with little resolution. I have a long list of issues and changes required to report on Proclaim and wondering if our investment last year was as wise as we had thought.
So in summary I'm having a bad day and need to get past today's workload and return to this with a better less emotional frame of mind. I do however appreciate all comments and help and will read and follow up on them once I everything done. Unfortunately the day will be one of facing both Logos and Proclaim issues and may well be posting all the issues I have as the day wears on. [:)]0 -
Stephen Challen said:
As you will note I have had no problems with installing Logos. The problem experienced was experienced after many months of usage, and not related to installation. I chose to reinstall and the re-installation worked fine. The problem unfortunately just rebuilt itself after re-installation.
That said I suppose you're suggesting that the problem is that the update did not install correctly and that the latest installation has repeated the same installation problem.
I understand that and not suggesting where the problem lies at all. I am suggesting that this is a way of enabling logging so we can try and determine what is going on.
Stephen Challen said:So at this point as we were looking at upgrading to Logos 6 I have to say my faith in the system has dropped dramatically, and my heart drops seeing the Logos 6 crashing reports being posted too
I would also point out that people are using Logos 6 and finding it very helpful. The nature of forums like these is that we tend to get problems reported.[:)]
Stephen Challen said:Unfortunately the day will be one of facing both Logos and Proclaim issues and may well be posting all the issues I have as the day wears on.
Please do feel free to post with any issues you experience.
0 -
After installing Logos 6- Microsoft Office 10 and Acrobat Professional, both are not working, as well as all security updates to NET are failing; this ONLY happened after L6 update to NET.
Have not heard back from Microsoft, cannot figure out how to get Office and Professional working again, clicking icon only starts a 'windows installer' function that fails, I get same result clicking the Acrobat icon.
0 -
Whyndell Grizzard said:
After installing Logos 6- Microsoft Office 10 and Acrobat Professional, both are not working, as well as all security updates to NET are failing; this ONLY happened after L6 update to NET.
Sorry to hear this but - if you think this is Logos-related - I suggest you start a separate thread in the Logos 6 forum.
0 -
Sorry didn't see "5" [:$]
0 -
Stephen Challen said:
As you will note I have had no problems with installing Logos. The problem experienced was experienced after many months of usage, and not related to installation. I chose to reinstall and the re-installation worked fine. The problem unfortunately just rebuilt itself after re-installation.
There is a similar failure in this thread and the steps taken may help you.
Dave
===Windows 11 & Android 13
0 -
Graham Criddle, Thanks for the reply. Will let you know how I get on with your idea.
Dave Hooton, Thanks for link. The link is however for Logos 6 and relates to issues once the program has finally opened. Will consider but the crash occurs just as it shows my Logos Layout. I will consider font cache and other aspects which I find I can do and see what happens.
Just to confirm I cannot use the software to reset layout, change layout, run reindex or any other tasks because I literally cannot use Logos in any way. All similar occurrences I've found of .net exceptions are when someone carries out a task once carrying out a task after Logos has opened. Please correct me if I'm wrong.0 -
I think somehow my .net Framework has been damaged by the latest update from Logos. Ran the repair tool and it has recommended reinstalling the .net framework and then subsequently did same crash
http://www.microsoft.com/en-gb/download/details.aspx?id=301350 -
Reinstalled .NET Framework and problem remains.
0 -
If you normally open to a layout it may be something in the layout. Have you tried opening to a Blank layout i.e. hold CTRL key whilst starting Logos and select the option? You should rebuild the layout.
What version of .NET do you have?
Dave
===Windows 11 & Android 13
0 -
Open Logos 5 to a blank layout; then in the command box (at the top of the program) enter "open Bible Facts to Jesus". This will reset the internal state of Bible Facts that is causing the crash.
0 -
Stephen: I'm having a very similar issue with Windows 8.1/Logos 5. Were you able to get to the bottom of it?
0 -
Thank you for the responses.
Dave, I have the latest version of .NET
Scott, hopefully this reply proves helpful to you.
Bradley, after a very tough week which included the funeral of a 9 year old boy who attended our Sunday School, I have now had time to follow up on this issue. I can confirm that today I changed my login email address, but do not think that has affected the issue in any way. I pressed CTRL and launched Logos using my new email login address and selected "Blank Layout". I was able to then install a new update which rebooted the program when installed. I then returned to my previous layout and the problem has been resolved. All is now working as normally expected.0
