Hi Fred, Removing the space after the colon was exactly the same thing I did after starting to receive errors. I also used the exit(0) line :-) I have no idea why it fails, the only way left seems a restart as Conny said, i think.
Koray On Apr 20, 8:20 pm, "Grooms, Frederick W" <[email protected]> wrote: > I may be picky here but when I do an external $PROCESS$ from an AL I don't > put a space after the colon > $PROCESS$ @@:/mypath/script -p1 parameter1 -p2 parameter2 > > The 0x86 is what the script is exiting with as a status. On scripts I don't > want to return an error to Remedy I exit them with an exit 0 line. > > Fred > > > > -----Original Message----- > From: Action Request System discussion list(ARSList) > [mailto:[email protected]] On Behalf Of koray > Sent: Tuesday, April 20, 2010 11:54 AM > To: [email protected] > Subject: Re: {Remedy ARS} Re: Active Link External $PROCESS$ on AR Server 7.5 > > Hello Conny, > > I activated arfork-log and here is the output: > > arforkd version 7.5.00 PatchTue Apr 20 18:46:00 2010 Arforkd: Opening > log file in overwrite mode. > Tue Apr 20 18:46:00 2010 Awaiting record marker. > Tue Apr 20 18:46:04 2010 Received record marker. > Tue Apr 20 18:46:04 2010 Spawning child, shell "", command "/mypath/ > script -p1 parameter1 -p2 parameter2". > Tue Apr 20 18:46:04 2010 Spawned "/mypath/script -p1 parameter1 -p2 > parameter2" as pid 886. > Tue Apr 20 18:46:04 2010 Awaiting record marker. > Tue Apr 20 18:46:06 2010 process id 886 has exited with status 0x86. > Tue Apr 20 18:46:14 2010 Received record marker. > > @process id 886 has exited with status 0x86: Can you help me on what > 0x86 status is? > @arserverd restart: How can I see the stdout messages related while > the restart? > > Best Regards, > Koray > > On Apr 20, 7:32 pm, Conny Martin <[email protected]> wrote: > > Koray, > > > acivate arfork-log. If you don't see anything in arfork.log restart > > arserverd in your Unix-shell to see stdout/stderr. > > > HTH > > > Kind Regards Conny > > > -----Ursprüngliche Nachricht----- > > Von: Action Request System discussion list(ARSList) > > [mailto:[email protected]] Im Auftrag von koray > > Gesendet: Dienstag, 20. April 2010 18:29 > > An: [email protected] > > Betreff: Re: {Remedy ARS} Re: Active Link External $PROCESS$ on AR Server > > 7.5 > > > Script's working quite perfect. I tried copying&pasting "/mypath/ script > > -p1 parameter1 -p2 parameter2" to UNIX shell and it returns as expected. So > > it can't be the syntax. > > > On Apr 20, 7:21 pm, Frank Caruso <[email protected]> wrote: > > > > Is the problem with the syntax or with what /mypath/script is doing? > > > > On Tue, Apr 20, 2010 at 7:18 PM, koray <[email protected]> wrote: > > > > Hello together, > > > > > I have upgraded my ARS servers from 6.3 to 7.5 and facing with some > > > > major problems since then. > > > > The previous syntax to run an external process via an Active Link > > > > was > > > > > $PROCESS$ @@: /mypath/script -p1 parameter1 -p2 parameter2 > > > > > and it worked perfect. But since the 7.5 upgrade I have been > > > > receiving > > > > errors: > > > > > <ACTL> -> Passed qualification -- perform if actions <ACTL> > > > > > > > > 0: Set Fields > > > > > <ACTL> Process: /mypath/script -p1 parameter1 -p2 > > > > parameter2 > > > > <ACTL> **** Error while performing active link action > > > > > Do you have any idea? What am I doing wrong here? > > > > I even tried double-quoting the parameters but nothing seems to work. > > > > > Also removing ":" character from active link results with no error > > > > but returns null. > > > > > Thanks in advance! > > > > Koray > > > > > ____________________________________________________________________ > > > > _______ ____ UNSUBSCRIBE or access ARSlist Archives > > > > atwww.arslist.orgattendwwrug10www.wwrug.comARSlist:"Where the Answers > > > > Are" > > > > ______________________________________________________________________ > > > _____ ____ UNSUBSCRIBE or access ARSlist Archives atwww.arslist.org > > > attend wwrug10www.wwrug.comARSlist:"Where the Answers Are" > > > > -- > > > You received this message because you are subscribed to the Google Groups > > > "Remedy ARS" group. > > > To post to this group, send email to [email protected]. > > > To unsubscribe from this group, send email to > > > [email protected]. > > > For more options, visit this group > > > athttp://groups.google.com/group/arslist?hl=en. > > > ___________________________________________________________________________ > > ____ > > UNSUBSCRIBE or access ARSlist Archives > > atwww.arslist.orgattendwwrug10www.wwrug.comARSlist:"Where the Answers Are" > > > ___________________________________________________________________________ > > ____ > > UNSUBSCRIBE or access ARSlist Archives atwww.arslist.org > > attend wwrug10www.wwrug.comARSlist:"Where the Answers Are" > > > -- > > You received this message because you are subscribed to the Google Groups > > "Remedy ARS" group. > > To post to this group, send email to [email protected]. > > To unsubscribe from this group, send email to > > [email protected]. > > For more options, visit this group > > athttp://groups.google.com/group/arslist?hl=en. > > ___________________________________________________________________________ > ____ > UNSUBSCRIBE or access ARSlist Archives atwww.arslist.org > attend wwrug10www.wwrug.comARSlist: "Where the Answers Are" > > ___________________________________________________________________________ > ____ > UNSUBSCRIBE or access ARSlist Archives atwww.arslist.org > attend wwrug10www.wwrug.comARSlist: "Where the Answers Are" > > -- > You received this message because you are subscribed to the Google Groups > "Remedy ARS" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group > athttp://groups.google.com/group/arslist?hl=en. _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are"
