Crash whilst updating to 4.3 SR1
Updated my Desktop "Beta" system using the web link. It asked me to Sign in (details filled in) and then crashed.
It restarted OK.
Dave
===
Windows 11 & Android 13
Comments
-
I experienced the same exact crash... then everything was fine after restarting
0 -
Paul Newsome said:
I experienced the same exact crash... then everything was fine after restarting
same... so, looking like a trend.
"I read dead people..."
0 -
Me too! Exactly the same (first time ever Logos has crashed on me for many years!).
Restarting Logos - everything seems fine again!
Edit: I was not running the beta this was a normal update from v4.3 to x4.3 SR-1
0 -
same
Orthodox Bishop Alfeyev: "To be a theologian means to have experience of a personal encounter with God through prayer and worship."; Orthodox proverb: "We know where the Church is, we do not know where it is not."
0 -
-
Dave Hooton said:
Updated my Desktop "Beta" system using the web link. It asked me to Sign in (details filled in) and then crashed.
My "'stable" Laptop system updated normally and without a crash!
Dave
===Windows 11 & Android 13
0 -
My desktop crashed too: and I was not running a beta.
0 -
Something is going on with an image upgrade because I got the same crash when I started my Desktop "stable" system running 4.2b SR-1
Dave
===Windows 11 & Android 13
0 -
I’m not sure if this is the same problem y’all are having,
but when I went to install the new update (4.3 SR 1?) I receive the attached
error message and I have to cancel the install process. There were also some
books that downloaded; these seemed to have installed correctly and the
indexing also seemed to have been completed successfully. I can run Logos
without installing (currently is 4.20.0.1516).Also, I am attaching the crash log from this AM (I'm not sure if this is related or not, but the program did crash on start-up): 2703.Logos4Crash.txt
If this is not the same problem, does anyone have a
suggestion to fix?
0 -
Bruce said:
Also, I am attaching the crash log from this AM
That is the same crash as we have experienced.
Bruce said:I’m not sure if this is the same problem y’all are having,
but when I went to install the new update (4.3 SR 1?) I receive the attached
error message and I have to cancel the install process.You should repeat the install and attempt the Retry as this has worked for other users. It may not appear to work but check the version of L4 (should see 4.3 SR-1). If that is not successful attempt this fix.
Dave
===Windows 11 & Android 13
0 -
Thank you Dave! As soon as I saw what was addressed in the
link, I knew that was the problem. To gain a bit more speed I had been running
as admin until recently. I went in and set to run as administrator and all is
well. Thx for the help! Have a great week!0 -
Dave; This is somewhat of a shot in the dark, but before the upgrade when I started Logos today on my Macbook Pro, this image:
...was in a new type of information window all by itself. I'd never seen it before in Logos. I was excited to see it on my desktop but never could produce it. My guess is some custom pop up window testing might be going on... or else I have pop up windows blocked on one computer and not the other,and this has been a feature in Logos for some time... [:P]
0 -
Dave
===Windows 11 & Android 13
0 -
I'm going to pass the posted logs onto Development so they can get a look at the error and try to figure out what happened.
0 -
Dave
===Windows 11 & Android 13
0 -
Dave Hooton said:
I got a crash when starting Logos just now. 1856.Logos4Crash.txt
Tried restarting again, and it worked fine.
MacBook Pro (2019), ThinkPad E540
0 -
Development has determined the cause of the crash and traced it to an issue on our end. It should not reoccur. [:)]
Thank you all for alerting us to the problem.
0 -
I guess it is too late since everyone else has already spoken up about this but I am not on Beta and I had the same thing happen.
0 -
Mine just crashed again. It did it yesterday, worked fine a few times in between, then crashed when I opened it just now.
0 -
Welcome Michele,
Michele Miner said:Mine just crashed again. It did it yesterday, worked fine a few times in between, then crashed when I opened it just now.
Yea, I just crashed. But let's be certain yours is the same crash. Find and attach logos4Crash.txt in \Logos Log Files\ in either your \Temp folder or \Documents folder.
Dave
===Windows 11 & Android 13
0 -
I continue to have crashes. When I have been away from Logos for some time, the next startup causes a crash. An immediate attempt to restart it is always successful.
Fred Greco
Senior Pastor, Christ Church PCA, Katy, TX
Windows 10 64-bit; Logos 7.1 SR-2 (Reformed Platinum)0 -
Apologies. I've been informed that the trouble item wasn't disabled until sometime this morning, and it is possible that it may be cached on some users' machines. That being said, the issue shouldn't reoccur multiple times for the same login on the same computer at this point.
0 -
Since resetting to run as admin. I have not had any further problems at start up. In addition, the update (4.3 SR-1) installed just fine. [:D] Sorry to hear y'all are still having problems. [:(]
0 -
Bruce said:
Sorry to hear y'all are still having problems.
Sorry to hear you may have problems with the next software update[:(] (running as Admin is not recommended).
It may be coincidental your running as Admin, because I successfully received a small notification window when starting 4.3; which is something new.
Dave
===Windows 11 & Android 13
0 -
I had the same error message when running the inprogram update. When I checked the Owner (as per the fix) it showed that my own user name was the owner already. So I changed the owner (which really didn't change anything from my perspective, but apparently it did from the computer's perspective). Once I executed that change, the update ran flawlessly. Don't know if this variation helps. Thanx for the tip.
In Christ,
Paul
0 -
Paul E. Zetterholm said:
I had the same error message when running the inprogram update. When I checked the Owner (as per the fix) it showed that my own user name was the owner already. So I changed the owner (which really didn't change anything from my perspective, but apparently it did from the computer's perspective). Once I executed that change, the update ran flawlessly. Don't know if this variation helps. Thanx for the tip.
Bruce's problem with access to dll files was unrelated to the spate of crashes most people reported here, so your fix was coincidental as the main problem was Logos' to fix and I believe that has happened (as I stated above).
Dave
===Windows 11 & Android 13
0 -
I have not use logos in a while but found a crash from august 18, 2011. So now I cannot access Logos at all. Can any one help. I tried uninstalling and reinstalling but it did not work. It says Logos is up to date but i STILL CANNOT USE IT. help
0 -
kyle brown said:
I have not use logos in a while but found a crash from august 18, 2011. So now I cannot access Logos at all. Can any one help. I tried uninstalling and reinstalling but it did not work. It says Logos is up to date but i STILL CANNOT USE IT. help
First enable logging http://wiki.logos.com/Diagnostic_Logging -->then try to start Logos4 and upload logs as stated in the wiki.
Dave
===Windows 11 & Android 13
0 -
David
Thanks for your reply. But my problems is more that that. I don't have an Icon to start Logos 4 in and it only shows only 4 gigs
on my hard drive which should show almost 26gigs. I cannot even start Logos.That is why I was re
installing Logos. When reinstall I get an error message saying the
package is bad. Please help0 -
Kyle -
If I understand you correctly, it sounds like you have WAY TOO MUCH on your hard drive. I am not a hyper techie guy. Perhaps others can chime in as well. In my personal experience, I seem to notice a drop off in performance when my hard drive gets to be much more than half full. If you only have 4 GB left, you have a serious issue.
0
