When User or Admin Tools try to connect to the server an ARERR 90 is received with the message RPC: Program not registered.

View previous topic View next topic Go down

When User or Admin Tools try to connect to the server an ARERR 90 is received with the message RPC: Program not registered.

Post  giby.varghese@gmail.com on Sun Nov 15, 2009 6:20 pm

When trying to login to AR Server, the following error is received on the client: ARERR [90] Cannot establish a network connection to the AR System server : remedy : RPC: Program not register - System error (Connection refused)

giby.varghese@gmail.com

Posts : 107
Points : 222
Reputation : 3
Join date : 2009-11-11

View user profile

Back to top Go down

Re: When User or Admin Tools try to connect to the server an ARERR 90 is received with the message RPC: Program not registered.

Post  giby.varghese@gmail.com on Sun Nov 15, 2009 6:20 pm

An ARERR 90 is a connection failure message. There are many types of ARERR 90s. The specific part of the error that distinguishes this ARERR 90 from others is the "program not registered" part.

This error means simply that AR Server is not running. This is to say, the arserver.exec process is not running. On a Windows Server, often times the Remedy Action Request System Server service will show that its Starting or Started, but confirmation in Task Manager will show that the process is not running.

Normally this occurs when AR Server starts up. One of the first things it does is to connect to the database. If it cannot do this for some reason, it terminates but does nott update the Windows Service Control Manager to show the true state of the service.

Trouble shooting then involves what is happening to AR Server upon startup such that it fails. There are two way to do this:

Method A

Verify the arserver.exec process is not running.
Open a command prompt and change directories to the AR Server installation folder where the arserver.exec file is located. *Note: If the Remedy Action Request System Server service starts as a domain account as opposed to the Local System account, then you must be logged into the server as this account.
Run the following command: arserver -m
Note any errors. Normally, after the version information, it should just hang indefinitely without returning to the command prompt cursor.
Method B

Locate the ar.cfg file within the AR Server installation directory.
Edit the file with Notepad and put your cursor at the end of the last parameters value and hit Enter to bring your cursor to the next line down.
Add the following parameter:
Debug-mode: 1

(Note: If the Debug-mode parameter already exists, you can simply change the value to 1)

Restart the Remedy Action Request System Server service and review the arsql.log that should be located in the AR Server install directory under arserver/db. Note any errors that occur as AR Server attempts to connect to the database.
Method C

Note the arerror.log for any current errors.
Of these two methods, Method A is usually fastest and most reliable. Sometimes the arerror.log will not have the error that caused the failure.



The types of errors youre looking for are usually database connectivity errors, such as a login failure for user ARAdmin. Other examples may include something like this:



*/ BEGIN TRANSACTION
/* Mon Oct 30 2000 12:04:55.0187 */ *** ERROR *** The transaction log in database ARSystem is almost full. Your transaction is being suspended until space is made available in the log. (Sybase 7415)



At any rate, you will now be trouble shooting the root cause of the problem. Technically, the ARERR 90 "program not registered" error is a symptom of this other error that is nott readily reported and must be revealed through the trouble shooting steps listed above.

giby.varghese@gmail.com

Posts : 107
Points : 222
Reputation : 3
Join date : 2009-11-11

View user profile

Back to top Go down

View previous topic View next topic Back to top

- Similar topics

 
Permissions in this forum:
You cannot reply to topics in this forum