Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Clustered SSAS unable to connect to named instance (instance not found on server) Expand / Collapse
Author
Message
Posted Thursday, March 20, 2014 6:53 PM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Wednesday, August 27, 2014 6:58 PM
Points: 48, Visits: 55
Hi All,

I have a 3 node cluster on which I have installed SSAS as it's own insntance. I have created this as a named instance and can connect to it by server\instance if I'm on the server itself. However from my desktop I get the error saying instance was not found on server name.

I have defined an alternate port and setup firewall rules and can connect via server:port but not server\instance. Prior to making this change SSAS was running on default port of 2383 and I could connect just by servername.

I have read many articles for previous versions saying that clustered SSAS will always use 2383 and that you must connect just using servername. However and this is were it gets strange. I have a 2 node UAT cluster with SSAS setup exactly the same way I've described above and I can connect from my desktop as server\instance.

Should I be able to connect as server\instances for a named clustered instance in 2012 ? If not I'll put UAT down to being an oddity if so can you tell me what I may be missing.

Many Thanks

Corinne
Post #1553290
Posted Thursday, March 20, 2014 10:52 PM
Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Friday, August 29, 2014 1:14 PM
Points: 1,194, Visits: 2,217
corinne_crawford (3/20/2014)
Hi All,

I have a 3 node cluster on which I have installed SSAS as it's own insntance. I have created this as a named instance and can connect to it by server\instance if I'm on the server itself. However from my desktop I get the error saying instance was not found on server name.

I have defined an alternate port and setup firewall rules and can connect via server:port but not server\instance. Prior to making this change SSAS was running on default port of 2383 and I could connect just by servername.

I have read many articles for previous versions saying that clustered SSAS will always use 2383 and that you must connect just using servername. However and this is were it gets strange. I have a 2 node UAT cluster with SSAS setup exactly the same way I've described above and I can connect from my desktop as server\instance.

Should I be able to connect as server\instances for a named clustered instance in 2012 ? If not I'll put UAT down to being an oddity if so can you tell me what I may be missing.

Many Thanks

Corinne


If the SSAS instance was started through Cluster Administrator, all clustered SSAS instances whether default or named instances always listen on the default port 2383. Whereas if the SSAS instance was not started through Cluster Administrator , then it behaves as a stand alone instance and will use dynamic port allocation through SQL Browser service.

The only supported way to connect to a clustered SSAS instance ( Default or Named instance) is to use VirtualServerName and not VirtualServerName\InstanceName. And all clustered instances always listens on the default port 2383. This is because SQL Browser service is not cluster aware and can't be used for dynamic port allocation of SSAS Named instance.

So on UAT server check if the SSAS service was started outside cluster administrator and hence has a peculiar behavior. So rule out things, start the UAT instance within the cluster administrator and observer the behavior.

The key here is not to start SSAS Named instance outside the cluster administrator. If done so then it will behave as a Non-Clustered Named Instance.

Note:
VirtualServerName\InstanceName may work sometimes but it's not gauranteed always and also not supported by MS.

--
SQLBuddy
Post #1553311
Posted Monday, March 24, 2014 9:22 PM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Wednesday, August 27, 2014 6:58 PM
Points: 48, Visits: 55
Many Thanks for the clarification
Post #1554269
Posted Tuesday, March 25, 2014 8:12 AM
Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Friday, August 29, 2014 1:14 PM
Points: 1,194, Visits: 2,217
You are welcome, Corinne

--
SQLBuddy
Post #1554491
Posted Friday, May 2, 2014 6:09 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Friday, May 2, 2014 6:05 PM
Points: 1, Visits: 0
Hi,

i have similar problem, i have two nodes, i have installed default instance with only SQL services and named instance with only SSAS. i was able to connect to SSAS using SSAS virtual name\instancename, from today morning i was not able to access the SSAS using SSAS virtual name or SSAS virtual name\instancename, but i am able to access it by providing Servername on which SSAS role is running. i restarted SSAS role using Failover cluster manager many times, but i am not able to connect it through SSAS virtual name. i am getting following error message.

TITLE: Connect to Server
------------------------------

Cannot connect to XXXXXXXXX

------------------------------
ADDITIONAL INFORMATION:

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 XXXXXXXXX:2383 (System)

------------------------------
BUTTONS:

OK
------------------------------
Post #1567199
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse