QTP launches and then abruptly get closed when invoked through RQM Commandline Adapter.
Settings:
QTP 11.0
RQM Adapter ver : com.ibm.rqm.adapter.commandline_2.0.0.v20140416_2010
RQM adapter calls the batch file, which invokes scriptlaunch.vbs program to launch qtp script.
QTP launches and then abruptly gets closed, however the process QTPro.exe is still active on the taskmanger for 1-2 minutes after which it ends when qtp fails to look solution for the problem on the web.
For many past months we have successfully carried out execution this way, however from very recent we are running into this issue.
This issue is seen after we took a Citrix remote login of the system where qtp script execution was going on via RQM CLA.
when the remote login was taken we saw some error and after that we are unable to get the execution done through RQM CLA.
This issue is seen after we took a Citrix remote login of the system where qtp script execution was going on via RQM CLA.
when the remote login was taken we saw some error and after that we are unable to get the execution done through RQM CLA.
Any help is highly appreciated.
One answer
Pradeep,
Could you give more details on what error you are getting? Are you seeing those error on CLA console? At a first glance it looks like some issue outside of CLA or RQM purview but any of the related log might be useful to investigate further, please share.
I would suggest to invoke that batch file manually and check if QTP start execution successfully. I am suspecting some user access related issue, please check the logged in user have enough privilege to access the files your script uses.
Regards,
Mehul
Comments
Hi Mehul,
when we invoke batch file manually qtp execution is fine.
the only time we see issue is when we excute it through RQM CLA.
on CLA console we do not see any error.
It is just that CLA gives call to batch file and batch file launches qtp via scriptlaunch.vbs file, however before the test script is loaded qtp gets closed.
we have been carrying out the excution this way since past 3-4 months and never faced any such issue.
It is jsut that very recently we are seeing this situation.
The logged user has administrator privileige.
Regards,
Pradeep