Since it is failing as an Escalation as well then it is not encountering the 
Active Link Run Process directory security setting in the Admin Console

I don’t have any v9 servers up right now so I'm not sure what is trying to run.

Fred

-----Original Message-----
From: jham36 [mailto:[email protected]] 
Sent: Friday, August 21, 2015 10:24 AM
To: Remedy ARS
Cc: [email protected]; Grooms, Frederick W
Subject: Re: Remedy 9 PROCESS command

My Active Link is actually a test for what is really done as an Escalation.  I 
need to call the exe to return a status value.  I created an Active Link and 
attached it to a button in order to test.  It is failing as an AL and as an 
Escalation.

-----Original Message-----
On Thursday, August 20, 2015 at 5:58:51 PM UTC-4, Grooms, Frederick W wrote:
** 
I’m always leery of running a server side command from an AL.  I now do the 
following
 
Create a SERVICE type filter to run the command.
Call the Filter from the AL with the Service action (and in here you can return 
the values you want)
 
Fred
 
-----Original Message----- 
From: Action Request System discussion list(ARSList) 
[mailto:[email protected]] On Behalf Of jham36
Sent: Thursday, August 20, 2015 4:44 PM
To: [email protected]
Subject: Remedy 9 PROCESS command

** 
Hello all,

A few months ago I posted an issue about running psexec from Remedy and got 
some good help.  I ended up using paexec which is able to get the console 
output from the remote process and return it directly into remedy.
I am currently on ARS 7.5 and upgrading to ARS 9 and doing some testing on the 
new servers.  What I have is an Active Link doing a set fields $PROCESS$ 
@@:$StatusCommand$ $Test Set Name$
I am getting values from fields on the form to use in the Process command.  The 
path to paexec.exe plus parameters and the remote exe name and parameters.

D:\QCInt\PAExec\paexec.exe \\servername -u domain\User -p Password 
C:\User\QCInt\RunTestSet\RunTestSet.exe -ss Demo_Process

I didn't have to call cmd.exe or comspec or anything special.

This works fine with my ARS 7.5 system and I get the return value into Remedy.
On my new ARS 9 system, the remote process is executed, but I do not get the 
return value and the paexec process as well as the remote temporary paexec 
service do not exit.
When I run the same command from a command line on the new remedy server, it 
works just fine.
It seems that something has changed in how the $PROCESS$ command works.

Any ideas?

Thanks,
James

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
"Where the Answers Are, and have been for 20 years"

Reply via email to