Hi John, I've seen this before. The date was hard coded in a macro a user had created. The user tried to circumvent some workflow by adjusting the end date stored in the macro. The server recorded the end date as it was passed from the "tweaked" macro. Eric Cleereman
-----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] Behalf Of Joe DeSouza Sent: Monday, January 22, 2007 4:08 PM To: [email protected] Subject: Re: Resolved date is three years in the future ** someone might have played around with the server time for a while.. and then reset it back.. The server couldn't suddenly decide to timestamp it differently.. and then get back to normal.. Joe D'Souza Remedy Developer / Consultant, BearingPoint, Virginia. ----- Original Message ---- From: John Atherly <[EMAIL PROTECTED]> To: [email protected] Sent: Monday, January 22, 2007 3:29:40 PM Subject: Resolved date is three years in the future I know that the server sets the date and time in the Resolved field but out of 52'000 tickets 5 of them have a date three years from the close date. My answer was the server just had a hiccup. Has anyone seen this before? 6.03 Patch 18 on HP UX __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com __20060125_______________________This posting was submitted with HTML in it___ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
