GlacierChris, What is the workflow behind the creation of the ticket?
I mean when the Escalation fires, is the Escalation directly creating that ticket? Or is a Filter set to fire on that Escalation create that ticket? What are the exactly actions on your Escalations as well as filters created to fire on that Escalation? It definitely isn't a problem with the Server Groups. Server groups allow for only one Escalation server within the server group. Joe D'Souza -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] Behalf Of Pickering, Christopher Sent: Monday, October 01, 2007 12:24 PM To: [email protected] Subject: Escalation creating dup tickets ** Hello all, Has anyone seen where a single escalation fires and creates matching tickets where the only difference is the Request ID? In the logs, it shows the escalation firing, doing a push to ITSM (Help Desk), does a return setfield back into the original form that a second setfield changes the value which triggered the escl firing in the first place, then immediately there after, with no escalation fire a second Help Desk Desk ticket is created with a sequential requestID. This is in a server group, but I have confirmed that the escalations are only firing on one of the 3 servers. ARS 6.3, CSS 5.01, ITSM 6.0, Solaris 5.9, Sybase 12.5.3. C Christopher H. Pickering Remedy System Administrator Premiere Global Services, Inc. 100 Tormee Drive Tinton Falls, NJ 07712 732.389.3900 X2411/800.333.0568 X2411 [EMAIL PROTECTED] www.premiereglobal.com No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.5.488 / Virus Database: 269.13.36/1041 - Release Date: 10/1/2007 10:20 AM _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
<<attachment: Glacier Bkgrd.jpg>>
