Hi, Axton: I assume that you are referring to ARS 7.0.01P1.
I do know that before we patched ARS Server 6.3 P18 to P21 that I ran a small test in the Remedy User Tool 6.3 P20 and BMC Remedy User 7.0.01P1. We have a little EPOCH <---> Real Time conversion button on a form. Anytime between 03/11/2007 02:00:00 AM - 02:59:59 AM would yield the value 3, as in 3 seconds. When you back convert it, it comes out as 12/31/1969 06:00:03 PM. Maybe that's the conversion the server is doing. I think you're Eastern right? So it is probably 12/31/1969 05:00:03 PM in your case. Then again, this little conversion is on the client side. By the way, our error message that does popup when we convert back from 3 seconds says, "The date is out of the allowed range of 12/31/1969 through 1/18/2038. Therefore, the calendar popup will be initialized to the current date, and the time dropdown will be set to 12:00:00 AM." ...just something to look at. Michelle -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Axton Sent: Tuesday, March 13, 2007 1:36 PM To: [email protected] Subject: DST Invalid Times Question With 7.0.01p1, if a user submits a record with a date/time at or between 3/11/07 2:00:00 am and 3/11 2:59:59 am, the following error is returned: Date is out of allowed range of 01/01/1970 - 01/19/2038 (GMT) for Windows client. : "<value>": <FieldName> (ARERR 1889) Can anyone confirm is this is how the system behaved prior to the DST patches? Any of you out there on 5.1.2 or unpatched care to test entering a value of "3/11/2007 2:01:00 AM" in one of your DateTime fields to let me know. Thanks, Axton Grams ________________________________________________________________________ _______ 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"
