• Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Critical Critical
    • remoting
    • None
    • Platform: All, OS: All

      Using latest Hudson (1.255). Attempting to install the slave agent as a Windows
      service on the Windows build slaves.

      Hudson is running on a remote server. Open an IE session as a local system
      administrator on the Windows build slave and start a JNLP agent. Select File to
      install the agent as a windows service.

      Get an error dialog that states: [build]$c:\cygwin\build\hudson-slave.exe install

      Attempt to run from command line (c:\cygwin\build\hudson-slave.exe install).

      Immediately returns with no information. No service is installed.

      Same problem on two different Windows boxes. On box is running Windows 2000
      Professional, the other is running Windows XP Professional. Same problem on both.

          [JENKINS-2452] Cannot install slave agent as Windows service

          ddominguez added a comment -

          I had the same problem. Updating the .NET framework fixed it for me. I believe
          you need at least .NET 2.0 for this feature to work. Although I went ahead and
          updated to 3.0 and it fixed the problem for me.

          ddominguez added a comment - I had the same problem. Updating the .NET framework fixed it for me. I believe you need at least .NET 2.0 for this feature to work. Although I went ahead and updated to 3.0 and it fixed the problem for me.

          aleksas added a comment -

          Hudson v:1.331
          Run slave agent on xp sp2 using JNLP.
          In hudson slave window pressed "install as windows service". -> Pop UP"Install as
          windows server" -> Press "OK"

          As a result no services created.
          dotNET 2.0 and 3.5 installed on slave machine.

          aleksas added a comment - Hudson v:1.331 Run slave agent on xp sp2 using JNLP. In hudson slave window pressed "install as windows service". -> Pop UP"Install as windows server" -> Press "OK" As a result no services created. dotNET 2.0 and 3.5 installed on slave machine.

          roxspring added a comment -

          Hudson: 1.331
          Windows: 2003 SE SP2
          .NET 2.0 SP2, 3.0 SP2, 3.5

          The following jars get downloaded into %HUDSON_HOME%: maven-agent.jar, maven-
          interceptor.jar, maven2.1-interceptor.jar, presumably thanks to the jnlp
          download, but no other files are downloaded and no logs are created. There
          seems to be no clue as to why nothing has happened.

          Workaround (if you have existing other slaves): Copy the .exe, .jar and .xml
          files from another slave, editing the url referenced in the .xml file to
          reference the new slave.

          roxspring added a comment - Hudson: 1.331 Windows: 2003 SE SP2 .NET 2.0 SP2, 3.0 SP2, 3.5 The following jars get downloaded into %HUDSON_HOME%: maven-agent.jar, maven- interceptor.jar, maven2.1-interceptor.jar, presumably thanks to the jnlp download, but no other files are downloaded and no logs are created. There seems to be no clue as to why nothing has happened. Workaround (if you have existing other slaves): Copy the .exe, .jar and .xml files from another slave, editing the url referenced in the .xml file to reference the new slave.

          Daniel Beck added a comment -

          Is this still an unresolved issue?

          Note that being able to only install one slave is tracked elsewhere.

          Daniel Beck added a comment - Is this still an unresolved issue? Note that being able to only install one slave is tracked elsewhere.

          Chris Welch added a comment -

          Haven't had this issue in a very long time. Slave setup has been working fine for at least the past 4 years.

          Chris Welch added a comment - Haven't had this issue in a very long time. Slave setup has been working fine for at least the past 4 years.

            Unassigned Unassigned
            cwelch cwelch
            Votes:
            3 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: