Are you using the portmapper? If not check the port you are trying to connect through.
Joe From: Kemes, Lisa Sent: Thursday, March 08, 2012 8:57 AM Newsgroups: public.remedy.arsystem.general To: arslist@ARSLIST.ORG Subject: Re: Client getting RPC Error (90) When Logging into DR Server ** Thanks so much everyone. I was able to comment out the DSO on armonitor.cfg file. I also added this “C:\Program Files\Common Files\AR System\Licenses\USW04AP004\arsystem.tag” to get rid of that arsystem.tag error. Started the services and now I'm not getting any errors in the arerror.log file but I'm still getting the RPC (90) error when trying to login with the client. I compared the ar.cfg files and there are a lot more lines in the prod ar.cfg file. I'll add these to the DR ar.cfg file and see what happens. I'll also install the client on the server and see what happens with that. Thanks! Lisa -------------------------------------------------------------------------------- From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of patchsk Sent: Wednesday, March 07, 2012 5:46 PM To: arslist@ARSLIST.ORG Subject: Re: Client getting RPC Error (90) When Logging into DR Server ** There could be more than just the DSO is failing. Since you mentioned the production is working and dr is using the same database, please compare both ar.conf and armonitor.conf b/n prod and dr and you may find something there. Make sure they are very similar as much as possible.(Same kind of ports,threads,timeouts, logging options etc...) during the troubleshooting. That would eliminate lot of unknowns. Also you are on a windows server so try installing user tool on the server itself and try login from there. Turn on API, SQL, User logs at server level and see if your login attempts are displayed in the logs. If they are it will atleast confirm that atleast server is receiving packets from client. You could also use the driver program that is installed along with arserver to initiate api calls for troubleshooting. On Wednesday, March 7, 2012 3:53:37 PM UTC-6, Kemes, Lisa wrote: ** I installed AR System Server on a server that we are using as a DR Server. It is pointing to the same DB server as our Prod Server (luckily this prod server is actually not in production yet). Prod App Server Services are turned on and everything is working. When I tried to turn on the AR Services on the DR server, I'm getting this in our arerror.log file. The first 4 lines are to be expected because the DR server has not been licensed yet. The next 2 lines I've heard that we can just ignore, but the lines about the Distributed Server Option is what I'm thinking is causing me problems. I'm trying to log into the DR Server with my Client (to get the host ID to get a license key for it) and I keep getting the RPC Error (90). So I stopped the services on our Prod Server and restarted the services on our DR Server and I'm still getting the RPC Error and these errors are still appearing on the arerror.log file. I know the APP server is talking to the DB Server or those types of errors would come up in the arerror.log file. Plus I was able to successfully install the AR System sofware on the DR server..... Is there anything else I can check? Yes, the network is working and my client is working and the ports are open and I can ping the DR server from my PC. Prod server is working just fine.... AR System 7.6.04 SP2 Oracle 11g Windows 2008 Server Windows 7 PC ----------------------------------------------------------------------------------------------------------- Wed Mar 07 14:32:45 2012 : Action Request System(R) Server x64 Version 7.6.04 SP2 201110080614 (c) Copyright 1991-2011 BMC Software, Inc. Wed Mar 07 14:32:46 2012 390600 : This COPY of the Action Request System(R) does not have authorization key set, but is ready for use or evaluation. For unlimited capabilities, contact your sales representative. (ARNOTE 27) Wed Mar 07 14:39:31 2012 390600 : Could not find or read the optional license tags file. (ARNOTE 452) Wed Mar 07 14:39:31 2012 C:\Program Files\Common Files\AR System\Licenses\USW04AP004\arsystem.tag Wed Mar 07 14:43:31 2012 Distrib : This AR System is not licensed for the Distributed Server Option (ARDSERR 3100) Wed Mar 07 14:43:31 2012 Distrib : AR System Distributed Server terminated -- fatal error encountered (ARDSERR 3001) Wed Mar 07 14:43:33 2012 Distrib : This AR System is not licensed for the Distributed Server Option (ARDSERR 3100) Wed Mar 07 14:43:33 2012 Distrib : AR System Distributed Server terminated -- fatal error encountered (ARDSERR 3001) Wed Mar 07 14:43:34 2012 Distrib : This AR System is not licensed for the Distributed Server Option (ARDSERR 3100) Wed Mar 07 14:43:34 2012 Distrib : AR System Distributed Server terminated -- fatal error encountered (ARDSERR 3001) Wed Mar 07 14:43:34 2012 Distrib : This AR System is not licensed for the Distributed Server Option (ARDSERR 3100) Wed Mar 07 14:43:34 2012 Distrib : AR System Distributed Server terminated -- fatal error encountered (ARDSERR 3001) Wed Mar 07 14:43:34 2012 Distrib : This AR System is not licensed for the Distributed Server Option (ARDSERR 3100) Wed Mar 07 14:43:34 2012 Distrib : AR System Distributed Server terminated -- fatal error encountered (ARDSERR 3001) Lisa Kemes AR System Developer TEIS - USA +1 717 810 2408 tel +1 717 602 9460 mobile lisa.ke...@te.com 100 Amp Drive Harrisburg, PA 17112 www.te.com _attend WWRUG12 www.wwrug.com ARSlist: "Where the Answers Are"_ _attend WWRUG12 www.wwrug.com ARSlist: "Where the Answers Are"_ _attend WWRUG12 www.wwrug.com ARSlist: "Where the Answers Are"_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
