I'm getting alot of timeouts from the server

Error:AR System server terminated -- fatal error encountered (ARNOTE 21)
Tue Dec 21 08:18:20 1999 AR System server terminated unexpectedly -- restarting
(ARTCNOTE 802)
Tue Dec 21 08:18:20 1999 Server -- 390600
Tue Dec 21 08:33:25 1999 390600 : AR System server terminated when a
signal/exception was received by the server (ARNOTE 20)

Does anyone know what could be causing this? I've made a call in to Remedy with
no luck.

Thanks


To Unsubscribe send e-mail to:
body of text is: unsubscribe arslist

things. The only way that I could determine what was happening was to turn on
SQL and API logging in the Admin Tool, then compare the times in that log file
to the times in the arerror.log to pinpoint the cause of the problem.

good luck!

Heidi Wagner
Montage IT Services, Ltd.
(613) 232-2760
heidi.wagner@montage.ca

>===== Original Message From Isabelle DeBurgo
=====
>I thought this would be an Urgent issue with Remedy -
>
>I'm getting alot of timeouts from the server
>
>Error:AR System server terminated -- fatal error encountered (ARNOTE 21)
>Tue Dec 21 08:18:20 1999 AR System server terminated unexpectedly --
restarting
>(ARTCNOTE 802)
>Tue Dec 21 08:18:20 1999 Server -- 390600
>Tue Dec 21 08:33:25 1999 390600 : AR System server terminated when a
>signal/exception was received by the server (ARNOTE 20)
>
>Does anyone know what could be causing this? I've made a call in to Remedy
with
>no luck.
>
>Thanks
>
>
>To Unsubscribe send e-mail to:
>body of text is: unsubscribe arslist


To Unsubscribe send e-mail to:
body of text is: unsubscribe arslist

To Unsubscribe send e-mail to:
body of text is: unsubscribe arslist

I have seen this happen when we have restarted the server and the Database
was not fully started. Also have seen errors like this when the RPC port is
not available for the Server daemons. I would verify if the RPC is not
conflicting with something else.

Hope that helps,

Ron Smith
Remedy System Administrator
Providence Health System



-----Original Message-----
From: Isabelle DeBurgo [mailto:Isabelle_Deburgo@DISCOVERY.COM]
Sent: Tuesday, December 21, 1999 9:37 AM
To: ARSLIST@LISTSERV.VISTAIT.COM
Subject: Server Down


I thought this would be an Urgent issue with Remedy -

I'm getting alot of timeouts from the server

Error:AR System server terminated -- fatal error encountered (ARNOTE 21)
Tue Dec 21 08:18:20 1999 AR System server terminated unexpectedly --
restarting
(ARTCNOTE 802)
Tue Dec 21 08:18:20 1999 Server -- 390600
Tue Dec 21 08:33:25 1999 390600 : AR System server terminated when a
signal/exception was received by the server (ARNOTE 20)

Does anyone know what could be causing this? I've made a call in to Remedy
with
no luck.

Thanks


To Unsubscribe send e-mail to:
body of text is: unsubscribe arslist


To Unsubscribe send e-mail to:
body of text is: unsubscribe arslist

Shawn



I thought this would be an Urgent issue with Remedy -

I'm getting alot of timeouts from the server

Error:AR System server terminated -- fatal error encountered (ARNOTE 21)
Tue Dec 21 08:18:20 1999 AR System server terminated unexpectedly --
restarting
(ARTCNOTE 802)
Tue Dec 21 08:18:20 1999 Server -- 390600
Tue Dec 21 08:33:25 1999 390600 : AR System server terminated when a
signal/exception was received by the server (ARNOTE 20)

Does anyone know what could be causing this? I've made a call in to Remedy
with
no luck.

--

==============================
Shawn Abigail
Manager, Remedy Systems
Newbridge Networks Corporation
External: (613) 599-3600 x3237
Internal: 720-3237
sabigail@newbridge.com
==============================

To Unsubscribe send e-mail to: body of text is: unsubscribe arslist

not always, was to set a field with the status-history assigned time value
on submit. Since this is the first status in my record, it is not available
until after submit. This killed the arserverd running the process about 80%
of the time. Since we have MPSO, it didn't always time out. I found the
problem on the development machine which had only the one server, 390600.
It always timed out when the arserver daemon died.

So look for workflow problems like this. Look for set fields operations
when the info is unavailable, things like that.

Another time we had this problem--arserverd being killed with signal 11 on
a regular basis--the cause was a bug in the ARS as compiled for our
operating system. A patch fixed the problem.

At 12:37 PM 12/21/99 -0500, you wrote:
>I thought this would be an Urgent issue with Remedy -
>
>I'm getting alot of timeouts from the server
>
>Error:AR System server terminated -- fatal error encountered (ARNOTE 21)
>Tue Dec 21 08:18:20 1999 AR System server terminated unexpectedly --
>restarting
>(ARTCNOTE 802)
>Tue Dec 21 08:18:20 1999 Server -- 390600
>Tue Dec 21 08:33:25 1999 390600 : AR System server terminated when a
>signal/exception was received by the server (ARNOTE 20)
>
>Does anyone know what could be causing this? I've made a call in to
>Remedy with
>no luck.
>
>Thanks
>
>
>To Unsubscribe send e-mail to:
>body of text is: unsubscribe arslist


To Unsubscribe send e-mail to:
body of text is: unsubscribe arslist

I've seen this before on NT - it's symptomatic of a memory problem somewhere
and can be triggered by escalations. I've found that changing the version
of the WinNT file msvcrt.dll sometimes helps (on one server, reverting to an
earlier version!)

HTH

David Sanders
Independent Remedy Consultant
__________________________
Westover Consulting Ltd
tel: +44 (0)410 377761
email: sandersd@globalnet.co.uk



----- Original Message -----
From: Isabelle DeBurgo
To:
Sent: Tuesday, December 21, 1999 5:37 PM
Subject: Server Down


> I thought this would be an Urgent issue with Remedy -
>
> I'm getting alot of timeouts from the server
>
> Error:AR System server terminated -- fatal error encountered (ARNOTE 21)
> Tue Dec 21 08:18:20 1999 AR System server terminated unexpectedly --
restarting
> (ARTCNOTE 802)
> Tue Dec 21 08:18:20 1999 Server -- 390600
> Tue Dec 21 08:33:25 1999 390600 : AR System server terminated when a
> signal/exception was received by the server (ARNOTE 20)
>
> Does anyone know what could be causing this? I've made a call in to
Remedy with
> no luck.
>
> Thanks
>
>
> To Unsubscribe send e-mail to:
> body of text is: unsubscribe arslist
>


To Unsubscribe send e-mail to:
body of text is: unsubscribe arslist