client 0.11.17 do not install with MSI



  • Hello
    The client do not install with msi

    I have add https install installing with this option: ./installfog.sh -W https://fogus.istic.univ-rennes1.fr -S

    CustomActionSchedule(Action=InstallCert,ActionType=3073,Source=BinaryData,Target=InstallCert,CustomActionData=sHTTPS=1;sUSETRAY=1;sWEBADDRESS=fogus.istic.univ-rennes1.fr;sWEBROOT=/fog;sROOTLOG=1;sProductVersion=0.11.17;sINSTALLDIR=C:\Program Files (x86)\FOG\)
    MSI (s) (58:C0) [16:30:10:887]: Invoking remote custom action. DLL: C:\windows\Installer\MSI2D78.tmp, Entrypoint: InstallCert
    SFXCA: Extracting custom action to temporary directory: C:\windows\Installer\MSI2D78.tmp-\
    SFXCA: Binding to CLR version v4.0.30319
    Calling custom action SetupHelper!SetupHelper.CustomActions.InstallCert
    MSI (s) (58!20) [16:30:11:809]: Note: 1: 2205 2:  3: Error 
    MSI (s) (58!20) [16:30:11:809]: Note: 1: 2228 2:  3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1709 
    MSI (s) (58!20) [16:30:11:809]: Product: FOG Service -- Unable to install CA certificate
    
    Unable to install CA certificate
    CustomAction InstallCert returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
    

    Here is the installfog generate by misexe:
    installfog.log

    installsation with SmartInstaller.exe works

    Could you help me ?



  • @Sebastian-Roth Looks good from this end.


  • Developer

    @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
    I am on leave for 10 days
    I’ll test the new installer when I get back.

    Merry Christmas


  • Developer


  • Developer

    @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.


  • Developer

    @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.


  • Developer

    @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.



  • @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 ?


  • Developer

    Possibly the installer doesn’t handle pining to a HTTPS server directly. Not sure at the moment.



  • @Sebastian-Roth
    I did not try with certificats and client 0.11.16.
    Without certificat 0.11.16 was working


  • Developer

    @Daniel-Miller Nice catch!!

    @lebrun78 Are you sure this is working fine for you with 0.11.16 version?



  • @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…



  • 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



  • 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


  • Developer

    @lebrun78 Thanks for your posting!! As we have not released a new client version in a long time and I have never done it before I am well aware of possible issues.

    Is this on a fresh system or one with 0.11.16 installed?

    It’s very interesting the SmartInstaller seems to work because it’s pretty much the MSI packed and wrapped up with some more things to make it also possible to install on Mono (Linux und MacOS).

    @Daniel-Miller Any chance the MacOS fix might be causing this?


Log in to reply
 

367
Online

6.6k
Users

14.0k
Topics

132.3k
Posts