Ive noticed that as well. I have seen it typically with the first HPD:AssignmentLog entry for a particular ticket. Obviously it is performing some Application-Business-Time-Add but the original date is not filled in so it assumes "0" time which depending on your server's timezone might put it at 12/31/1969 or 1/1/1970.
Never been pressed by my users to investigate this but I would be curious to know if there is a bug submitted to BMC about this. ITSM 7.02 patch 005 Thanks Peter Lammey ESPN IT Client Architecture and Automation 860-766-4761 ________________________________ From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of Frank Caruso Sent: Thursday, May 28, 2009 10:16 AM To: arslist@ARSLIST.ORG Subject: Bad HPD Assignment Records ** Has anybody seen issues with ITSM 7 creating HPD Assignment records with Actual and Business Duration (Seconds) that are equal to roughly 40 years time? The seconds value are 1242994998 and bigger. Not all of the assignment records are like this. I think what is happening is that a bad Date (DateTime) value is getting sent to this form and getting set to 12/31/1969 before calculations are made. Thoughts? Frank Caruso _Platinum Sponsor: rmisoluti...@verizon.net ARSlist: "Where the Answers Are"_ ________________________________ Please consider the environment before printing this e-mail. _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor:rmisoluti...@verizon.net ARSlist: "Where the Answers Are"
