This happens a lot when installing in a server grouped environment. The armonitor.cfg has to have the AR server name, not the server group name, in the command lines that make up the armonitor.cfg. Sometimes the server-grouped name gets set in the armonitor.cfg file instead of the AR servers. You have to have the actual name of your AR server in the armonitor file. Here's an example Server grouped name: Remedy01 AR Server 1: Remedy-AR1 AR Server2:Remedy-AR2
You will see command line in the armonitor file like this: "C:\Program Files\Java\jre6\bin\java" -Xmx512m -classpath "d:\Program Files\BMC Software\AtriumCore\cmdb\plugins\ne;d:\Program Files\BMC Software\AtriumCore\cmdb\plugins;d:\Program Files\BMC Software\AtriumCore\cmdb\sdk\bin\arpluginsvr7604_build002.jar;d:\Program Files\BMC Software\AtriumCore\cmdb\sdk\bin\arapi7604_build002.jar;d:\Program Files\BMC Software\AtriumCore\cmdb\sdk\bin\arutil7604_build002.jar;d:\Program Files\BMC Software\AtriumCore\cmdb\sdk\bin\log4j-1.2.14.jar;d:\Program Files\BMC Software\AtriumCore\cmdb\sdk\bin\cmdbapi7604.jar;" com.bmc.arsys.pluginsvr.ARPluginServerMain -x Remedy01 -i "D:\Program Files\BMC Software\ARSystem" When you installed ARsystem or Atrium, if you were already server grouped, the installer plugged in the Server group alias, not the AR server name. Change all references to the Server group alias to the actual server that this armonitor file is sitting one. You will have to do this for all your servers in the group. Here is another thing that happens, You will have to search your BMC Software\* directory and find all the instances for pluginsvr_config.xml. Usually in the Atrium directory the installer also likes to put in the server group alias there too. If there are any references to the Server Group name, Remedy01, change them to the AR Server name ( Remedy-AR1). Do this for all your servers. Last but not least, make sure that the installer did not plug in the Server group alias into the Plug-in aliases in your ar.cfg file. It will sometimes do this as well. Make sure you have the actual AR server name. After you have fixed the references and restarted AR system, run the following command in dos: "netstat -afo". This will tell you if your plugin ports are actually in use. You will see something like RemedyAR1:9556 in the list. Check all the ports that are defined in the ar.cfg file and see if they are referenced in the results of the netstat command. In summary, the installer will change the AR server name in the ar.cfg, armonitor.cfg, and the pluginsvr_config.xml. If you clean those up, your plug-ins should work. Jesus Ortega Senior II, Implementation Engineer LyondellBasell Industries Office: 713 309-4914 Cell: 281 546-0735 From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Ramy S. Ayoub Sent: Friday, March 15, 2013 5:00 AM To: [email protected]<mailto:[email protected]> Subject: Cannot establish a network connection to the AR System Plug-In server : remedy01 (9999) REMEDY.ARDBC.APPQUERY : RPC: Miscellaneous tli error - System error (Connection refused) (ARERR 8760) ** Dears, I have issue when login to the web , Im using load blancer and server group , conf Cannot establish a network connection to the AR System Plug-In server : remedy01 (9999) REMEDY.ARDBC.APPQUERY : RPC: Miscellaneous tli error - System error (Connection refused) (ARERR 8760) any idea _ARSlist: "Where the Answers Are" and have been for 20 years_ Information contained in this email is subject to the disclaimer found by clicking on the following link: http://www.lyondellbasell.com/Footer/Disclaimer/ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
