Solution: Connecting to BMC Remedy via Opalis Integration Server fails with "Connection test failed"

Article
11/03/2010

Here's a solution we ran across the other day and since I didn't see it published here I thought it would be worth a mention.

Symptoms

You may be unable to connect to BMC Remedy via Opalis Integration Server. When you attempt to do so you receive the following error when testing the BMC Remedy Connection:

Connection test failed. Please make sure that the server name, username, password and application are correct.

Details: AR System call failed. Details:
Message number: 90:
Cannot open catalog; Message number = 90
HOSTNAME.com : RPC: Rpcbind failure - RPC: Unable to receive

The following error is also received when attempting to enumerate the catalog from the BMC Connection Settings page:

Unable to connect to the AR System server and as a result the application list is not available.

Cause

Error 90 within BMC Remedy indicates a network connection or interruption error has occurred. This issue often occurs when using a non-standard port to connect to BMC Remedy. If the Portmapper service is not running, an environment variable must be defined in order for Opalis to successfully connect to BMC Remedy using the non-standard TCP port.

Resolution

In order to successfully connect Opalis Integration Server to BMC Remedy using a non-standard connection port, the following environment variable must be defined on the Opalis Action Server from where the connection originates.

Variable: ARTCPPORT
Value: <Port Number>

Once the appropriate system environment variable has been set, reboot the server and test the connection to BMC Remedy once again. The connection should complete a test successfully with the variable defined.

Hope this helps,

Nicholas Dodge | Senior Support Escalation Engineer

Solution: Connecting to BMC Remedy via Opalis Integration Server fails with "Connection test failed"

Symptoms

Cause

Resolution

Additional resources