Hi Doug,
Thanks for responding. That’s what I thought too, but there is something strange in the “new” ARERR 90 I’m afraid. I tried this on my laptop with no access to the server mentioned and got a proper 90: 093701.357 E ARGetServerInfo returned an error 2. Status messages: 1 093701.357 E ARGetServerInfo ==> 2, 90, Cannot open catalog; Message number = 90 cent-91 : RPC: Rpcbind failure - RPC: Timed out Here’s what I got on the actual server box: (one with a specified RPC port and the other not. Both with the correct TCP port. 102931.002 q Server Type: Remedy ARS 102931.002 q Server: ( 9) localhost 102931.002 q User: ( 8) ex004395 102931.002 q Port: 46262 102931.002 q RPC: 390600 102931.016 E ARGetServerInfo returned an error 2. Status messages: 1 102931.017 E ARGetServerInfo ==> 2, 90, Cannot establish a network connection to the AR System server localhost : RPC: Success 103108.327 q Server Type: Remedy ARS 103108.343 q Server: ( 9) localhost 103108.343 q User: ( 8) ex004395 103108.343 q Port: 46262 103108.408 E ARGetServerInfo returned an error 2. Status messages: 1 103108.409 E ARGetServerInfo ==> 2, 90, Cannot establish a network connection to the AR System server localhost : RPC: Success Note the “RPC Success” message vs. the Rpcbind failed message. I’ve tried every combination of server name including localhost and its IP address. This was working prior to patch 5 being applied. I added Client Type to RPC Restriction mapping: Unidentified Client (0) to 390600 – which is the Admin RCP Port but I note we have only one admin thread. Image attached Should I set that at the Admin thread or should I set that at another thread? Meta-Update insists that the ARS User have admin rights though the other utilities do not. However some of their calls will fail if the user is not an admin (such as an SQL read). Presumably being an admin is unrelated to the admin thread and I should change that RCP to one of the multi-threaded fast RPC numbers. I also tried various ClientTypes: driver and mid-tier. But that also was to no avail. Driver also fails with the same error. BTW. That addition of Unidentified client was not set into the ar.cfg file. We have centralized config in a two member server group. I am “physically” on the admin server and connecting through localhost generally. Cheers, Ben From: ARSList <arslist-boun...@arslist.org> On Behalf Of Mueller, Doug Sent: January-31-19 6:35 PM To: ARSList <arslist@arslist.org> Subject: RE: weird problem ARERR 90; need suggestions 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:arslist-boun...@arslist.org] On Behalf Of Ben Chernys Sent: Thursday, January 31, 2019 2:57 AM To: 'ARSList' <arslist@arslist.org <mailto:arslist@arslist.org> > 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 ARSList@arslist.org https://mailman.rrr.se/cgi/listinfo/arslist
