If I understand your situation, you have a Remedy server on Windows, from which you want to call a batch file, and that batch file calls another script on a remote Unix server. Your batch file works (successfully runs the remote Unix script) when executed manually. And you are having trouble getting Remedy to call the batch file?
Are you using a "Run Process" action in your filter, or is it a "Set Fields" action? Some of the other responses have referenced the $PROCESS$ keyword, which would be used in a "Set Fields" action, but not in a "Run Process" action. I notice your batch file is located in C:\Users\An***\Desktop. Does your Remedy server have access to that file location? (also keep in mind that if the path to your script has any spaces, it should be double quoted). -Thad On Sat, Oct 14, 2017 at 11:42 PM, Abhishek Anand <abhi.masc...@gmail.com> wrote: > Hi Experts, > > > How to call a .sh script located in remote unix box from the remedy > server 8.1 on windows using the FILTER Run Process command? > > I have designed the close_tt.bat file in my local system which in turn is > calling below script residing on remote server:- > > C:\plink -l **** -pw ***** stemipt /usr/opt/temip_tttls/Runtime/OpenCTI.sh > CLOSE "$Request ID$" > > I am using below logic in FILTER Run Process command line but its failing > :- > > cmd /c C:\Users\An******\Desktop\close_tt.bat "$Request ID$" > > Early response will be highly appreciated. > > Regards, > AA > > ____________________________________________________________ > ___________________ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > "Where the Answers Are, and have been for 20 years" > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
