Hi there,

The following entry in my arerror.log appeared after one of our servers
failed to evaluate the $TIMESTAMP$ variable correctly. This occurred twice,
first at execution value 500 when $TIMESTAMP$ is used in an artime setfields
(sets a hidden date/time field) run process command (this is what produced
the error in the error log) and secondly at execution value 510 where the
$TIMESTAMP$ value is populated in the Resolved Time field during a simple
set fields action. These two actions occur in two separate filters. The Last
Modified date is correct, as is the Resolved.TIME date, the Resolved Time
field should have contained the same value as the Last Modified field.


Thu Dec 21 15:57:39 2000 390620 : Filter/escalation 'set field' process
timed out before completion (value not changed) (ARERR 39)
Thu Dec 21 15:57:39 2000 D:\APPS\REMEDY/artime -h
D:\APPS\REMEDY\conf\holiday.txt -w D:\APPS\REMEDY\Conf\workdays.txt -m a -s
"12/31/69 7:00:00 PM" -a 30 -u d

I have since found a 2nd occurrence of this error on another server. Again
it displays the exact same date/time value ("12/31/69 7:00:00 PM") in both
the arerror.log and in the Resolved Time field.

We are running:
ARS4.0.3 server with patch 947 (as well as the French Pack) on NT SP6a
ARS4.5.1 user tool patch 966
Oracle 8.0.5

Has anyone seen this before and is there a fix or work around?

Thanks
...anik

Egan,
2 possible suggestions here.
1. the client is wrong.. (most likely not the case)
2. the Timeout setting is too small for the computation.
a. modify the timeout setting to see if it continues.
-Severinformation, timeouts, process time Add 5 seconds.
It could be the server got busy and just ran out of time.
b. if it contines check on 1. if the client
Hope this helps.

-----Original Message-----
From: Egan, Anik [mailto:Anik.Egan@CCRA-ADRC.GC.CA]
Sent: Thursday, December 28, 2000 11:22 AM
To: ARSLIST@LISTSERV.VISTAIT.COM
Subject: $TIMESTAMP$ error


**

Hi there,

The following entry in my arerror.log appeared after one of our servers
failed to evaluate the $TIMESTAMP$ variable correctly. This occurred twice,
first at execution value 500 when $TIMESTAMP$ is used in an artime setfields
(sets a hidden date/time field) run process command (this is what produced
the error in the error log) and secondly at execution value 510 where the
$TIMESTAMP$ value is populated in the Resolved Time field during a simple
set fields action. These two actions occur in two separate filters. The Last
Modified date is correct, as is the Resolved.TIME date, the Resolved Time
field should have contained the same value as the Last Modified field.


Thu Dec 21 15:57:39 2000 390620 : Filter/escalation 'set field' process
timed out before completion (value not changed) (ARERR 39)
Thu Dec 21 15:57:39 2000 D:\APPS\REMEDY/artime -h
D:\APPS\REMEDY\conf\holiday.txt -w D:\APPS\REMEDY\Conf\workdays.txt -m a -s
"12/31/69 7:00:00 PM" -a 30 -u d

I have since found a 2nd occurrence of this error on another server. Again
it displays the exact same date/time value ("12/31/69 7:00:00 PM") in both
the arerror.log and in the Resolved Time field.

We are running:
ARS4.0.3 server with patch 947 (as well as the French Pack) on NT SP6a
ARS4.5.1 user tool patch 966
Oracle 8.0.5

Has anyone seen this before and is there a fix or work around?

Thanks
...anik

Anik,

It worths the try to store the date in a temp integer field and run artime
with integer instead of date/time. Most of the issues with the artime comes
from inappropriate date/time format, using integer will avoid any
misinterpretation.

Nicky Madjarov
Intellico Solutions, Inc.

1507 Hermitage Pk. Dr.
Hermitage, TN 37076
Phone: (615) 883 7591
Mobil : (201) 747 8672
Pager: 2017478672@mobile.att.net
e-mail: nickym@intellicosolutions.net
http://www.intellicosolutions.net
----- Original Message -----
From: "Egan, Anik"
To:
Sent: Thursday, December 28, 2000 10:21 AM
Subject: $TIMESTAMP$ error


> **
>
> Hi there,
>
> The following entry in my arerror.log appeared after one of our servers
> failed to evaluate the $TIMESTAMP$ variable correctly. This occurred
twice,
> first at execution value 500 when $TIMESTAMP$ is used in an artime
setfields
> (sets a hidden date/time field) run process command (this is what produced
> the error in the error log) and secondly at execution value 510 where the
> $TIMESTAMP$ value is populated in the Resolved Time field during a simple
> set fields action. These two actions occur in two separate filters. The
Last
> Modified date is correct, as is the Resolved.TIME date, the Resolved Time
> field should have contained the same value as the Last Modified field.
>
>
> Thu Dec 21 15:57:39 2000 390620 : Filter/escalation 'set field' process
> timed out before completion (value not changed) (ARERR 39)
> Thu Dec 21 15:57:39 2000 D:\APPS\REMEDY/artime -h
> D:\APPS\REMEDY\conf\holiday.txt -w D:\APPS\REMEDY\Conf\workdays.txt -m
a -s
> "12/31/69 7:00:00 PM" -a 30 -u d
>
> I have since found a 2nd occurrence of this error on another server. Again
> it displays the exact same date/time value ("12/31/69 7:00:00 PM") in both
> the arerror.log and in the Resolved Time field.
>
> We are running:
> ARS4.0.3 server with patch 947 (as well as the French Pack) on NT SP6a
> ARS4.5.1 user tool patch 966
> Oracle 8.0.5
>
> Has anyone seen this before and is there a fix or work around?
>
> Thanks
> ...anik
>
>
>

>

Hi Patrick,

Thanks for the feedback.
I figured it wouldn't be the client since the $TIMESTAMP$ value is being
evaluated on the server side for the filters. My timeout setting for Run
Process is currently 20 seconds, this may have some affect on the Run
Process set fields that is producing the error in the arerror.log, but I
didn't think this would have any bearing on the filter (EO 510) that fires a
simple set fields for the Resolved Time field.

Or am I going under completely the wrong assumptions here?

Thanks

...anik

-----Original Message-----
From: Zandi Patrick S TSgt AFRL/IFOSS [mailto:Patrick.Zandi@RL.AF.MIL]
Sent: December 28, 2000 11:38 AM
To: ARSLIST@LISTSERV.VISTAIT.COM
Subject: Re: $TIMESTAMP$ error


**

Egan,
2 possible suggestions here.
1. the client is wrong.. (most likely not the case)
2. the Timeout setting is too small for the computation.
a. modify the timeout setting to see if it continues.
-Severinformation, timeouts, process time Add 5 seconds.
It could be the server got busy and just ran out of time.
b. if it contines check on 1. if the client
Hope this helps.

-----Original Message-----
From: Egan, Anik [mailto:Anik.Egan@CCRA-ADRC.GC.CA]
Sent: Thursday, December 28, 2000 11:22 AM
To: ARSLIST@LISTSERV.VISTAIT.COM
Subject: $TIMESTAMP$ error


**

Hi there,

The following entry in my arerror.log appeared after one of our servers
failed to evaluate the $TIMESTAMP$ variable correctly. This occurred twice,
first at execution value 500 when $TIMESTAMP$ is used in an artime setfields
(sets a hidden date/time field) run process command (this is what produced
the error in the error log) and secondly at execution value 510 where the
$TIMESTAMP$ value is populated in the Resolved Time field during a simple
set fields action. These two actions occur in two separate filters. The Last
Modified date is correct, as is the Resolved.TIME date, the Resolved Time
field should have contained the same value as the Last Modified field.


Thu Dec 21 15:57:39 2000 390620 : Filter/escalation 'set field' process
timed out before completion (value not changed) (ARERR 39)
Thu Dec 21 15:57:39 2000 D:\APPS\REMEDY/artime -h
D:\APPS\REMEDY\conf\holiday.txt -w D:\APPS\REMEDY\Conf\workdays.txt -m a -s
"12/31/69 7:00:00 PM" -a 30 -u d

I have since found a 2nd occurrence of this error on another server. Again
it displays the exact same date/time value ("12/31/69 7:00:00 PM") in both
the arerror.log and in the Resolved Time field.

We are running:
ARS4.0.3 server with patch 947 (as well as the French Pack) on NT SP6a
ARS4.5.1 user tool patch 966
Oracle 8.0.5

Has anyone seen this before and is there a fix or work around?

Thanks
...anik