CLR 80004005 error

I have been using Logos for a few years now, and I just had to reinstall my OS (Win 7) and when I attempted to install Logos 6, it gave me the 80004005 error upon trying to launch it, which means it would not even open.
So I uninstalled it, tried Logos 5, and it gave me the same error.
Then I went all the way back to Logos 4, and it installed fine and downloaded all my books.
Now how do I get Logos 6 to install?
I have been reading on these forums and this error has been going on since Logos 5, and it still persists in Logos 6, and has not been fixed yet.
BTW, I have tried all the solutions (uninstalling the NET framework, reinstalling it, etc., etc.) and nothing has worked.
I have reinstalled my OS 3 times to see if there was a problem with it, but I get the same error.
Comments
-
80004005 is a generic error code, so we would need more details (e.g., from Windows Event Viewer) to diagnose the exact cause of the error and recommend specific steps to get Logos 6 installed.
At a minimum, you'll need to ensure that Windows 7 SP1 and all the latest Windows updates are installed first. (Personally, I'd recommend taking the free update to Windows 10 while Microsoft is still offering it.)
0 -
If you can tell me how to give you the Event Viewer info, I would be glad to give it to you.
As far as Win10 is concerned, I am on a multiboot machine with WinXP, Win7, & Win10 installed, so I already know about Windows 10 and I have it. When I installed the Logos software on Win10, I got several errors also, but it finally did install (sort of). I finally gave up on it being so slow on downloading my books and indexing them (I waited for 8 hours for it to finish and it never did on Win10).
Logos and Noet have to be the slowest Bible programs in the world, and I am running a Quad-core with 8GB of RAM on a 1TB HD.
I was having problems with my Win7, so I reinstalled the OS fresh, and ever since I have been having this error code when I attempt to install & run Logos 6. It was working fine before on Win7, so why is it not working now that I have reinstalled the OS & all the updates? As I said I reinstalled the OS 3 times and got this error every time.
There has to be a solution since Logos 4 installs fine, but Logos 5 & Logos 6 give me this error.
0 -
Bob Bacle said:
If you can tell me how to give you the Event Viewer info, I would be glad to give it to you.
There are instructions here: Tip: How to use event viewer to diagnose Logos crashes
This is my personal Faithlife account. On 1 March 2022, I started working for Faithlife, and have a new 'official' user account. Posts on this account shouldn't be taken as official Faithlife views!
0 -
OK...I did as you said in the Event Viewer, but there were no errors there for the Logos program. All there was were 2 Net Runtime Version errors (both identical).
So what do I do next? Is there a solution? Other people have been experiencing the same problem since Logos 5 with no solution as of yet.
Are you going to give us a fix for this problem? Thx.0 -
Can you paste the error messages that you do see?
Also, try the .NET repair tool to help ensure .NET errors are not causing the problem: https://support.microsoft.com/en-gb/kb/2698555
This is my personal Faithlife account. On 1 March 2022, I started working for Faithlife, and have a new 'official' user account. Posts on this account shouldn't be taken as official Faithlife views!
0 -
OK...I ran the Net repair tool and now the CLR 80004005 error does not come up.
But now I am getting something new - the program crashes upon launch and all it allows me to do is to close the program.Here is the error found in Event Viewer:
Application: Logos.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.IO.FileLoadException
at Libronix.DigitalLibrary.UserManager..ctor(System.String)
at Libronix.DigitalLibrary.UserManager.CreateCommon()
at LDLS4.OurApp.AddUnhandledExceptionHandler()
at LDLS4.OurApp.Main(System.String[])
Any solutions to this?
0 -
We still need a little more information than this to track this down. If you have a LogosError.log file in Documents\Logos Log Files, please zip and upload it. Otherwise, please contact technical support, reference this thread, and ask them to collect crash dump information for Development.
0 -
Thank you, but where is the Log file?
I can't find it anywhere - I have searched under my username in the documents folder and in the Logos folder in AppData/Logos and there is no log file there.0 -
There may not be a log file.
I recommend calling technical support and having them help you collect a crash dump.
0