The BMC Remedy AR System server also provides error logs, such as arerror.log and arapi.log. The arerror.log file records all AR System server error messages, such as notifying you that your AR System server stopped responding, and so on. For example, you might receive an ARERR 92 Timeout during database update error on the BMC Atrium Core client. One of the possible causes for this timeout error might be that the AR System server stopped responding. To troubleshoot this error, try to reproduce the error and examine other logs to identify the cause of the error. The arapi.log file traces all AR System API calls that are run on the server. Both arerror.log and arapi.log files are located by default in the C: Program Files BMC Software ARSystem Arserver Db subdirectory of your AR System server installation directory.

If you enable the Filter and SQL logging options, the log files are created under the Program Files BMC Software ARSystem Arserver Db subdirectory of your installation directory by default ( Windows ) or /db ( UNIX ). You can change the file names and location of any of these logs at any time. Make sure that you examine the arerror.log and cmdbengdebug.log files for any CMDB Engine library loading errors, If any errors occurred when loading the library during AR System server starts up, BMC Atrium Core might not function correctly. In addition to logging errors to the cmdbengdebug.log file, BMC Atrium Core also writes to the arerror.log file under certain circumstances, such as the following scenarios: • If the RPC program was not registered when making a BMC Atrium Core API call from a BMC Atrium Core client, an error is written to arerror.log. This error occurs because the AR System server did not load the CMDB Engine library. • If the OBJSTR:Class form that holds BMC Atrium CMDB metadata is not available on the server, an ARERR 9755 error is written to arerror.log, such as the following example, and the CMDB Engine library fails to load: Thu May 03 15: 390600: Error encountered while initializing (Initialization routine) the shared library (ARERR 9755) Thu May 03 15: bmc.cmdb.cmdbEngine Thu May 03 15: 390600: Form does not exist on server: OBJSTR:Class (ARERR 303) For more information about these AR System server log files, see in the BMC Remedy Action Request System online documentation.

In side the back and neck. Report Broken Links Issue: * THE BACK HORN – B-SIDE THE BACK HORN Released: 2013 Genre: Rock Bitrate: MP3 320 KBPS RAR / 349 MB Tracklist: Disc1 01.

Kevin, Also if that does not work, check if the transaction logs on your SQL server are full. Flush it if necessary. Also check the size and usage of the DB as well as the log file. SQL 2005 auto sets them to increment, but if the disk these files are on is getting full, this auto increment would fail. Make sure that the disk that contains these files has enough free space. Joe -----Original Message----- From: Action Request System discussion list(ARSList) [ Behalf Of Kevin Begosh Sent: Monday, July 12, 2010 3:11 PM To: arslist@ARSLIST.ORG Subject: Re: ARERR 92 Server Timeout During Database Update ** it is not a prod box. I will try the Delay-Recache-Time option. Download mac os x free.

On Mon, Jul 12, 2010 at 3:03 PM, Garrison, Sean (Norcross) wrote: ** Try setting “Delay-Recache-Time” to a few minutes. My suggestion would be more than the amount of time it takes to restart an arserver. That way if your update for some reason causes a server restart then you wouldn’t be down while it is restarting. I would also suggest turning developer cache mode off since it is a prod box. Sean From: Action Request System discussion list(ARSList) [] On Behalf Of Kevin Begosh Sent: Monday, July 12, 2010 1:52 PM To: arslist@ARSLIST.ORG Subject: Re: ARERR 92 Server Timeout During Database Update ** it is not our current prod. It is the environment that is going to be prod. Dev Cache Mode is checked.

Re: ARERR [92] Timeout during database update -- the operation has been accepted by the server and will usually complete successfully: Jayesh Panchal Mar 7, 2013 1:55 AM ( in response to Ashwanth Padmanabhan ). I'm using ARInside 3.0.1, but it fails to extract active links with ARERR 93 (basically it's timed out). I figured out from the API log that the timeout happens after 5 minutes.