Bug/Warning: 5.3 clobbered my main 32-bit installation on same 64-bit Windows
After installing 64-bit 5.3 beta on the same Windows 8 computer, Logos 5.2b crashes.
no crash/error logs. I'll upload event log later.
UPDATE:
.NET Runtime
Application: Logos.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.DllNotFoundException
Stack:
at Libronix.DigitalLibrary.NativeMethods.EnableLogging(Libronix.DigitalLibrary.LogMessageCallback)
at Libronix.DigitalLibrary.DigitalLibraryUtility.EnableNativeLogging()
at LDLS4.Indexer.Logos4ApplicationUtility.InitializeLogging()
at LDLS4.OurApp.Main(System.String[])
Application
Faulting application name: Logos.exe, version: 5.2.2.1489, time stamp: 0x53ece774
Faulting module name: KERNELBASE.dll, version: 6.2.9200.16864, time stamp: 0x531d2be6
Exception code: 0xe0434352
Fault offset: 0x00010f22
Faulting process ID: 0x168c
Faulting application start time: 0x01cfc25e6da3a261
Faulting application path: 
\Logos5\System\Logos.exe
Faulting module path: C:\WINDOWS\SYSTEM32\KERNELBASE.dll
Report ID: afa30f79-2e51-11e4-bec3-6cf04971afb5
Faulting package full name:
Faulting package-relative application ID:
It doesn't matter if logging is enabled or not, or whether I restart the computer and start 5.2b first.
Dave
===
Windows 11 & Android 13
Comments
-
Are you sure it's the beta, and not a resource or so?
The reason I'm asking: Prior to delving into the beta, I made a fresh install of the 32bit stable version (5.2b SP2) according to Method 2 in a new user account - worked like a charm (even the Home Page and Reading List - my respective error might be due to custom install directory in my old install). The Logos showed a 85MB update (which is the CP Starter Base Package I bought, I think) and after the download, while the indexer was preparing library, L5 constantly crashed without crash log - the process is not killed, the crash notice and "send to MS" notice displays and when aborted the crash notice reappears. I have yet to download the 5.3 beta...
UPDATE: after a PC restart, it seems to work
Have joy in the Lord!
0 -
Dave
===Windows 11 & Android 13
0 -
Similar occurred on my 32 bit netbook.
The crash occurred during the second part of the update (the databases), and it completely locked up the system. Had to hold power button for 5 seconds. Once restarted, everything appears to be functioning ok.
0 -
Erwin Stull, Sr. said:
Similar occurred on my 32 bit netbook.
Not the same problem, but I clarified my description to avoid confusion
Dave
===Windows 11 & Android 13
0 -
Dave Hooton said:Erwin Stull, Sr. said:
Similar occurred on my 32 bit netbook.
Not the same problem, but I clarified my description to avoid confusion
Got it.
Thanks Dave
0 -
Dave Hooton said:
After installing 64-bit 5.3 beta on the same Windows 8 computer, Logos 5.2b crashes.
(Mine is Windows 7 but it also) "After installing 64-bit 5.3 beta" on different user account on same 64 bit Win7 computer - my stable Logos 5.2b gets a "L5 has stopped working" message ie. it also will not load.
Problem details of Stable L5:
Problem signature:
Problem Event Name: CLR20r3
Problem Signature 01: logos.exe
Problem Signature 02: 5.2.2.1496
Problem Signature 03: 53ee8653
Problem Signature 04: Libronix.DigitalLibrary
Problem Signature 05: 5.2.2.1496
Problem Signature 06: 53ee71c6
Problem Signature 07: 2c0
Problem Signature 08: 0
Problem Signature 09: System.DllNotFoundException
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 4105
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789
[The following are from Stable L5 logs etc]QUESTION FROM 5 Logoserror.log: What is following referring to? - System.Net.WebException: The remote name could not be resolved: 'api.raygun.io'
No L5 stable crash log was generated.
HERE ARE THE (newly installed beta's) LOGS:
So at this point I am unable to load either the new Beta on it's unique User account NOR a Stable on its' own User Account.
[I have had the former [non 64 bit] Betas installed on this separate User Account with no issues]
NOTE: L5 64 bit Beta had been up and running. But then I attempted to download/install the new free Morris Proctor Resource which included the "get started" videos. It never properly re-booted. During that process I had the Stable L5 on the other User Account turned off. But it no longer will load.
I wondered if re-installing Stable L5 would help but got (almost) identical message: The last 9 lines below are identical to that above.
Problem signature:
Problem Event Name: CLR20r3
Problem Signature 01: logos.exe
Problem Signature 02: 5.2.2.1512
Problem Signature 03: 53f5f7c7
Problem Signature 04: Libronix.DigitalLibrary
Problem Signature 05: 5.2.2.1512
Problem Signature 06: 53f5f42c
Problem Signature 07: 2c3
Problem Signature 08: 0
Problem Signature 09: System.DllNotFoundException
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 4105
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789Thanks
Regards, SteveF
0 -
SteveF said:Dave Hooton said:
After installing 64-bit 5.3 beta on the same Windows 8 computer, Logos 5.2b crashes.
(Mine is Windows 7 but it also) "After installing 64-bit 5.3 beta" on different user account on same 64 bit Win7 computer - my stable Logos 5.2b gets a "L5 has stopped working" message ie. it also will not load.
Problem details of Stable L5:
Thanks for confirmation, Steve.
SteveF said:NOTE: L5 64 bit Beta had been up and running. But then I attempted to download/install the new free Morris Proctor Resource which included the "get started" videos. It never properly re-booted.
It would have been better to put this 5.3 problem in another thread.
Dave
===Windows 11 & Android 13
0 -
Failed to see this earlier and posted: Crash on Startup of L5 Gold in parallel account after installation of L5B3
Same issue here.
For fun I created a new account and performed a CLEAN INSTALL of L5 Gold.
The crash is near enough to be identical.
[quote]
Problem signature:
Problem Event Name: CLR20r3
Problem Signature 01: logos.exe
Problem Signature 02: 5.2.2.1512
Problem Signature 03: 53f5f7c7
Problem Signature 04: Libronix.DigitalLibrary
Problem Signature 05: 5.2.2.1512
Problem Signature 06: 53f5f42c
Problem Signature 07: 2c3
Problem Signature 08: 0
Problem Signature 09: System.DllNotFoundException
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789
Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409
If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt
Sarcasm is my love language. Obviously I love you. 0 -
FWIW:
I installed the current beta on my gold account [:'(] and will set it's update channel to default. It kind of ruins the backup of a gold account, but at least I can selectively upgrade it with beta's until it get's stable again.
So far.... L5.3b is doing what I need it to do.
Sarcasm is my love language. Obviously I love you. 0 -
Dave Hooton said:
After installing 64-bit 5.3 beta on the same Windows 8 computer, Logos 5.2b crashes.
Sorry everyone for these issues; I'll make a report and we'll investigate the cause of this.
In case it's relevant: are all of your installations in the default location, i.e. Users\[your user]\AppData\Local? I'm not sure if this would do anything, but what happens when you run "Repair" on the Logos Prerequisites on the 5.2b user account?
0 -
Right now both versions of mine are working under separate user accounts on my PC. I have not rebooted. I cannot recall whether I already had the 5.2 installation open before I did the 5.3 installation but at any event both are working without a problem. (I hesitate to close and reopen the 5.2 version at this point or reboot, but I'm sure I will eventually have to and discover if my 5.2 installation still works.)
I sent my 5.3 log files in a previous post on a separate thread. Some errors there but nothing to keep 5.3 from running.
Pastor, North Park Baptist Church
Bridgeport, CT USA
0 -
Dylan Rondeau said:
In case it's relevant: are all of your installations in the default location, i.e. Users\[your user]\AppData\Local?
All three of mine (L5 Gold, L5 beta, L5 beta playground) are in the default location.
The "Playground" is where I really try to break things.
Sarcasm is my love language. Obviously I love you. 0 -
Dylan Rondeau said:
what happens when you run "Repair" on the Logos Prerequisites on the 5.2b user account?
I was afraid to try this. Is the prereqs installation user account specific or is it for all accounts?
Sarcasm is my love language. Obviously I love you. 0 -
TCBlack said:Dylan Rondeau said:
what happens when you run "Repair" on the Logos Prerequisites on the 5.2b user account?
I was afraid to try this. Is the prereqs installation user account specific or is it for all accounts?
So I tried it.
I logged onto my Logos 5 Gold account and proceeded to the programs applet in control panel.
I located Logos 5 Prerequisites >> Right clicked and chose the repair option.
I am greeted with the knowledge that the prereqs appear to be system wide and not user specific - meaning it won't work.
The message I receive (on my 32 bit install) is:
[quote]
The file 'C:\Users\tcblack\AppData\Local\Logos4\install\Installers\' is not a valid installation package for the product Logos 5 Prerequisites. Try to find the installation package 'LogosPrerequisites-x64.msi' in a folder from which you can install Logos 5 prerequisites.
That it's asking for a file named *x64.msi tells me it wants to repair the 64bit prereqs. Here's the problem then: The 32bit prereqs are toast.
EDIT: I should note that while it gives the path to the file as including tcblack, that is not my current logged in account which is literally 'L5Gold' not tcblack. Further pointing to a system wide install of the pre-reqs.
Sarcasm is my love language. Obviously I love you. 0 -
With WPF and DX libraries getting in the picture, peaceful co-existence between a 32-bit installation and a 64-bit installation may be asking too much. Perhaps the devs should just forget the idea.
0 -
Lee said:
With WPF and DX libraries getting in the picture, peaceful co-existence between a 32-bit installation and a 64-bit installation may be asking too much. Perhaps the devs should just forget the idea.
Actually, I don't think a peaceful coexistence btwn 32/64 bit was the goal of the devs. But it does apply especially to many of us dedicated beta testers. Many of us keep multiple installations under different accounts on our computer.
Mostly then, this serves as a warning to us: it just ain't gonna happen. (Unless the devs decide they want the pre-reqs to become a user specific install. Not necessary methinks.
Sarcasm is my love language. Obviously I love you. 0 -
When there is a definitive answer on this would someone make sure that there is a clear official answer? I run only one machine and am staying out of this beta until I am certain that I can run Verbum in one account and Logos beta in another.
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 -
Sorry, Dave:Dave Hooton said:SteveF said:NOTE: L5 64 bit Beta had been up and running. But then I attempted to download/install the new free Morris Proctor Resource which included the "get started" videos. It never properly re-booted.
It would have been better to put this 5.3 problem in another thread.
I included that note here because I had tried to download/instal that resource while using the Beta version of L5.
I did try a "repair" of my stable L5 pre-reg's & program etc but neither Beta L5 nor Stable L5 [on separate users] simply will not load
So I am now using L4 [on yet another User Account] which is not connected to the Internet & also have access to a copy of L3. So I am "good to go" etc.
I did take the warnings of possible instability, very seriously, but did not read anything about the possibility that the Beta L5 could corrupt a stable L5 loaded on a different User Account [until you posted your experience, Dave]. Thanks for that.
And thanks to all who are attempting to sort this out.
Regards, SteveF
0 -
@MJ:
The closest thing to a definitive statement so far, from another thread:
Bradley Grainger (Logos) said:Dave Hooton said:will there be two Prerequisites; one for x86 and the other for x64?
There will be two.
Dave Hooton said:Does this mean we cannot have a 32-bit and a 64-bit installation on the same machine
You should be able to, but I guess we'll find out in the beta.
0 -
TCBlack said:TCBlack said:Dylan Rondeau said:
what happens when you run "Repair" on the Logos Prerequisites on the 5.2b user account?
I was afraid to try this. Is the prereqs installation user account specific or is it for all accounts?
So I tried it.
I logged onto my Logos 5 Gold account and proceeded to the programs applet in control panel.
I located Logos 5 Prerequisites >> Right clicked and chose the repair option.
I am greeted with the knowledge that the prereqs appear to be system wide and not user specific - meaning it won't work.
Yup! The 64-bit Prerequisites appears to have "replaced" the previous 32-bit Prerequisites.
We need solid information from the developers.
Dave
===Windows 11 & Android 13
0 -
Dylan Rondeau said:
In case it's relevant: are all of your installations in the default location
I never install to the default location!
Dave
===Windows 11 & Android 13
0 -
Dylan Rondeau said:
are all of your installations in the default location,
Only one of my L3, L4, L5 Stable & L5 Beta installatiions are in the"default" location
Regards, SteveF
0 -
Dave Hooton said:
Yup! The 64-bit Prerequisites appears to have "replaced" the previous 32-bit Prerequisites.
We need solid information from the developers.
This seems to be the case for 5.3 Beta 1. The Logos Prerequisites are installed machine-wide, and thus the 32-bit prerequisites are being replaced with the 64-bit ones, which causes the 5.2b installations to crash, even on different user accounts.
I don't have the information yet on how difficult this will be to fix for future betas or the final release of 5.3, but for now, it is not possible to install 5.3 Beta 1 on a machine and maintain a stable 5.2b. We apologize for this, and we know it's an inconvenience not to have the usual "safety net" in order to test the beta.
Also of note: Verbum shares the prerequisites with Logos, and so a 5.2b Verbum will also crash on launch after installing Logos 5.3.
0 -
Dylan Rondeau said:
for now, it is not possible to install 5.3 Beta 1 on a machine and maintain a stable 5.2b.
Ah well, that's easy: just use an old, slow 32bit machine to run both! Problem solved. Glad to be at your service...[;)]
EDIT: I retract that. Even on my 32bit machine the beta kills the Kernelbase.DLL needed for stable:
Name der fehlerhaften Anwendung: Logos.exe, Version: 5.2.2.1512, Zeitstempel: 0x53f5f7c7
Name des fehlerhaften Moduls: KERNELBASE.dll, Version: 6.1.7601.18409, Zeitstempel: 0x531599f6
Ausnahmecode: 0xe0434352
Fehleroffset: 0x0000812f
ID des fehlerhaften Prozesses: 0x1214
Startzeit der fehlerhaften Anwendung: 0x01cfc318429baf47
Pfad der fehlerhaften Anwendung: C:\Users\Mick\AppData\Local\Logos5\System\Logos.exe
Pfad des fehlerhaften Moduls: C:\Windows\system32\KERNELBASE.dll
Berichtskennung: 81fe3759-2f0b-11e4-b8de-001f16bf95beHave joy in the Lord!
0 -
Dylan Rondeau said:
We apologize for this, and we know it's an inconvenience not to have the usual "safety net" in order to test the beta.
Understood. Those warnings are there for a reason. My safety net is upstairs on my old computer running 5.1(something).
Sarcasm is my love language. Obviously I love you. 0 -
Dylan Rondeau said:
I don't have the information yet on how difficult this will be to fix for future betas or the final release of 5.3, but for now, it is not possible to install 5.3 Beta 1 on a machine and maintain a stable 5.2b.
Please add this warning to the Beta 1 release thread.
Dylan Rondeau said:We apologize for this, and we know it's an inconvenience not to have the usual "safety net" in order to test the beta.
I'm disappointed because I had requested information on this matter 7 days before the release!
Dave
===Windows 11 & Android 13
0 -
I am re-posting here simply to say that I am still running 5.2 and 5.3 on the same computer under different user accounts. I restarted both Logos installations this afternoon with no trouble. I still have not re-booted my computer since installing 5.3 (and don't have plans to do so right now). Perhaps things will change when I do.
Pastor, North Park Baptist Church
Bridgeport, CT USA
0 -
Mark Smith said:
I am re-posting here simply to say that I am still running 5.2 and 5.3 on the same computer under different user accounts.
I have the same issue in Windows 7 of 5.2b not starting after installing 64-bit 5.3.
Dave
===Windows 11 & Android 13
0 -
Dave Hooton said:Mark Smith said:
I am re-posting here simply to say that I am still running 5.2 and 5.3 on the same computer under different user accounts.
I have the same issue in Windows 7 of 5.2b not starting after installing 64-bit 5.3.
As I mentioned I haven't rebooted, although I don't see how that would change anything. It is curious I am running both and you and others are not. I am pretty sure I had Logos 5.2 running when I installed 5.3. Could that make a difference if you and others did not do the same thing?
It's all beyond me anyway, but hopefully Logos can figure out if there is a way around this problem. I suspect it will cut down on the number of L6 beta testers if most users only have Logos on one computer.
Pastor, North Park Baptist Church
Bridgeport, CT USA
0 -
In case anyone was wondering; there doesn't seem to be any problem running 5.2b stable and 5.3 beta alongside each other on Mac... [;)]
0 -
That's one for the Mac!
Dave
===Windows 11 & Android 13
0 -
Mark Smith said:
It is curious I am running both and you and others are not. I am pretty sure I had Logos 5.2 running when I installed 5.3. Could that make a difference if you and others did not do the same thing?
I tried it with 5.2 running but Prerequisites-x64 wasn't happy and wanted a reboot to complete its installation. 5.2 didn't survive!
Dave
===Windows 11 & Android 13
0 -
Dave Hooton said:
I tried it with 5.2 running but Prerequisites-x64 wasn't happy and wanted a reboot to complete its installation. 5.2 didn't survive!
No point in belaboring this esp. if Bradley's suggested fix works, but of course, I didn't have that happen. No when I reboot...
Pastor, North Park Baptist Church
Bridgeport, CT USA
0 -
Mark Smith said:
I didn't have that happen. No when I reboot...
But do you have the 2012 Redistributable?
Dave
===Windows 11 & Android 13
0 -
Pastor, North Park Baptist Church
Bridgeport, CT USA
0 -
TCBlack said:
Do you know if it is possible to run Logos 4 on a separate Windows 7 Account without clobbering my L5.3β ?
I use three separate user accounts: L4 - L5 Stable - L5 Beta
When both the L5 Beta & L5 Stable "crashed" on their individual, separate user accounts my L4 still worked on a third account with NO problems
I believe that it also included re-boots etc.
I do not know how/or why it worked that way. But it was a relief knowing that I could still use L4 [and also use my Libronix or L3] which was loaded on the same user account as my L5 Stable.
Regards, SteveF
0 -
Thank you SteveF. I think I'll build an L4Gold account on my computer tonight... just because I'm like that. :-)
Sarcasm is my love language. Obviously I love you. 0
