Cannot connect to a named instance of a clustered analysis service
This article helps you resolve the problem where you might not be able to connect to a named instance of Analysis Services that is installed on a failover cluster.
Original product version: SQL Server 2008 R2 Enterprise, SQL Server 2008 Enterprise, Microsoft SQL Server 2005 Enterprise Edition
Original KB number: 2429685
You might not able to connect to a named instance of Analysis Services that is installed on a failover cluster. You may receive an error message that is similar to the following:
Cannot connect to <server name>
A connection cannot be made. Ensure that the server is running. (Microsoft.AnalysisServices.AdomdClient)
No connection could be made because the target machine actively refused it <ip address>:2383 (System)
The problem occurs when you start the named instance of SQL Server Analysis services (SSAS) using either SQL Server Configuration Manager or the Services applet in the Control panel. When you start an SSAS instance on a failover cluster using a tool other than Failover Cluster Management (Cluster administrator on older Operating Systems), that SSAS instance will run as a stand-alone instance and will listen on a non-default port resulting in connection failures from various applications.
Stop and restart the SQL Server Analysis services using the Failover Cluster Management tool.
An SSAS instance started on a cluster (default or named instance) will start listening on all IP addresses of the cluster group using the default port of 2383. The server setting
<Port> property does not change the port number of SSAS service on a cluster.
For more information, see the KB article: How to determine and change the port of an SSAS Instance