The server is timing out.  Make sure your api, sql, filter, and escalation
logs are enabled, and when the timeouts start, grab a copy of the logs then
restart ARS.  Look in the logs for the last thing that was taking place and
you will have your answer.  It could be any number of things causing the
timeout.... the logs will point you in the right direction.

If you have your arserver set up to create a backup log, the .bak files
will be the logs before you restart the server and you can look in there to
see what is going on.

Axton Grams

On Fri, Feb 10, 2012 at 9:34 AM, Peters, Ron <[email protected]> wrote:

> **
>
> Hello all,****
>
> ** **
>
> Having some AR server issues. Something has been happening in the mornings
> about 6am in that our service desk can’t access Remedy. This started in
> Decemeber but only once. Then twice in January and now a couple times this
> week. The first few times it resolved itself after about 30 minutes but
> this week we had to restart the AR service on the server to get it back.
> The following is the arerror log from this morning. I’ve contacted our
> DBA’s to see if they notice anything but since an AR restart resolves it,
> I’m not convinced it’s a DB issue. Any thoughts?****
>
> ** **
>
> Thanks.****
>
> ** **
>
> Fri Feb 10 06:25:30 2012  AssignEng : Timeout during database update --
> the operation has been accepted by the server and will usually complete
> successfully (OUR_AR_SERVER)  ARERR - 92****
>
> Fri Feb 10 06:25:30 2012  AssignEng : AR System Application server
> terminated -- fatal error encountered (ARAPPNOTE 4501)****
>
> Fri Feb 10 06:25:31 2012  SLMCS : Timeout during database update -- the
> operation has been accepted by the server and will usually complete
> successfully (OUR_AR_SERVER)  ARERR - 92****
>
> Fri Feb 10 06:25:31 2012  SLMCS : AR System Application server terminated
> -- fatal error encountered (ARAPPNOTE 4501)****
>
> Fri Feb 10 06:27:32 2012  AssignEng : Timeout during database update --
> the operation has been accepted by the server and will usually complete
> successfully (OUR_AR_SERVER)  ARERR - 92****
>
> Fri Feb 10 06:27:32 2012  AssignEng : AR System Application server
> terminated -- fatal error encountered (ARAPPNOTE 4501)****
>
> Fri Feb 10 06:27:32 2012  SLMCS : Timeout during database update -- the
> operation has been accepted by the server and will usually complete
> successfully (OUR_AR_SERVER)  ARERR - 92****
>
> Fri Feb 10 06:27:32 2012  SLMCS : AR System Application server terminated
> -- fatal error encountered (ARAPPNOTE 4501)****
>
> Fri Feb 10 06:29:32 2012  AssignEng : Timeout during database update --
> the operation has been accepted by the server and will usually complete
> successfully (OUR_AR_SERVER)  ARERR - 92****
>
> Fri Feb 10 06:29:32 2012  AssignEng : AR System Application server
> terminated -- fatal error encountered (ARAPPNOTE 4501)****
>
> Fri Feb 10 06:29:32 2012  SLMCS : Timeout during database update -- the
> operation has been accepted by the server and will usually complete
> successfully (OUR_AR_SERVER)  ARERR - 92****
>
> Fri Feb 10 06:29:32 2012  SLMCS : AR System Application server terminated
> -- fatal error encountered (ARAPPNOTE 4501)****
>
> Fri Feb 10 06:30:05 2012  BRIE : Timeout during database query -- consider
> using more specific search criteria to narrow the results, and retry the
> operation (OUR_AR_SERVER)  ARERR - 94****
>
> Fri Feb 10 06:31:32 2012  AssignEng : Timeout during database update --
> the operation has been accepted by the server and will usually complete
> successfully (OUR_AR_SERVER)  ARERR - 92****
>
> Fri Feb 10 06:31:32 2012  AssignEng : AR System Application server
> terminated -- fatal error encountered (ARAPPNOTE 4501)****
>
> Fri Feb 10 06:31:32 2012  SLMCS : Timeout during database update -- the
> operation has been accepted by the server and will usually complete
> successfully (OUR_AR_SERVER)  ARERR - 92****
>
> Fri Feb 10 06:31:32 2012  SLMCS : AR System Application server terminated
> -- fatal error encountered (ARAPPNOTE 4501)****
>
> Fri Feb 10 06:33:32 2012  AssignEng : Timeout during database update --
> the operation has been accepted by the server and will usually complete
> successfully (OUR_AR_SERVER)  ARERR - 92****
>
> Fri Feb 10 06:33:32 2012  AssignEng : AR System Application server
> terminated -- fatal error encountered (ARAPPNOTE 4501)****
>
> Fri Feb 10 06:33:32 2012  SLMCS : Timeout during database update -- the
> operation has been accepted by the server and will usually complete
> successfully (OUR_AR_SERVER)  ARERR - 92****
>
> Fri Feb 10 06:33:32 2012  SLMCS : AR System Application server terminated
> -- fatal error encountered (ARAPPNOTE 4501)****
>
> Fri Feb 10 06:35:02 2012  CMDB Dispatcher : Timeout during database query
> -- consider using more specific search criteria to narrow the results, and
> retry the operation (OUR_AR_SERVER)  ARERR - 94****
>
> Fri Feb 10 06:35:05 2012  BRIE : Timeout during database query -- consider
> using more specific search criteria to narrow the results, and retry the
> operation (OUR_AR_SERVER)  ARERR - 94****
>
> Fri Feb 10 06:35:32 2012  AssignEng : Timeout during database update --
> the operation has been accepted by the server and will usually complete
> successfully (OUR_AR_SERVER)  ARERR - 92****
>
> Fri Feb 10 06:35:32 2012  AssignEng : AR System Application server
> terminated -- fatal error encountered (ARAPPNOTE 4501)****
>
> Fri Feb 10 06:35:32 2012  SLMCS : Timeout during database update -- the
> operation has been accepted by the server and will usually complete
> successfully (OUR_AR_SERVER)  ARERR - 92****
>
> Fri Feb 10 06:35:32 2012  SLMCS : AR System Application server terminated
> -- fatal error encountered (ARAPPNOTE 4501)****
>
> Fri Feb 10 06:37:32 2012  AssignEng : Timeout during database update --
> the operation has been accepted by the server and will usually complete
> successfully (OUR_AR_SERVER)  ARERR - 92****
>
> Fri Feb 10 06:37:32 2012  AssignEng : AR System Application server
> terminated -- fatal error encountered (ARAPPNOTE 4501)****
>
> Fri Feb 10 06:37:32 2012  SLMCS : Timeout during database update -- the
> operation has been accepted by the server and will usually complete
> successfully (OUR_AR_SERVER)  ARERR - 92****
>
> Fri Feb 10 06:37:32 2012  SLMCS : AR System Application server terminated
> -- fatal error encountered (ARAPPNOTE 4501)****
>  _attend WWRUG12 www.wwrug.com ARSlist: "Where the Answers Are"_

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"

Reply via email to