Logos & Noet Bible Software Has Stopped Working

I started having this problem today (July 18, 2016) with Logos 6.

I had this problem before and finally someone at Logos pointed me a .NET Framework file that I needed to install to make it work. I tried that file today and did a repair, but still having the same problem - "Logos Bible Software Has Stopped Working," and "Noet Has Stopped Working."

This is very disconcerting that a program of this caliber would experience these kinds of problems constantly.

Why is this an ongoing problem with this software?
I have experienced this same problem since Logos 3.

Find more posts tagged with

Comments

JT (alabama24)

You will need to enable and post logs to determine why. See my signature line

Bob Bacle

https://community.logos.com/discussion/comment/833166#Comment_833166

What do you mean by "see my signature line?"
What is a signature line?

And how do I send log files to you?
I have them zipped up.

Dave Hooton

https://community.logos.com/discussion/comment/833168#Comment_833168

What do you mean by "see my signature line?"

The line at the bottom of his post with links for PC and Mac logs.

And how do I send log files to you?

Attach them to a post using the Paperclip icon.

Bob Bacle

https://community.logos.com/discussion/comment/833177#Comment_833177

800624.Logos Log Files.zipOK...here are the log files.

Dave Hooton

https://community.logos.com/discussion/comment/833179#Comment_833179

Not so! Try again

EDIT: ok. Try to fix it by installing the Visual C++ 2013 Redistributable: http://www.microsoft.com/en-us/download/details.aspx?id=40784

Bob Bacle

https://community.logos.com/discussion/comment/833180#Comment_833180

Did that but still won't load.

Getting this information when trying to open the program:

Problem signature:

Problem Event Name: CLR20r3

Problem Signature 01: Logos.exe

Problem Signature 02: 6.13.0.20

Problem Signature 03: 577bdbdc

Problem Signature 04: mscorlib

Problem Signature 05: 4.6.1076.0

Problem Signature 06: 56d79d90

Problem Signature 07: 10fb

Problem Signature 08: 3d

Problem Signature 09: System.IO.FileLoadException

OS Version: 6.1.7601.2.1.0.256.1

Locale ID: 1033

Additional Information 1: af7f

Additional Information 2: af7f3c3468e432cee89db749af004e9e

Additional Information 3: c589

Additional Information 4: c58914315b2e441f09ab39dcd3f5c548

Bradley Grainger (Logos)

https://community.logos.com/discussion/comment/833179#Comment_833179

OK...here are the log files.

System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.Configuration.ConfigurationErrorsException: An error occurred creating the configuration section handler for system.serviceModel/commonBehaviors: Could not load file or assembly 'Microsoft.VisualStudio.Diagnostics.ServiceModelSink, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. Access is denied. (C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Config\machine.config line 238) ---> System.IO.FileLoadException: Could not load file or assembly 'Microsoft.VisualStudio.Diagnostics.ServiceModelSink, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. Access is denied.

at System.RuntimeTypeHandle.GetTypeByName(String name, Boolean throwOnError, Boolean ignoreCase, Boolean reflectionOnly, StackCrawlMarkHandle stackMark, IntPtr pPrivHostBinder, Boolean loadTypeFromPartialName, ObjectHandleOnStack type)
at System.RuntimeTypeHandle.GetTypeByName(String name, Boolean throwOnError, Boolean ignoreCase, Boolean reflectionOnly, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean loadTypeFromPartialName)
at System.RuntimeType.GetType(String typeName, Boolean throwOnError, Boolean ignoreCase, Boolean reflectionOnly, StackCrawlMark& stackMark)
at System.Type.GetType(String typeName, Boolean throwOnError)
at System.ServiceModel.Configuration.ServiceModelExtensionCollectionElement`1.GetExtensionType(ContextInformation evaluationContext, String name)
at System.ServiceModel.Configuration.ServiceModelExtensionCollectionElement`1.CreateNewSection(String name)
at System.ServiceModel.Configuration.ServiceModelExtensionCollectionElement`1.DeserializeElementCore(XmlReader reader)
at System.Configuration.ConfigurationElement.DeserializeElement(XmlReader reader, Boolean serializeCollectionKey)
at System.Configuration.RuntimeConfigurationRecord.RuntimeConfigurationFactory.CreateSectionImpl(RuntimeConfigurationRecord configRecord, FactoryRecord factoryRecord, SectionRecord sectionRecord, Object parentConfig, ConfigXmlReader reader)
at System.Configuration.RuntimeConfigurationRecord.RuntimeConfigurationFactory.CreateSectionWithFullTrust(RuntimeConfigurationRecord configRecord, FactoryRecord factoryRecord, SectionRecord sectionRecord, Object parentConfig, ConfigXmlReader reader)
at System.Configuration.RuntimeConfigurationRecord.CreateSection(Boolean inputIsTrusted, FactoryRecord factoryRecord, SectionRecord sectionRecord, Object parentConfig, ConfigXmlReader reader)
at System.Configuration.BaseConfigurationRecord.CallCreateSection(Boolean inputIsTrusted, FactoryRecord factoryRecord, SectionRecord sectionRecord, Object parentConfig, ConfigXmlReader reader, String filename, Int32 line)

I have never seen this particular crash message before. My best guess is that the Microsoft .NET Framework is misconfigured or corrupted on your system. This is a Microsoft technology that Logos depends on in order to function. If it's not installed correctly, Logos cannot work.

Since you're on Windows 7, you might try the .NET Framework Repair Tool to see if that helps: https://www.microsoft.com/en-us/download/details.aspx?id=30135

Did you install any software or system updates recently? Rolling back to a System Restore point before this happened might help.

Otherwise, please call our technical support department and reference this thread, and they should be able to help you repair .NET on your computer.

Bradley Grainger (Logos)

https://community.logos.com/discussion/comment/833207#Comment_833207

One final thing: have you rebooted your computer recently? If not, try that first.

Bob Bacle

https://community.logos.com/discussion/comment/833208#Comment_833208

Yes, I rebooted when I installed the Visual C++ 2013 redistributable.

That didn't help.

Bob Bacle

https://community.logos.com/discussion/comment/833207#Comment_833207

Nothing has worked thus far.

I cannot believe that your program depends so much on .NET framework from MS.
Why can't you have the program written where it does NOT depend on MS code?

This has been a problem with your program for several years.
I have experienced this problem since Logos 3, and other people are experiencing the same problem.

It looks like you would address these problems and NOT depend on MS code so that your program would work flawlessly.
e-Sword works with .NET framework, and other Bible software programs work without .NET framework code from MS.
Why can't you write something that does NOT depend on MS code so that it will work all the time?

I am getting totally disgusted with this program.
Over and over again I face this problem, and all you can tell me is to repair .NET framework or to do a system restore or to call your technical department.

I have done all of these things before more than once and I am still experiencing this problem time and time again.

MJ. Smith

https://community.logos.com/discussion/comment/833223#Comment_833223

I cannot believe that your program depends so much on .NET framework from MS.
Why can't you have the program written where it does NOT depend on MS code?

This is next to impossible - I know of no company providing application programs that writes its own operating system except Microsoft and Apple. Most of us do not experience the problems that you are. There is something different on your machine than the "standard machine". Often these differences are unintentional or are the result of two separate applications you are running being incompatible - most often this happens with advertisement popup suppression or firewall settings. I know it gets very frustrating ... what it likely your best approach is to call customer service and let them access your machine remotely to identify the problem. You may not like the answer "to repair .NET framework or to do a system restore or to call your technical department" but that is the actual solution to your problem. The most I could hope to do on the forums at this point is to help you understand why that is the answer and why that does not reflect poorly on the Logos product itself.