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

Silk Performer Test Build error out with Master node

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      Hello Team,

       

      I just tried running a Silk Performer test build with Master only node and the build error out with an access issue as mentioned below,

       

      so would like to know what I am missing here which led to the below access Denied error. PFB, detailed error for reference.

       

      Started by user User
      Running as SYSTEM
      Building on master in workspace C:\Program Files (x86)\Jenkins\workspace\JenSil_Int
      Unable to auto-install JDK until the license is accepted.
      Object = true
      Object = true
      Initializing the load tests.

      USING THE FOLLOWING SETTINGS
      Project file path: \\MachineName\Scripts_POC\JSON_POC.ltp
      Results path: \\MachineName\Scripts_POC\result\
      Silk Performer installation directory: C:\Program Files (x86)\Silk\Silk Performer 17.5
      com.segue.em.SGRuntimeException: SYSTEM: 5 - Access is denied.
       at com.segue.em.SGExecutionManager.sgemOpenProject(Native Method)
       at com.segue.em.SGExecutionManager.openProject(SGExecutionManager.java:50)
       at com.borland.jenkins.SilkPerformerJenkins.util.SilkPerformerTestManager.getActiveWorkload(SilkPerformerTestManager.java:32)
       at com.borland.jenkins.SilkPerformerJenkins.ExecuteOnNode.call(ExecuteOnNode.java:86)
       at com.borland.jenkins.SilkPerformerJenkins.ExecuteOnNode.call(ExecuteOnNode.java:33)
       at hudson.remoting.LocalChannel.call(LocalChannel.java:45)
       at com.borland.jenkins.SilkPerformerJenkins.SilkPerformerBuilder.perform(SilkPerformerBuilder.java:83)
       at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
       at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:741)
       at hudson.model.Build$BuildExecution.build(Build.java:206)
       at hudson.model.Build$BuildExecution.doRun(Build.java:163)
       at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:504)
       at hudson.model.Run.execute(Run.java:1815)
       at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
       at hudson.model.ResourceController.execute(ResourceController.java:97)
       at hudson.model.Executor.run(Executor.java:429)
      Build step 'Execute Silk Performer Tests' marked build as failure
      Archiving artifacts
      Unable to auto-install JDK until the license is accepted.
      Recording plot data
      Finished: FAILURE

        Attachments

          Activity

          Hide
          mihai_virag Mihai Virag added a comment -

          Do we have writing rights for this directory?

          Also, Silk Performer 17.5 is a pretty old one, do you have any plans to update?

          Show
          mihai_virag Mihai Virag added a comment - Do we have writing rights for this directory? Also, Silk Performer 17.5 is a pretty old one, do you have any plans to update?
          Hide
          chandru_s Chandrakumar Sekar added a comment -

          Yes, I have right access to the directory, i.e. my ID has full control to the directory where the script are placed. When i run this through Master - Salve config build (Silk Performer test) is success and failing only if i choose Master configuration. 

          Yes, We have plan to update the Silk Performer version to 19.5 by early 2020 till then we will be using the 17.5 version. 

          Show
          chandru_s Chandrakumar Sekar added a comment - Yes, I have right access to the directory, i.e. my ID has full control to the directory where the script are placed. When i run this through Master - Salve config build (Silk Performer test) is success and failing only if i choose Master configuration.  Yes, We have plan to update the Silk Performer version to 19.5 by early 2020 till then we will be using the 17.5 version. 
          Hide
          chandru_s Chandrakumar Sekar added a comment -

          Currently this Jira can be closed as when i created a new build and mapping it to Jenkins, it worked

          Show
          chandru_s Chandrakumar Sekar added a comment - Currently this Jira can be closed as when i created a new build and mapping it to Jenkins, it worked

            People

            Assignee:
            silk Silk Performer
            Reporter:
            chandru_s Chandrakumar Sekar
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: