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

Jenkins will not start as Window Service error 1053

    Details

    • Similar Issues:

      Description

      Jenkins will no longer start as a Window Service after a symantec update to v14. It was working prior to this but I am not sure if this is related to the error.

      When I attempt to start Jenkins as a service I receive the error:

       " Windows could not start the Jenkins service on Local Computer.

      Error 1053: The service did not respond to the start or control request in a timely fashion"

       

      When I try to start it using cmd using the command "jenkins.exe start"I get this error: 

      "System.ArgumentNullException: Value cannot be null.

      Parameter name: path1

      at System.IO.Path.Combine(String path1, Stringpath2)

      at winsw.ServiceDescriptor..ctor()

      at winsw.WrapperService.Run(String[] _args)

      at winsw.WrapperService.Main(string[] args)"

       

       

      Does anyone have any idea on how to fix this?

      I tried using https://support.symantec.com/en_US/article.TECH193916.html

      and I also tried creating a jenkins.exe.config file to prevent the firewall from blocking it

        Attachments

          Activity

          Hide
          oleg_nenashev Oleg Nenashev added a comment -

          marcelino dayrit please provide your jenkins.xml configuration

          Show
          oleg_nenashev Oleg Nenashev added a comment - marcelino dayrit please provide your jenkins.xml configuration
          Hide
          mdayrit marcelino dayrit added a comment - - edited

          Oleg Nenashev, the jenkins.xml was renamed to config.xml. would this be a problem?

          Also, in the config one of the JDK is pointing to a non existent jdk can this be the problem?

          or would it skip the non existent jdk and use the working one instead?

          Show
          mdayrit marcelino dayrit added a comment - - edited Oleg Nenashev , the jenkins.xml was renamed to config.xml. would this be a problem? Also, in the config one of the JDK is pointing to a non existent jdk can this be the problem? or would it skip the non existent jdk and use the working one instead?
          Hide
          oleg_nenashev Oleg Nenashev added a comment -

          Jenkins.xml renaming is likely a root cause. Not a defect then though a nessage could be better

          Show
          oleg_nenashev Oleg Nenashev added a comment - Jenkins.xml renaming is likely a root cause. Not a defect then though a nessage could be better
          Hide
          mdayrit marcelino dayrit added a comment -

          Oleg Nenashev Thank you for your help!

          Show
          mdayrit marcelino dayrit added a comment - Oleg Nenashev Thank you for your help!
          Hide
          mdayrit marcelino dayrit added a comment -

          Jenkins.xml fixed the issue

          Show
          mdayrit marcelino dayrit added a comment - Jenkins.xml fixed the issue

            People

            • Assignee:
              oleg_nenashev Oleg Nenashev
              Reporter:
              mdayrit marcelino dayrit
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: