Hi, I fixed this issue with: 1. Uninstalling/Remove the EMC M&R Health SolutionPack 2. I Configured "Load balancer Connector" in the Collector hosts pointing to "Load Balancer  Arbiter" in Primary Backend Host 3. Install EMC M&R Health SolutionPack  Cause: Installing EMC M&R Health SolutionPack before to configure Load Balancer Conector/Arbiter [IMAGE]
Hi, I do a Windows binary deployment of VIPR SRM 3.6 SP2 that include 1 FrontEnd, 1 Backend, 1 Colector. Only EMC M&R Health SolutionPack was deployed on each host, everything is working OK.  The issue appear in the collecting log file on module Collector-Manager::Load-Balancer on server 'Colector 1' Load Balancer Connector in Colector 1 is pointing to Load Balance Arbiter on Backend. No restrictions on the Firewall, all ports are open.  Each minute this Warning message appear:  WARNING  -- [2015-04-10 09:40:36 PDT] -- BalancerConnector::isArbiterReachable(): Arbiter Balancing Service connection is unavailable (com.sun.xml.internal.ws.fault.ServerSOAPFaultException: Client received SOAP Fault from server: Cannot find dispatch method for { [URL]}nop Please see the server log to find more detail regarding exact cause of the failure.) !   [IMAGE]  Someone knows what is the cause of this, where is the log file to find more details of the failure?  This is only a warning message, but the collecting log file is full of this messages.  Regards Jose Luis
Arbiter Balancing Service connection is unavailable (Windows Binary Deployment)