A couple of things that come to mind: - OS/Java patches for DST tz changes - defect addressed in mid-tier 7.0.1 patch 3 where users that did not authenticate via login.jsp would not have the proper timezone data loaded for the web session (causing weird issues with date/time values). We saw things like 7/0/2007 or 7/1/2007 11:00:00 PM for times that should have been midnight. - client timezone
Axton Grams On 7/19/07, Somers, Chris <[EMAIL PROTECTED]> wrote:
** What patch level is your Midtier at? I ran into this very same problem (hour behind on midtier, correct on client) and was able to fix it by applying Midtier 7.0.1 patch 003. Chris ________________________________ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Kaiser Norm E CIV USAF 96 CS/SCCE Sent: Thursday, July 19, 2007 3:48 PM To: [email protected] Subject: Time an Hour Behind on Midtier Hello everyone: I was hoping folks would help me think this through. Our Midtier is displaying time an hour behind. For example, when a technician submits a ticket, we have an Incident Start time field and it's populated with a time that's an hour ago. The time is correct, however, on the client. So let's throw out the obvious stuff I checked so far: - Time and timezone have been checked on the midtier server. - Time and timezone have been checked on the Remedy server. - Time and timezone have been checked on the client. So…I'm stuck. Any ideas? Norm __20060125_______________________This posting was submitted with HTML in it___ __20060125_______________________This posting was submitted with HTML in it___
_______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
