I figured out what was causing the exceptions (even though it is a little disappointing). The notification that I had configured was hitting on many, MANY records on the helpdesk form and attempting to send an email for each. It think the underlying mail daemon was simply being hammered too hard?
Either way, I've made the modifications and isolated the individual records I'm concerned with and I now have my *first ever* active link, filter, and escalation working. I wouldn't have been able to do it without this list. Thanks everyone! Scott Olsen. On 8/8/07, Tony Worthington <[EMAIL PROTECTED]> wrote: > > Welcome to 7.0 > > :P > > > -- > Tony Worthington > [EMAIL PROTECTED] > 262-703-5911 > > > > Lateralus <[EMAIL PROTECTED]> > Sent by: "Action Request System discussion list(ARSList)" > <arslist@ARSLIST.ORG> > 08/08/2007 12:26 PM > Please respond to > arslist@ARSLIST.ORG > > > To > arslist@ARSLIST.ORG > cc > > Subject > Re: HelpDesk escalations > > > > > > > ** WTF... > > I've tried configuring a fairly straightforward notification using the > email method, and now it's actually *crashing* the server process?!? > Ummm... it CAN'T really be this finicky... CAN IT? > > Wed Aug 08 13:49:45 2007 390603 : AR System server terminated when a > signal/exception was received by the server (ARNOTE 20) > Wed Aug 08 13:49:45 2007 0xc0000005 > Wed Aug 08 13:49:45 2007 390603 : AR System server terminated -- fatal > error encountered (ARNOTE 21) > Wed Aug 08 13:49:46 2007 390603 : AR System server terminated when a > signal/exception was received by the server (ARNOTE 20) > Wed Aug 08 13:49:46 2007 > Timestamp: Wed Aug 08 2007 13:49:47.2030 > Thread Id: 3328 > Version: 7.0.01 patch 001 200701111654 Jan 11 2007 20:15:38 > ServerName: VM-RMDYSANDBOX > Database: SQL -- SQL Server > Hardware: Intel Pentium > OS: Windows NT 5.2 > RPC Id: 385 > RPC Call: 10003 > RPC Queue: 390603 > Protocol Version: 0 > Client IP Address: > Form: HPD:Help Desk > Logging On: Alert API Escalation SQL User Thread > Code: c0000005 > Operation: read > Access Addr: 0x0 > Stack Begin: > Addr: 006E3FFD > Addr: 00000001 > Stack End > > has *anyone* had anything similar happen? > > I don't know where I would turn without this list. > > Thanks. > > On 8/7/07, Roger Justice <[EMAIL PROTECTED]> wrote: > ** The request ID and the Incident ID are created differently in ITSM 7 > and can be different numbers. If you are not sending a URL use the > Incident ID if you are sending a URL you will need to include the Request > ID. > > > > -----Original Message----- > From: Lateralus <[EMAIL PROTECTED]> > To: arslist@ARSLIST.ORG > Sent: Tue, 7 Aug 2007 3:42 pm > Subject: HelpDesk escalations > > ** Hi Everyone, > > I'm new to the list, and a have a quick (and probably stupid) question: > > I've attempted to create a simple escalation for the Helpdesk form that > sends a notification whenever the Estimated Resolution Date is blown. I > believe I've got it working, but when the alert goes out... the Request ID > doesn't actually match the Incident ID? Can anyone help me understand the > difference here? What am I missing? I don't see any relation within the > Incident to the Request ID listed on the alert. > > Thanks, > > Scott Olsen > > > __20060125_______________________This posting was submitted with HTML in > it___ > AOL now offers free email to everyone. Find out more about what's free > from AOL at AOL.com . > __20060125_______________________This posting was submitted with HTML in > it___ > > __20060125_______________________This posting was submitted with HTML in > it___ > > > CONFIDENTIALITY NOTICE: > This is a transmission from Kohl's Department Stores, Inc. > and may contain information which is confidential and proprietary. > If you are not the addressee, any disclosure, copying or distribution or > use of the contents of this message is expressly prohibited. > If you have received this transmission in error, please destroy it and > notify us immediately at 262-703-7000. > > CAUTION: > Internet and e-mail communications are Kohl's property and Kohl's reserves > the right to retrieve and read any message created, sent and > received. Kohl's reserves the right to monitor messages to or from > authorized Kohl's Associates at any time > without any further consent. > > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where > the Answers Are" > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
