[JIRA] (JENKINS-56194) Not able to run UFT ALM Scripts from master when the slave machine is logged off

2 views
Skip to first unread message

sakthiisaibharathi.samundeeswari@bnymellon.com (JIRA)

unread,
Feb 19, 2019, 4:37:01 AM2/19/19
to jenkinsc...@googlegroups.com
Sakthi Isai Bharathi Samundeeswari created an issue
 
Jenkins / Bug JENKINS-56194
Not able to run UFT ALM Scripts from master when the slave machine is logged off
Issue Type: Bug Bug
Assignee: Daniel Gront
Components: hp-application-automation-tools-plugin, hp-quality-center-plugin, slave-setup-plugin
Created: 2019-02-19 09:36
Priority: Critical Critical
Reporter: Sakthi Isai Bharathi Samundeeswari

Team, 

I am not able to run UFT scripts when slave machine is logged off completely.
Started by user
Sakthi
Building remotely on
W000WVP0C
in workspace D:\Jenkins\workspace\TestbedXAT
[TestbedXAT] $ D:\Jenkins\workspace\TestbedXAT\HpToolsLauncher.exe -paramfile props19022019041726459.txt
"Started..."
Timeout is set to: -1
Run mode is set to: RUN_LOCAL
============================================================================
Starting test set execution
Test set name: XAT_StabilityCheck_Copy_1_Copy_1, Test set id: 40885
"Number of tests in set: "1
Test 1: [1]RES_COB_StabilityCheck will run on host: W000WVP0C
"Scheduler started at:19/02/2019 04:17:32
-------------------------------------------------------------------------------------------------------
19/02/2019 04:17:32 Running: [1]RES_COB_StabilityCheck
19/02/2019 04:17:32 Running test: [1]RES_COB_StabilityCheck, Test id: 558831, Test instance id: 827741
Test: [1]RES_COB_StabilityCheck, Id: 827741, Execution status: Running
Test: [1]RES_COB_StabilityCheck, Id: 827741, Execution status: Error, Message: The server process could not be started because the configured identity is incorrect. Check the username and password
19/02/2019 04:17:37 Test complete: [1]RES_COB_StabilityCheck
-------------------------------------------------------------------------------------------------------
Test: [1]RES_COB_StabilityCheck, Status: Error, Message: The server process could not be started because the configured identity is incorrect. Check the username and password \nLink: tds://PERSHING_TECHNOLOGY.PERSHING.qc.pershing.com:8443/qcbin/TestLabModule-000000003649890581?EntityType=IRun&EntityID=1326605\n
Test set: XAT_StabilityCheck_Copy_1_Copy_1, finished at 19/02/2019 04:17:37
================================================
Run status: Job failed, total tests: 1, succeeded: 0, failures: 0, errors: 1
Error : Root\ReS\Automation\StartofDay\TESTBED\XAT_StabilityCheck_Copy_1_Copy_1[1]RES_COB_StabilityCheck
================================================
Build step 'Execute Micro Focus functional tests from Micro Focus ALM' changed build result to FAILURE
Finished: FAILURE
Add Comment Add Comment
 
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

sakthiisaibharathi.samundeeswari@bnymellon.com (JIRA)

unread,
Feb 19, 2019, 5:18:02 AM2/19/19
to jenkinsc...@googlegroups.com

daniel.gront@microfocus.com (JIRA)

unread,
Feb 19, 2019, 6:22:02 AM2/19/19
to jenkinsc...@googlegroups.com
Daniel Gront assigned an issue to Anda Sorina Laakso
 
Change By: Daniel Gront
Assignee: Daniel Gront Anda Sorina Laakso

daniel.gront@microfocus.com (JIRA)

unread,
Feb 19, 2019, 6:22:02 AM2/19/19
to jenkinsc...@googlegroups.com
Daniel Gront updated an issue
Change By: Daniel Gront
Labels: UFT

anda-sorina.laakso@microfocus.com (JIRA)

unread,
Feb 19, 2019, 6:54:02 AM2/19/19
to jenkinsc...@googlegroups.com

anda-sorina.laakso@microfocus.com (JIRA)

unread,
Feb 19, 2019, 7:15:01 AM2/19/19
to jenkinsc...@googlegroups.com

anda-sorina.laakso@microfocus.com (JIRA)

unread,
Feb 19, 2019, 7:21:02 AM2/19/19
to jenkinsc...@googlegroups.com

And this is about the registries setup for autolog on Windows.

anda-sorina.laakso@microfocus.com (JIRA)

unread,
Feb 19, 2019, 7:21:03 AM2/19/19
to jenkinsc...@googlegroups.com
Anda Sorina Laakso edited a comment on Bug JENKINS-56194
And this is about the registries setup for autolog on Windows.

anda-sorina.laakso@microfocus.com (JIRA)

unread,
Feb 19, 2019, 7:21:03 AM2/19/19
to jenkinsc...@googlegroups.com
Anda Sorina Laakso updated an issue
 

anda-sorina.laakso@microfocus.com (JIRA)

unread,
Feb 19, 2019, 7:21:03 AM2/19/19
to jenkinsc...@googlegroups.com

sakthiisaibharathi.samundeeswari@bnymellon.com (JIRA)

unread,
Feb 19, 2019, 7:29:02 AM2/19/19
to jenkinsc...@googlegroups.com

Anda Sorina Laakso Tried all possibilities. It is not working. Can you provide working solutions ?

anda-sorina.laakso@microfocus.com (JIRA)

unread,
Feb 19, 2019, 7:31:01 AM2/19/19
to jenkinsc...@googlegroups.com

Did you try also the last 2 links i provided?

sakthiisaibharathi.samundeeswari@bnymellon.com (JIRA)

unread,
Feb 19, 2019, 7:33:02 AM2/19/19
to jenkinsc...@googlegroups.com

yes Anda Sorina Laakso. Facing same issues

daniel.gront@microfocus.com (JIRA)

unread,
Feb 19, 2019, 7:38:02 AM2/19/19
to jenkinsc...@googlegroups.com

Anda Sorina Laakso, Could it be due to UFT's new feature?

anda-sorina.laakso@microfocus.com (JIRA)

unread,
Feb 19, 2019, 7:46:02 AM2/19/19
to jenkinsc...@googlegroups.com

 
 
To solve it, set Windows Auto-Logon as I explain here: https://serverfault.com/questions/269832/windows-server-2008-automatic-user-logon-on-power-on/606130#606130

Then create a startup batch for Jenkins slave (place it in Jenkins directory), which will launch it's console on desktop, and will allow GUI jobs to run:
 java -jar slave.jar -jnlpUrl http://\{Your Jenkins Server}:8080/computer/{Your Jenkins Node}/slave-agent.jnlp
(slave.jar can be downloaded from http://\{Your Jenkins Server}:8080/jnlpJars/slave.jar)

EDIT : If you're getting black screenshots (when using Selenium for example), create a batch file that disconnects Remote Desktop, instead of closing the RDP session with the regular X button:
 %windir%\system32\tscon.exe %SESSIONNAME% /dest:console

anda-sorina.laakso@microfocus.com (JIRA)

unread,
Feb 19, 2019, 7:59:09 AM2/19/19
to jenkinsc...@googlegroups.com

From this page https://sumeetkushwah.com/2015/03/24/implementing-ci-using-jenkins-and-uft/

check the paragraph :

Unlocking remote slave machine before executions

 

sakthiisaibharathi.samundeeswari@bnymellon.com (JIRA)

unread,
Feb 19, 2019, 8:09:01 AM2/19/19
to jenkinsc...@googlegroups.com

Anda Sorina Laakso Its not working when i logoff the slave and start the scripts from master

 

anda-sorina.laakso@microfocus.com (JIRA)

unread,
Feb 19, 2019, 8:11:02 AM2/19/19
to jenkinsc...@googlegroups.com

Then it means you need an RDP session.

sakthiisaibharathi.samundeeswari@bnymellon.com (JIRA)

unread,
Feb 19, 2019, 8:37:03 AM2/19/19
to jenkinsc...@googlegroups.com

Anda Sorina Laakso So, Jenkins Master and Slave will not work if it is logged off completely ? Daniel Gront

daniel.gront@microfocus.com (JIRA)

unread,
Feb 21, 2019, 2:55:02 AM2/21/19
to jenkinsc...@googlegroups.com

Hey Sakthi Isai Bharathi Samundeeswari,

Since the master needs to communicate with the slave so it could tell it to:

  1. Execute
  2.  Copy relevant files like HpToolLauncher.exce

It isn't possible to do it while you're not connected to a master as a slave.

I am closing this issue since it's not a defect but a limitation of Jenkins itself.

daniel.gront@microfocus.com (JIRA)

unread,
Feb 21, 2019, 2:55:03 AM2/21/19
to jenkinsc...@googlegroups.com
Daniel Gront closed an issue as Not A Defect
 
Change By: Daniel Gront
Status: Open Closed
Resolution: Not A Defect

jenkins@alexview.com (JIRA)

unread,
Feb 3, 2020, 2:56:02 PM2/3/20
to jenkinsc...@googlegroups.com
Mat Walker commented on Bug JENKINS-56194
 
Re: Not able to run UFT ALM Scripts from master when the slave machine is logged off

Sakti,

FYI Daniel Gront

We have this issue with Bamboo (we are migrating to Jenkins) so I confirm it is NOT Jenkins.  To resolve, you need to;

  1. Log on to Test Execution host machine.
  2. Launch UFT
  3. In Tools->Options click ‘Verify Connection’ button
  4. Close UFT
  5. Disconnect from Test Execution host machine (DO NOT LOG OFF!)

Apparently ALM has had this issue since QC (Quality Centre days).
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
Atlassian logo
Reply all
Reply to author
Forward
0 new messages