[resolved] Upgrade to Beta 3 didn't install automatically
For me the upgrade to Beta 3 didn't install automatically.
I saw the warning sign saying it was downloading. It downloaded, then nothing happened apparently.
I restarted Verbum, and the little warning sign appeared, but no pop-up info was available when hovering the mouse over it. It just sat there. Update now didn't do anything more. Still on Beta 2.
Looking through the logs, it looks like the update process was failing. Maybe related to the faulty Verbum.exe in the Verbum folder, as it seems the update process was calling that file.
I found the installer in the Verbum folder and installed it from there. It installed fine. However, the Verbum.exe in my Verbum folder still doesn't do anything (the EXE file in the System folder continues to work correctly). I'm now running Beta 3.
Logs from before I manually ran the installer:
Comments
-
This has been happening the last 4 updates for me- not sure why.
0 -
The last two for me HAVE NOT installed automatically. It downloaded, I saw the triangle but NO upgrade. In fact, I restarted Logos and still NO upgrade. Not sure how to manually upgrade.
Bob Deacon
Ipad Air 2 (ios 9.7 (0014)
Windows 11 inside edition
Samsung S23
0 -
Bob Deacon said:
The last two for me HAVE NOT installed automatically. It downloaded, I saw the triangle but NO upgrade. In fact, I restarted Logos and still NO upgrade. Not sure how to manually upgrade.
Updates do not even download for me. Update Now returns No updates available.
0 -
My understanding is that the new version should download, but the new version will only open upon a manual restart. I have auto downloads set to "no" and received a banner telling me about the download. If I would have closed the banner, there would have been no indication that the download was occurring.
macOS, iOS & iPadOS |Logs| Install
Choose Truth Over Tribe | Become a Joyful Outsider!0 -
Mine will download automatically, but when am prompted to restart Logos the hyperlink does nothing when clicked. I ended up manually downloading and installing. The same thing with the last two Beta releases.
For book reviews and more visit sojotheo.com
0 -
Mine downloaded automatically but the triangle disappeared with no mention of an update. I then restart Logos, no update so I restarted computer and still no update.
Bob Deacon
Ipad Air 2 (ios 9.7 (0014)
Windows 11 inside edition
Samsung S23
0 -
Bob Deacon said:
Mine downloaded automatically but the triangle disappeared with no mention of an update. I then restart Logos, no update so I restarted computer and still no update.
This is what I experienced.
The only thing I'd add is that when I restarted manually, the triangle would appear, but with no message upon hover over.
0 -
Fr Devin Roza said:
Looking through the logs, it looks like the update process was failing. Maybe related to the faulty Verbum.exe in the Verbum folder, as it seems the update process was calling that file.
Fr. Devin, this should be the case. The Verbum.exe that wasn't launching the app for you also includes update information, and we weren't able to fix that in time for Beta 3.
John Kight said:Mine will download automatically, but when am prompted to restart Logos the hyperlink does nothing when clicked. I ended up manually downloading and installing. The same thing with the last two Beta releases.
This is listed as a known issue, and we hope to have it fixed soon.
Bob Deacon said:Mine downloaded automatically but the triangle disappeared with no mention of an update. I then restart Logos, no update so I restarted computer and still no update.
Are you sure this was the application update, and not a resource update? For resource updates the triangle will disappear once downloading and indexing have completed, but for application updates it should remain until you manually restart the application and apply the update. Could you verify that you have the channel set to beta, and enter "update now" in the command box?
Whyndell Grizzard said:This has been happening the last 4 updates for me- not sure why.
Huh. I'd expect the issues to be related to the change in update process with 6.3, but there's only been 3 releases. This has been happening since before then?
alabama24 said:My understanding is that the new version should download, but the new version will only open upon a manual restart. I have auto downloads set to "no" and received a banner telling me about the download. If I would have closed the banner, there would have been no indication that the download was occurring.
This is the expected behavior at the moment. Though closing the banner should still leave the triangle icon, which would give the text of the banner on hover or click.
0 -
It was a program update (beta 3).
Bob Deacon
Ipad Air 2 (ios 9.7 (0014)
Windows 11 inside edition
Samsung S23
0 -
Same problems with Beta 4. Except this time I didn't find the installer in the installer directory, and had to download it manually. So, slightly worse experience with the upgrade to Beta 4. All other problems were the same - the warning icon that wouldn't go away, with no information on hover, etc. Verbum.exe still doesn't work from the main folder.
0 -
I can confirm this behavior. I guess I am stuck on beta-2. A software download occurred, but nothing happened.
macOS, iOS & iPadOS |Logs| Install
Choose Truth Over Tribe | Become a Joyful Outsider!0 -
alabama24 said:
I can confirm this behavior. I guess I am stuck on beta-2. A software download occurred, but nothing happened.
I manually downloaded and installed Beta 4 successfully—See *IMPORTANT* Beta Testing Information/Warnings for the link.
0 -
You are correct about the upgrade mechanism for Beta 2 (and Beta 3). Verbum registers the update with the splash screen application (Verbum.exe in your Verbum folder), then launches the splash screen to install the update. The splash screen asks if you want to upgrade and launches the VerbumSetup.exe if you choose "Yes." Since your splash screen application isn't working, the update doesn't happen.
I haven't been able to reproduce the problem with the splash screen application... and I can't understand why it's not working. It's a pretty simple program with no dependencies, so it should just work. It should at least display the Verbum splash screen image. Could you please check the version of that file? From Windows Explorer, navigate to your Verbum folder, right-click on Verbum.exe and choose Properties, then go to the Details tab. If you've got Beta 4 installed, the "Product version" should be 6.3.0.0026.
The other point of interest would be the name of the System folder. In order to facilitate installing updates in the background, we're now putting the Verbum application and its dependencies in a folder named after its version rather than a folder named "System." For Beta 4, this folder should be named "6.3.0.0026" and there shouldn't be a folder named "System." Does your system have this folder in the Verbum folder?
Thanks for your patience on this, hopefully we can get it figured out quickly!
Bryan
0 -
Bryan Albert said:
Could you please check the version of that file? From Windows Explorer, navigate to your Verbum folder, right-click on Verbum.exe and choose Properties, then go to the Details tab. If you've got Beta 4 installed, the "Product version" should be 6.3.0.0026.
Yes, product version is 6.3.0.0026. Size = 289,736 bytes. File version = 6.3.0.26.
Double clicking on it makes the mouse change to the spinning wheel for maybe .1 seconds. Then nothing happens. It never appears in the Task Manager, as best I can tell.
Bryan Albert said:
The other point of interest would be the name of the System folder. In order to facilitate installing updates in the background, we're now putting the Verbum application and its dependencies in a folder named after its version rather than a folder named "System." For Beta 4, this folder should be named "6.3.0.0026" and there shouldn't be a folder named "System." Does your system have this folder in the Verbum folder?
Yes, that's correct. I have the folder 6.3.0.0026, and no longer have the folder System. This new folder was created when I manually downloaded and installed the install files for Beta 4. Prior to that, Verbum Beta 3 had downloaded the install files and tried to install but failed. At that point (after the failed install), I still had the "System" folder, and there was no 6.3.0.0026 folder.
If you want to connect up to my computer and take a look, just drop me an email.
0 -
Here's maybe a shot in the dark, but attached should be a file Verbum.zip. It contains the Logos.exe splash screen renamed as Verbum.exe. Could you please move your Verbum\Verbum.exe splash screen somewhere else, then extract this copy to your Verbum folder, then execute it? It should display the Logos 6 splash screen but run your Verbum\6.3.0.0026\Verbum.exe application. If it works, it could suggest that there's some subtle problem with our "branding" process that converts Logos into Verbum.
Thanks!
Bryan
0 -
Bryan, thanks. Your shot in the dark worked. The Logos 6 splash screen showed up, then Verbum opened, just as you suggested.
0 -
Here's my update for Beta 5....
Got the notification bar that a new version was available. Clicked on it, but no option to restart, just an indication that when I restarted it would upgrade.
So, I restarted (using a link to "C:\...\Verbum\6.3.0.0026\Verbum.exe"), but Beta 4 opened up.
So, then I tried the Verbum.exe file in the \Verbum folder, which did nothing (my half-working Verbum.exe file that you supplied me, Bryan, had been replaced with a new broken Verbum.exe file).
So, I noticed I now have two Verbum system folders - one for Beta 4 (named 6.3.0.0026) and one for Beta 5 (named 6.3.0.0029). Both have about 230MB. For a while I was about to run both of them, both Beta 4 and Beta 5 worked.
Then I saw the Beta 5 installer in the Install folder and ran that. It offered to repair my installation. So, I let it try. Verbum.exe in the Verbum folder still does nothing (and, BTW, is about 100KB smaller than the Verbum.exe file you gave me to try that half-worked). I still have two 230MB System folders, so Beta 4 was never removed, but now Beta 4 no longer works, it tells me I have some components installed from a later version and that I should upgrade. Beta 5 works, as long as I open the EXE in the System folder.
0 -
Fr Devin Roza said:
Here's my update for Beta 5....
Got the notification bar that a new version was available. Clicked on it, but no option to restart, just an indication that when I restarted it would upgrade.
This is by design for this release.
Fr Devin Roza said:So, I restarted (using a link to "C:\...\Verbum\6.3.0.0026\Verbum.exe"), but Beta 4 opened up.
Yes, the 6.3.0.0026 folder holds Beta 4, so executing that path from your shortcut will run Beta 4 (at least until Beta 5 runs—see below. After that Beta 4 will show a dialog talking about upgrading).
Fr Devin Roza said:So, then I tried the Verbum.exe file in the \Verbum folder, which did nothing (my half-working Verbum.exe file that you supplied me, Bryan, had been replaced with a new broken Verbum.exe file).
This is unfortunate, I was hoping that the new splash screen would just work. We'll figure this out... When you shut down Verbum and relaunch it from the desktop shortcut, it launches the Verbum\Verbum.exe splash screen, which is tied to the current version, so it launches Verbum\6.3.0.0029\Verbum.exe. In your case, Verbum\Verbum.exe is just not working, so Beta 5 doesn't launch.
Fr Devin Roza said:So, I noticed I now have two Verbum system folders - one for Beta 4 (named 6.3.0.0026) and one for Beta 5 (named 6.3.0.0029). Both have about 230MB. For a while I was about to run both of them, both Beta 4 and Beta 5 worked.
That's by design. When we upgrade, we install the new System folder (6.3.0.0029 in this case) side-by-side with the old one (6.3.0.0026). Old System folders that are neither of these are deleted.
Fr Devin Roza said:Then I saw the Beta 5 installer in the Install folder and ran that. It offered to repair my installation. So, I let it try. Verbum.exe in the Verbum folder still does nothing (and, BTW, is about 100KB smaller than the Verbum.exe file you gave me to try that half-worked). I still have two 230MB System folders, so Beta 4 was never removed, but now Beta 4 no longer works, it tells me I have some components installed from a later version and that I should upgrade. Beta 5 works, as long as I open the EXE in the System folder.
Once the new version runs successfully, it sets a registry key marking the new version, so that the old version can't be run accidentally, since a new version can update database files in a way that isn't necessarily backwards compatible.
The good news is that the upgrade seems to have worked properly, the bad news is, of course, that your splash screen doesn't work, so it's difficult to launch Beta 5. I'm scrutinizing that code and plan on figuring this out today.
If you could find the Beta 4 to Beta 5 VerbumSetup.log on your system (in the "Verbum Log Files" folder, either in your Documents or %TEMP% folder), it might have one or two clues. Also, if you run regedit.exe, what do you see in your HKEY_CURRENT_USER\Software key? There should be a Verbum key, with string values InstallDirectory and InstalledVersion. Is there a Software\Logos4 key?
Thank you for your detailed and useful analysis!
0 -
Bryan Albert said:
If you could find the Beta 4 to Beta 5 VerbumSetup.log on your system (in the "Verbum Log Files" folder, either in your Documents or %TEMP% folder), it might have one or two clues.
The install logs are being placed directly inside the %TEMP% folder, not inside a subfolder called "Verbum Log Files" (I do have a folder called that in the %DOCUMENTS% folder, however).
Here are the log files. This one is for the initial upgrade from Beta 4 to 5.
And here is the one from the Repair:
Bryan Albert said:
Also, if you run regedit.exe, what do you see in your HKEY_CURRENT_USER\Software key? There should be a Verbum key, with string values InstallDirectory and InstalledVersion. Is there a Software\Logos4 key?
Here you go:
0 -
This is now working correctly in RC1. Thanks!
0 -
Fr Devin Roza said:
This is now working correctly in RC1. Thanks!
Worked seamlessly here also. Thanks for the fix.
0
