Hi I hope my findings wont confuse you.
I could locate the same error coming into arescl.log and was firing on "SLA Rule Event Occurrence" form. The escl name is "SLA:TAD Polling_Escalation". It sets the 'SLA Rule Event Occurred' field is to 'Yes'. Tracing the root cause in backward direction, I could find some application generated filters (starting with zSLAGen:tad..) which fires on setting the field (SLA Event Rule Event Occured) value to "Yes". IMPORTANT : I had deleted some SLAs from Remedy User login(SLA : Main console) sometimes back.I doubt it make be associated filters of SLA which are still existing and firing on meeting condition. Should i simply go ahead and disable the esclation or should i go for deletion of those (zSLA..) filters. priyanka_sareen wrote: > > hi friends, > > I am using Remedy server6.3 > In arerror.log , i sent the follownig entry numerous times : > "Cannot translate a group name in either the Group List or Assignee Group > field (ARERR 417)" > Though the functionality is running fine and no impact on Remedy server > working as such. > I want to know its root cause and eliminate this. > Any pointers? > > Priyanka Sareen > -- View this message in context: http://www.nabble.com/Entry-coming-recursively-in-arerror.log-tp15133113p15202654.html Sent from the ARS (Action Request System) mailing list archive at Nabble.com. _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
