Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-64053

Windows MSI installer fails prematurely when using a service logon account containing spaces in its name

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Minor Minor
    • core, packaging
    • Windows 10 Pro 64 bit
      Version 10.0.19041, Build 19041
      Java SE Runtime Environment 8u271
      Tried installing 2.249.2 and 2.264, both resulting in the same error
    • 2.266

      The msi installer will fail prematurely when the user chooses to use an account with spaces in its name as the service logon account.

      I have confirmed that installing using another account which name doesn't have spaces does work properly as a workaround, so it seems that the issue really stems from the whitespace in the account name being parsed as separate arguments in the command line.

      Still, creating another user account just for this purpose is really annoying in cases like mine where the PC only has one account to begin with. Not to mention potentially being a turnoff for first time users!

      The way I see it, the issue should be really quick and simple to fix by wrapping the user account name with surrounding quotes, just like install path, etc.

      I hope it will be fixed soon, cheers

        1. installer_whitespace_bug.png
          installer_whitespace_bug.png
          199 kB

          [JENKINS-64053] Windows MSI installer fails prematurely when using a service logon account containing spaces in its name

          Oleg Nenashev added a comment -

          I have created https://github.com/jenkinsci/packaging/pull/197 which should fix the issue. CC slide_o_mix.  

          Oleg Nenashev added a comment - I have created https://github.com/jenkinsci/packaging/pull/197  which should fix the issue. CC slide_o_mix .  

          Dennis Samuel added a comment - - edited

          Neat, thanks!

          Dennis Samuel added a comment - - edited Neat, thanks!

          Alex Earl added a comment -

          This should be in 2.266

          Alex Earl added a comment - This should be in 2.266

          Dennis Samuel added a comment -

          Can confirm that the 2.266 msi installs properly, but on a clean install :

          For some reason it wouldn't install until I removed all Windows registry entries left by the old Jenkins installation where I used a temporary user account to confirm the bug for reporting. Jenkins was uninstalled from the command line, and said account was removed from the system afterwards.

          Here's the error line from the install log :
          'Error 1920. Service 'Jenkins' (Jenkins) failed to start. Verify that you have sufficient privileges to start system services.'

           

          Should I reopen this report or close it and/or create a new one for that particular case?

          Dennis Samuel added a comment - Can confirm that the 2.266 msi installs properly, but on a clean install : For some reason it wouldn't install until I removed all Windows registry entries left by the old Jenkins installation where I used a temporary user account to confirm the bug for reporting. Jenkins was uninstalled from the command line, and said account was removed from the system afterwards. Here's the error line from the install log : 'Error 1920. Service 'Jenkins' (Jenkins) failed to start. Verify that you have sufficient privileges to start system services.'   Should I reopen this report or close it and/or create a new one for that particular case?

          Alex Earl added a comment -

          Probably a new issue

          Alex Earl added a comment - Probably a new issue

            oleg_nenashev Oleg Nenashev
            voxeus Dennis Samuel
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: