I cannot get the new update to run. I get an error message "object already exists" I tried to run the update as Administrator but no luck.
If I say no to run the update, Logos loads normally>
Can you upload your logs? Specifically your install log.
Program Version: 5.2a SR-7 (5.2.1.0171)Time: 2014-08-16 13:34:09 -04:00 (2014-08-16T17:34:09Z)Error handling response (POST https://services.logos.com/v1/LicenseService.svc/compatibility).System.Net.WebException: The underlying connection was closed: A connection that was expected to be kept alive was closed by the server. at System.Net.HttpWebRequest.GetResponse() at Libronix.Utility.Net.HttpWebRequestUtility.DoGetHttpResponse(Func`1 fnGetResponse) at Libronix.Utility.Net.HttpWebRequestUtility.GetHttpResponse(HttpWebRequest request) at Libronix.Utility.Net.WebServiceRequestBase`1.<GetResponse>b__0(HttpWebRequest x) at Libronix.Utility.Net.WebServiceRequestBase`1.DoGetResponse(HttpWebRequest webRequest, Func`2 getWebResponse, IWorkState workState) at Libronix.Utility.Net.WebServiceRequestBase`1.GetResponse(IWorkState workState)
Assuming Windows, zip and upload the Logos Log Files folder as per https://wiki.logos.com/Diagnostic_Logging.
Logging started: 2014-08-16T23:33:22Z
**truncated output**
2014-08-16T23:33:36Z 0x840 Info RunCommandInstall MsiInstallProductW returned 1603: failure 2014-08-16T23:33:36Z 0x840 Error RunCommandInstall The Windows Installer return code must be ERROR_SUCCESS (0) to succeed. Flagging for abort. 2014-08-16T23:33:36Z 0x840 Info LogosMessageBox Displaying message box with title 'Logos Bible Software Setup', message 'The installation of Logos Bible Software did not succeed.' and an error icon. 2014-08-16T23:33:38Z 0x840 Info Run Processing line 66: # if the install failed, it set the abort flag; abort now 2014-08-16T23:33:38Z 0x840 Info Run Processing line 67: abort 2014-08-16T23:33:38Z 0x840 Info RunCommandAbort Aborting 2014-08-16T23:33:38Z 0x840 Info LookupMessage Message ID not specified, using script's string value of ''. 2014-08-16T23:33:38Z 0x840 Info Run Return code 'fail', canceling BITS download jobs. 2014-08-16T23:33:38Z 0x840 Info CancelBackgroundCopyJobs Checking for background copy jobs. 2014-08-16T23:33:38Z 0x840 Info SaveCommands Writing command file back to 'C:\Users\Jon\AppData\Local\Logos4\Install\Logos4UpdateScript.lbxdat'. 2014-08-16T23:33:38Z 0x840 Info Module Terminating module, return code 2.
Please don't copy and paste logs into the forums. Also, make sure you have enabled logging first. Then attach the logos.log file via the paperclip icon in the formatting pallet. If you can edit your previous post, please delete the log.
[6318.DigitalLibraryInstall.zip
The critical lines are:-
MSI (s) (EC:34) [07:36:19:581]: SECREPAIR: Hash Database: C:\Windows\Installer\SourceHash{8F48977E-AE63-4C8E-9F91-14B14086B317}MSI (s) (EC:34) [07:36:19:581]: SECREPAIR: SourceHash database file already exists. Deleting it.MSI (s) (EC:34) [07:36:19:628]: Note: 1: 2262 2: SourceHash 3: -2147287038 MSI (s) (EC:34) [07:36:19:924]: SECREPAIR: New Hash Database creation complete.MSI (s) (EC:34) [07:36:19:924]: SECREPAIR: CryptAcquireContext: Could not create the default key containerMSI (s) (EC:34) [07:36:19:924]: SECREPAIR: Crypt Provider not initialized. Error:-2146893809MSI (s) (EC:34) [07:36:19:924]: SECUREREPAIR: Failed to CreateContentHash of the file: Logos.msi: for computing its hash. Error: -2146893809MSI (s) (EC:34) [07:36:19:924]: SECREPAIR: Failed to create hash for the install source filesMSI (s) (EC:34) [07:36:19:924]: Note: 1: 2262 2: SourceHash 3: -2147287038 MSI (s) (EC:34) [07:36:19:924]: SECUREREPAIR: SecureRepair Failed. Error code: 8009000fF54234B8Action start 7:36:19: ProcessComponents.MSI (s) (EC:34) [07:36:22:514]: MSI (c) (58:20) [07:36:19:940]: Font created. Charset: Req=0, Ret=0, Font: Req=MS Shell Dlg, Ret=MS Shell Dlg
Object already exists.MSI (s) (EC:34) [07:36:22:545]: Machine policy value 'DisableRollback' is 0MSI (s) (EC:34) [07:36:22:545]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2 Action ended 7:36:22: ProcessComponents. Return value 3.
I don't fully understand this. However:-
If it exists, delete the folder C:\Windows\Installer to Recycle Bin (so it can be recovered). Then try updating again from this link and upload the install logs if it fails again.
Different error message but no luck!6521.DigitalLibraryInstall (2).zip
Still cannot get the install to work
The error code returned is:
Your temp folder is C:\Users\Jon\AppData\Local\Temp\
Could you that you have enough space and that folder is writeable?
Similar errors installing Microsoft products offer the following advice. It might be worth following that, too: https://support.microsoft.com/kb/811881
Still no luck same error message
2308.DigitalLibraryInstall (3).zip
The log file is empty. Please contact Logos Technical Support for further assistance.
I call tomorrow but here's the log
5556.DigitalLibraryInstall (3).zip
Jon, can you go into your Windows update history and tell me if you have an update called KB2918614?
Yes, it was installed on the 16th
Uninstalled KB2918614 and the Logos update ran with no problem!
I have this Windows update and did not have a problem (as far as I know). I assume this is because I was on the beta and the Logos updates installed prior to the Windows update. Does that mean that the Windows update can be applied after updating Logos?
I have this Windows update and did not have a problem (as far as I know).
Are you running Windows 7? AFAIK, on Windows 7 users get the "object already exists" error.
Does that mean that the Windows update can be applied after updating Logos?
Yes... but it doesn't mean that the next Logos update (5.2b SR-3, 5.3, etc.) will succeed once that update is installed.
I have this Windows update and did not have a problem (as far as I know). Are you running Windows 7? AFAIK, on Windows 7 users get the "object already exists" error. Does that mean that the Windows update can be applied after updating Logos? Yes... but it doesn't mean that the next Logos update (5.2b SR-3, 5.3, etc.) will succeed once that update is installed.
Yes, I'm running Win7 SR-1 (64bit). I did not get an "object already exists error."
Hmm. Considering that the update is listed as a security update, and that many Logos users may update without checking the forums, shouldn't Logos figure out a work-around for this, other than removing this Windows update?
Or is it really a problem?
I have a logossetup.log dated 8/21/14 (after the problematic Windows update, which I got on 8/15/14), that shows no errors. Looks like it was installing 5.2.2.1512 - my current version of Logos (from the previous beta, I assume). There are no errors in that log, and the log ends with a return code of 0.
Looking at my current logs since then, there are no errors that look like they have anything to do with this problem. (There is only one error in my current Logos.log: "NotificationsViewModel Error wanted to read 8 bytes, but got 0" with no other errors or warnings on that thread. The LogosError.log only shows several consecutive errors connecting to the Logos servers - all on 2014-08-28 between 07:31 and 07:38 - which may have been a wi-fi issue on my end).
So, is it really a problem, once Logos is installed? Or is this a problem that may affect some users and not others (for whatever unknown reasons there might be)?
Well, I'd argue that this Windows Update broke our perfectly good installer (and many others; this problem is being reported on forums for dozens of different software packages)... [:)]
Ideally, yes, we would have an installer that works in the presence of the latest Windows updates. However, we haven't had time to diagnose and understand the issue, and prepare a revised update. So, right now, the only workaround is to uninstall the Windows update. When we have a different workaround, we'll let you know.
Hmm. Considering that the update is listed as a security update, and that many Logos users may update without checking the forums, shouldn't Logos figure out a work-around for this, other than removing this Windows update? Well, I'd argue that this Windows Update broke our perfectly good installer (and many others; this problem is being reported on forums for dozens of different software packages)... Ideally, yes, we would have an installer that works in the presence of the latest Windows updates. However, we haven't had time to diagnose and understand the issue, and prepare a revised update. So, right now, the only workaround is to uninstall the Windows update. When we have a different workaround, we'll let you know.
Well, I'd argue that this Windows Update broke our perfectly good installer (and many others; this problem is being reported on forums for dozens of different software packages)...
[/Tongue in cheek] It's so much easier to criticize you guys when we have no idea what the problems are. [/Tongue no longer in cheek]
