Hi, I have encountered an fatal error when i used the ARS6.3 JAVA API to access the ARS. The detail message is as below:
MessageType: 2
MessageNum: 90
MessageText: Cannot establish a network connection to the AR System server.
AppendedText: arsdev919 : RPC: Rpcbind failure - RPC: Unable to receive.
Env:
ARS : 6.3 For Windows
OS : windows server 2003
JDK: 1.4.2_07
Database: SQL Server 2000 with SP4
I just compile the sample code of JavaDriver.java ,and run:
....
Command: log
Control record:
Authentication String ():
User name (): Demo
Password():
Locale () :
TimeZone () :
Server () : arsdev919 (note: has been add to the hosts)

Command: ver
VERIFY USER
Results
ReturnCode: ERROR
Status List : 1 items
Status Struct :
Message type : ERROR
Message number : 90
Message: Cannot establish a network connection to the AR System server.
Appended: arsdev919 : RPC: Rpcbind failure - RPC: Unable to receive


Command:

....

Who can help me ? or any suggestion? Thanks a lot!

We also have that same problem. The problem started occurring after we had installed ARS 6.3 with a 6.3 Mid-Tier. In our case, the problem is only caused by search menu's being accessed from the web and we can't find the cause at all. Flushing the mid-tier cache solves the problem, but eventually the problem keeps on coming back.

This is what shows up in our mid-tier log:

Code:

---

  4-okt-2005 9:48:09 com.remedy.arsys.support.Log log
SEVERE: GoatException during NDXRequest: 
ARERR [90] Cannot establish a network connection to the AR System server : ARS63UK : RPC: Rpcbind failure - RPC: Unable to receive
	at com.remedy.arsys.goat.Menu.expandMenu(Unknown Source)
	at com.remedy.arsys.goat.QueryMenu.emitJS(Unknown Source)
	at com.remedy.arsys.backchannel.ExpandMenuAgent.process(Unknown Source)
	at com.remedy.arsys.backchannel.NDXRequest.<init>(Unknown Source)
	at com.remedy.arsys.backchannel.EntryListBase.<init>(Unknown Source)
	at com.remedy.arsys.backchannel.NDXExpandMenu.<init>(Unknown Source)
	at com.remedy.arsys.backchannel.ExpandMenuAgent.<init>(Unknown Source)
	at com.remedy.arsys.backchannel.NDXFactory.handleRequest(Unknown Source)
	at com.remedy.arsys.stubs.BackchannelServlet.doRequest(Unknown Source)
	at com.remedy.arsys.stubs.GoatServlet.postInternal(Unknown Source)
	at com.remedy.arsys.stubs.GoatHttpServlet.doGet(Unknown Source)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:743)
Caused by: 
MessageType: 2
MessageNum: 90
MessageText: Cannot establish a network connection to the AR System server
AppendedText: ARS63UK : RPC: Rpcbind failure - RPC: Unable to receive
	at com.remedy.arsys.api.Proxy.ARExpandMenu(Native Method)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
	at com.newatlanta.servletexec.SERequestDispatcher.forwardServlet(SERequestDispatcher.java:638)
	at com.newatlanta.servletexec.SERequestDispatcher.forward(SERequestDispatcher.java:236)
	at com.newatlanta.servletexec.SERequestDispatcher.internalForward(SERequestDispatcher.java:283)
	at com.newatlanta.servletexec.ApplicationInfo.processApplRequest(ApplicationInfo.java:1827)
	at com.newatlanta.servletexec.ServerHostInfo.processApplRequest(ServerHostInfo.java:919)
	at com.newatlanta.servletexec.ServletExec.ProcessRequest(ServletExec.java:1091)
	at com.newatlanta.servletexec.ServletExec.ProcessRequest(ServletExec.java:1002)

---

Remedy's response is that the problem has to do with a firewall but we can also reproduce the error locally (by opening IE from the server machine)

The server machine is running on Windows XP SP2 using ARS 6.3/mid-tier 6.3 (both patch 13). The default Windows firewall is turned OFF all the time

Does anyone else have (or had) this problem??

We also have that same problem. The problem started occurring after we had installed ARS 6.3 with a 6.3 Mid-Tier. In our case, the problem is only caused by search menu's being accessed from the web and we can't find the cause at all. Flushing the mid-tier cache solves the problem, but eventually the problem keeps on coming back.

This is what shows up in our mid-tier log:

Code:

---

  4-okt-2005 9:48:09 com.remedy.arsys.support.Log log
SEVERE: GoatException during NDXRequest: 
ARERR [90] Cannot establish a network connection to the AR System server : ARS63UK : RPC: Rpcbind failure - RPC: Unable to receive
	at com.remedy.arsys.goat.Menu.expandMenu(Unknown Source)
	at com.remedy.arsys.goat.QueryMenu.emitJS(Unknown Source)
	at com.remedy.arsys.backchannel.ExpandMenuAgent.process(Unknown Source)
	at com.remedy.arsys.backchannel.NDXRequest.<init>(Unknown Source)
	at com.remedy.arsys.backchannel.EntryListBase.<init>(Unknown Source)
	at com.remedy.arsys.backchannel.NDXExpandMenu.<init>(Unknown Source)
	at com.remedy.arsys.backchannel.ExpandMenuAgent.<init>(Unknown Source)
	at com.remedy.arsys.backchannel.NDXFactory.handleRequest(Unknown Source)
	at com.remedy.arsys.stubs.BackchannelServlet.doRequest(Unknown Source)
	at com.remedy.arsys.stubs.GoatServlet.postInternal(Unknown Source)
	at com.remedy.arsys.stubs.GoatHttpServlet.doGet(Unknown Source)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:743)
Caused by: 
MessageType: 2
MessageNum: 90
MessageText: Cannot establish a network connection to the AR System server
AppendedText: ARS63UK : RPC: Rpcbind failure - RPC: Unable to receive
	at com.remedy.arsys.api.Proxy.ARExpandMenu(Native Method)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
	at com.newatlanta.servletexec.SERequestDispatcher.forwardServlet(SERequestDispatcher.java:638)
	at com.newatlanta.servletexec.SERequestDispatcher.forward(SERequestDispatcher.java:236)
	at com.newatlanta.servletexec.SERequestDispatcher.internalForward(SERequestDispatcher.java:283)
	at com.newatlanta.servletexec.ApplicationInfo.processApplRequest(ApplicationInfo.java:1827)
	at com.newatlanta.servletexec.ServerHostInfo.processApplRequest(ServerHostInfo.java:919)
	at com.newatlanta.servletexec.ServletExec.ProcessRequest(ServletExec.java:1091)
	at com.newatlanta.servletexec.ServletExec.ProcessRequest(ServletExec.java:1002)

---

Remedy's response is that the problem has to do with a firewall but we can also reproduce the error locally (by opening IE from the server machine)

The server machine is running on Windows XP SP2 using ARS 6.3/mid-tier 6.3 (both patch 13). The default Windows firewall is turned OFF all the time

Does anyone else have (or had) this problem??

We also Get that "RPC: Rpcbind failure - RPC:Timed Out" Error Msg when one of our users tries to change her ARS password. She too is behind a firewall. I have not had Any response from Remedy yet.

avillafana@gmail.com

I have the same problem. Could anyone answer, please?

Thanks

Alex

It's not a Mid-Tier problem, it's an IIS one.

Do not run Mid-Tier 6.3 on IIS 6. Theses errors occured very often.

After a Mid-Tier 6.3 installation on W2K and IIS 5, theses errors disapear.

Other than rolling back to a 7-year-old operating system, how can we verify where the problem is coming from? It's easy to say it's the other guys fault, but how can we prove that to ourselves out here in the field? And how can we expect them to change it if we can't trace the errors back to their app?

Have you tried setting the ARTCPPORT system environment variable to the TCP Port that your arserver is set to? That generally resolves the issue you are reporting.

There are multiple KBs on Remedy's site that deal with this:
Here are a few:

These are pretty straightforward:
KM-000000005315
KM-000000012464
KM-000000006019

Also these:
KM-000000006782
KM-000000011607

I hope that helps!

Certainly worth a try. We'll give it a shot and see what happens. This environment variable is set on the machine holding the Remedy application server? or on the mid-tier?

Thanks!
Mike

Well, a Mid-Tier installation can connect to multiple AR Servers... each server definition within the Mid-Tier configuration utitility allows you to set the TCP Port, so that is the level you would do it at.

However, if you are running an independent Java application (or other API) to your AR Server, you may need to use the ARTCPPORT environment variable. In those cases, you would set it on the machine where the API code is running.

Enjoy,