client 0.11.17 do not install with MSI
-
There is always that chance, but I would have thought the case statement I added would have eliminated any changes to the windows and linux install process. let me poke around it
-
Installing the release msi interactively and targeting a non-https FOG installation is successful and functions as expected on one of my test systems, so I don’t think there is anything inherently wrong with the installation logic. Going to spin up an https fog instance to test against
-
@Sebastian-Roth
OK, I was able to replicate the error with 0.11.17 with a command line installation using:msiexec /i FOGService.msi /quiet USETRAY="1" HTTPS="1" WEBADDRESS="192.168.137.11" WEBROOT="/fog" ROOTLOG="1" /l*v "FOGService.msi.log"I was also able to replicate the issue on 0.11.16 using the same command line.
MSI (s) (04:10) [14:51:08:538]: Invoking remote custom action. DLL: C:\windows\Installer\MSI34C8.tmp, Entrypoint: InstallCert SFXCA: Extracting custom action to temporary directory: C:\windows\Installer\MSI34C8.tmp-\ SFXCA: Binding to CLR version v4.0.30319 Calling custom action SetupHelper!SetupHelper.CustomActions.InstallCert MSI (s) (04!08) [14:51:09:303]: Note: 1: 2205 2: 3: Error MSI (s) (04!08) [14:51:09:303]: Note: 1: 2228 2: 3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1709 MSI (s) (04!08) [14:51:09:303]: Product: FOG Service -- Unable to install CA certificate Unable to install CA certificate ...[clip]... MSI (s) (04:10) [14:51:09:741]: Note: 1: 2205 2: 3: Error MSI (s) (04:10) [14:51:09:741]: Note: 1: 2228 2: 3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1708 MSI (s) (04:10) [14:51:09:741]: Note: 1: 2205 2: 3: Error MSI (s) (04:10) [14:51:09:741]: Note: 1: 2228 2: 3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1709 MSI (s) (04:10) [14:51:09:741]: Product: FOG Service -- Installation failed. MSI (s) (04:10) [14:51:09:741]: Windows Installer installed the product. Product Name: FOG Service. Product Version: 0.11.16. Product Language: 1033. Manufacturer: FOG. Installation success or error status: 1603.will need to dig into who is trying to talk to what, where, and how…
-
@Daniel-Miller Nice catch!!
@lebrun78 Are you sure this is working fine for you with 0.11.16 version?
-
@Sebastian-Roth
I did not try with certificats and client 0.11.16.
Without certificat 0.11.16 was working -
Possibly the installer doesn’t handle pining to a HTTPS server directly. Not sure at the moment.
-
@Sebastian-Roth
Hello
msi install works when passing https=0, so if I copy a settings.json file after installation, will the operation be sustainable ? -
@lebrun78 said in client 0.11.17 do not install with MSI:
msi install works when passing https=0, so if I copy a settings.json file after installation, will the operation be sustainable ?
Yes I would say so but this is definitely something we need to find and fix in the fog-client too.
-
@Daniel-Miller @lebrun78 I have looked through the code and can’t find an obvious issue related to using HTTPS! I’ll need to add some more debugging output and figure that out. Will be back.
-
@lebrun78 @Daniel-Miller Ok, I found what is causing this! Thanks again for reporting. I moved this topic to bug reports. Will push out a fix soon. Will be in the next fog-client release to come out soon.
-
@Daniel-Miller @lebrun78 Can you please try the new MSI package? https://github.com/FOGProject/fog-client/releases/download/0.11.17/FOGService-fixed_HTTPS_install.msi
-
@Sebastian-Roth
I am on leave for 10 days
I’ll test the new installer when I get back.Merry Christmas
-
@lebrun78 Leave should be over now, hello back again!?
I have tested this so many times over the last days. Marking as solved as I know it is.
-
@Sebastian-Roth Looks good from this end.