Ben,

An error 90 means that it cannot find the server.  Most commonly, either the 
machine cannot be found or the AR Server cannot be found or the AR Server is 
not running and not responding.

In your case, the server is clearly present and responding as you can access it.

So, is there a possibility it cannot be found?  This can be because of not 
specifying the TCP port if you have a specified TCP port and portmapper 
disabled.  Or you specify a tcp port that is the wrong one.

Or, could the machine not be being found.  This could be a DNS issue?   Maybe 
the machine name you are using cannot be found?  Is there a possibility of a 
local hosts file that changed and is overriding a global DNS?  From the same 
session you are running driver/meta-update from, can you ping the server name 
using the same name you are using from those programs?

90 is a connectivity problem.  You cannot find/reach the server.  Clearly the 
server is present and responding as access via other mechanisms is working.  
The key in this case is why you are not able to access it from the path you are 
trying.

Hopefully, this offers some possibilities,

Doug Mueller

From: ARSList [mailto:[email protected]] On Behalf Of Ben Chernys
Sent: Thursday, January 31, 2019 2:57 AM
To: 'ARSList' <[email protected]>
Subject: weird problem ARERR 90; need suggestions

Hi Folks,
Up until yesterday, I was able to connect with my Remedy server through the API 
(driver & Meta-Update) – running on the actual server.  Now, I am getting an 
ARERR 90 – RPC Success.
I am still able to connect to the Remedy server through the mid-tier (any 
client machine; mid-tier on a different server) as well as the Pentaho client 
(running on the actual server).
Yesterday, the server was patched to patch 5 and restarted.
I have tried to come in as various client types such as mid-tier and UDM 
Adapter.  I have also tried various RPC ports.  What is odd is that prior to 
applying the patch and restarting there were no issues at all.  The server 
itself was not touched and the firewall as was disabled.
Server version:                  9.1.05.005 201812170836
OS:                                         Windows Server 2012 R2 6.3
DB:                                         MS SQL Server 2014 (SP3) 
(KB4022619) 12.0.6024.0
Cheers,
Ben Chernys
www.softwaretoolhouse.com<http://www.softwaretoolhouse.com>
-- 
ARSList mailing list
[email protected]
https://mailman.rrr.se/cgi/listinfo/arslist

Reply via email to