Re: Help with SLA Problem - MattReinfeldt.com - Remedy Discussion Site

You are not logged in. [Log In] MattReinfeldt.com » Forums » ARSList Archives » Archives - 2006 » Re: Help with SLA Problem

Topic Options

Rate This Topic

#129848 - 01/18/06 04:29 AM Re: Help with SLA Problem
wrentfrow journeyman Registered: 03/11/04 Posts: 126 Loc: Minneapolis, MN	It sounds like your server is setting the time to the value of GMT time - are you sure the server time is set correctly? Keep in mind the AR Server actually stores time in Epoch time (second since Jan 1 1970 -or something like that) so it is always doing the translation when you view the time. Since it is set by a filter the time has to come from the server - I'd check both the time and the time zone to make sure it is correct. From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Sean Garrison Sent: Wednesday, January 18, 2006 9:05 AM To: arslist@ARSLIST.ORG Subject: Help with SLA Problem We have a field that is being set by a filter created by the SLA engine. All it is doing is setting the field based on the value of $TIME$. The issue we are running into is that the time that is being stored in the field is 4 hours later than the current time. There is no other workflow setting the field. The server's time is in EST. What is really odd is if we do a set fields of $TIME$ - 60604 we get the current time minus 4 hours. Any idea on what can cause this? Thanks, Sean This posting was submitted via the Web interface This posting was submitted via the Web interface
Top

#129849 - 01/18/06 04:35 AM Re: Help with SLA Problem [Re: maryann_armitage]
christopher_pickering newbie Registered: 09/22/05 Posts: 13	Sean, Look into your Admin tool and see what the time setting is within. I have the same situation but a 5 hr. differential. If you monitor the admin tool time you will see the time value jump forward and back with no logic. I have found that the server time is set correctly - SUN 9 and the client time is correct WIN XP, it is something else. I started to attempt to track but we decided to upgrade to 6.3, but the problem persists. Chris Pickering From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of William Rentfrow Sent: Wednesday, January 18, 2006 11:29 AM To: arslist@ARSLIST.ORG Subject: Re: Help with SLA Problem It sounds like your server is setting the time to the value of GMT time - are you sure the server time is set correctly? Keep in mind the AR Server actually stores time in Epoch time (second since Jan 1 1970 -or something like that) so it is always doing the translation when you view the time. Since it is set by a filter the time has to come from the server - I'd check both the time and the time zone to make sure it is correct. From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Sean Garrison Sent: Wednesday, January 18, 2006 9:05 AM To: arslist@ARSLIST.ORG Subject: Help with SLA Problem ** We have a field that is being set by a filter created by the SLA engine. All it is doing is setting the field based on the value of $TIME$. The issue we are running into is that the time that is being stored in the field is 4 hours later than the current time. There is no other workflow setting the field. The server's time is in EST. What is really odd is if we do a set fields of $TIME$ - 60604 we get the current time minus 4 hours. Any idea on what can cause this? Thanks, Sean This posting was submitted via the Web interface This posting was submitted via the Web interface This posting was submitted via the Web interface
Top

#129850 - 01/18/06 05:34 AM Re: Help with SLA Problem [Re: maryann_armitage]
msgarris journeyman Registered: 03/11/04 Posts: 51	Thanks for the info . I will continue to monitor to see if we can duplicate the error. Sean -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Pickering, Christopher Sent: Wednesday, January 18, 2006 11:35 AM To: arslist@ARSLIST.ORG Subject: Re: Help with SLA Problem Sean, Look into your Admin tool and see what the time setting is within. I have the same situation but a 5 hr. differential. If you monitor the admin tool time you will see the time value jump forward and back with no logic. I have found that the server time is set correctly - SUN 9 and the client time is correct WIN XP, it is something else. I started to attempt to track but we decided to upgrade to 6.3, but the problem persists. Chris Pickering From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of William Rentfrow Sent: Wednesday, January 18, 2006 11:29 AM To: arslist@ARSLIST.ORG Subject: Re: Help with SLA Problem It sounds like your server is setting the time to the value of GMT time - are you sure the server time is set correctly? Keep in mind the AR Server actually stores time in Epoch time (second since Jan 1 1970 -or something like that) so it is always doing the translation when you view the time. Since it is set by a filter the time has to come from the server - I'd check both the time and the time zone to make sure it is correct. From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Sean Garrison Sent: Wednesday, January 18, 2006 9:05 AM To: arslist@ARSLIST.ORG Subject: Help with SLA Problem We have a field that is being set by a filter created by the SLA engine. All it is doing is setting the field based on the value of $TIME$. The issue we are running into is that the time that is being stored in the field is 4 hours later than the current time. There is no other workflow setting the field. The server's time is in EST. What is really odd is if we do a set fields of $TIME$ - 60604 we get the current time minus 4 hours. Any idea on what can cause this? Thanks, Sean This posting was submitted via the Web interface This posting was submitted via the Web interface This posting was submitted via the Web interface This posting was submitted via the Web interface
Top

View All Topics