Bug: Logos crashing on startup
Installed the latest beta while trying to update an expired version of Mcafee. Mcafee is still not downloading.
The software installed, but crashes shortly after the logo comes up.
Will restart and see if this solves the problem.
3343.DigitalLibraryInstall.log
Mission: To serve God as He desires.
Comments
-
The log shows a "FileNotFoundException" but doesn't indicate which file isn't found. Please try to Repair Logos 4 in "Programs and Features" in "Control Panel" and see if that helps.
0 -
Same report here - crashes on startup. Tried the repair, but still has the same behavior.
0 -
Just went so far as to uninstall Logos and reinstall Beta 3 from scratch, but still failed on startup.
0 -
-
I tried repairing from the programs and features screen. That did not fix the problem. I also tried starting Logos without being connected to the internet; same result. This release renders Logos unusuable
0 -
Same crash here...
0 -
I am seeing the same problem.
0 -
Has anyone found a work around?
I have been beta testing since 2005, and this is the first time that I have been unable to use the software. First time that I do not have a backup version of L4 on the same machine. So I am locked out. Lots of firsts. [H]
Fortunately, I can still access my resources via biblia.com and mobile platform. Thanks for the one lisence, many platforms philosophy Logos.
I'll just sit back and wait for Beta 4 to fix the problem. [;)]
Mission: To serve God as He desires.
0 -
חַפְּשׂוּ בַּתּוֹרָה הֵיטֵב וְאַל תִּסְתַּמְּכוּ עַל דְּבָרַי
0 -
Lynden Williams said:
Has anyone found a work around?
Unfortunately no. I tried deleting L4 from my computer and then reinstalling the beta from scratch but that did not work either. This is a broken beta. Fortunately I have a backup from my netbook and can reload from there.
0 -
I am also experiencing the same problem with Win7Pro... tried rebooting and running repair. No success. Will be interested in a workaround.
Dave Nisly
0 -
Hope they fix this soon. Without iPad & Biblia, I'd be dead in the water.
0 -
I'm back in business after installing from a backup of beta 2 from my netbook. Not meaning to rub anything in but wanted to once gain publicly thank Dave Hooton for his instaling on multiple computers page on the wiki. That has saved me a lot of time a trouble a number of times over the years.
As a side note when broken betas have gone out before Logos is usually pretty quick to fix it. Very often the next day.
0 -
Fredc said:
As a side note when broken betas have gone out before Logos is usually pretty quick to fix it. Very often the next day.
That is why I expect them to probably give a fix today, if they can solve the problem. Don't plan on installing the stable version, will wait.
Mission: To serve God as He desires.
0 -
Lynden Williams said:Fredc said:
As a side note when broken betas have gone out before Logos is usually pretty quick to fix it. Very often the next day.
That is why I expect them to probably give a fix today, if they can solve the problem. Don't plan on installing the stable version, will wait.
Agreed. I usually keep a back-up of a stable version and the latest tested beta (in this case 4.6 beta 2) for that very reason. I would not think this would be too difficult to diagnose and fix.
0 -
Here is the error message I got. I cannot start up Logos at all - it just keeps shutting down
Problem signature:
Problem Event Name: CLR20r3
Problem Signature 01: logos4.exe
Problem Signature 02: 4.60.0.2889
Problem Signature 03: 50294ff1
Problem Signature 04: Logos4
Problem Signature 05: 4.60.0.2889
Problem Signature 06: 50294ff1
Problem Signature 07: 23f
Problem Signature 08: 10b
Problem Signature 09: System.IO.FileNotFoundException
OS Version: 6.0.6002.2.2.0.768.3
Locale ID: 1037
0 -
Would someone at Logos please let us know what's going on with this?
0 -
For those users who report experiencing the issue and have not yet done so, please post your full diagnostic logs.
It would also be helpful if we could get a crash dump file.
Lynden, since we have your full logs, if you get a chance to collect a crash dump file as well, that would be greatly appreciated.
Thanks!0 -
-
-
If you are experiencing the crash, what anti-virus software are you using? (I'm wondering if that is a common factor across all these failing installations.)
Please check your AV's quarantined files list and restore any Logos 4 files that have been quarantined. (Sorry that I can't provide instructions on how to do this; it is different for each AV program.)
0 -
I am running Trend Micro OfficeScan. I haven't updated/patched Windows7 since Sep2011 (corporate restrictions).
0 -
Bradley Grainger (Logos) said:
If you are experiencing the crash, what anti-virus software are you using? (I'm wondering if that is a common factor across all these failing installations.)
Please check your AV's quarantined files list and restore any Logos 4 files that have been quarantined. (Sorry that I can't provide instructions on how to do this; it is different for each AV program.)
Bradley,
I use McAfee; I think Lynden uses the same. Found no Logos 4 files in quaratine.
db
0 -
-
Bradley Grainger (Logos) said:
Please check your AV's quarantined files list and restore any Logos 4 files that have been quarantined. (Sorry that I can't provide instructions on how to do this; it is different for each AV program.)
Nothing quarantined by Trend Micro OfficeScan on my Win7 installation.
0 -
OK, it sounds like anti-virus probably isn't the cause.
If you're experiencing this crash, please collect a crash dump with ProcDump (see instructions here: http://wiki.logos.com/ProcDump) and email it to logos4feedback@logos.com.
We probably don't need more than two or three, so if you see some other users posting here that they've already sent one in, then you don't need to.
0 -
Crash dump log submitted.
0 -
Having trouble with the dos command. Somewhere I do seem to be getting the syntax right.
Mission: To serve God as He desires.
0 -
Dump file submitted.
db0 -
0
