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 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<file:///\\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"
