2008 RTM, SSAS: named Analysis Services instance port doesn't adjust to the configured port after a failover - by Brandon.Tucker

Status : 

  By Design<br /><br />
		The product team believes this item works according to its intended design.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 377639 Comments
Status Closed Workarounds
Type Bug Repros 0
Opened 10/24/2008 4:03:29 PM
Access Restriction Public


During a failover of a named instance of Analysis Services, SSAS begins listening on the default port rather than the one specified in the configuration file.

-SQL Browser is running
-Inbound TCP 2382 firewall rule for SQL Browser enabled
-Inbound TCP <named instance port> firewall rule for SSAS enabled
-<Port> element in OLAP\Config\msmdsrv.ini specifies <named instance port> before and after the failover
Sign in to post a comment.
Posted by MarcosLeRosa on 9/9/2011 at 11:02 AM
In a Production environment there is no way to each time a failover occurs we open a Change ticket to change the configuration to the .ini file. So there is no work around to it, which makes me ask why for this such restricted configuration? I will have to redo 5 clusters on my prod environment due to this and customer do need to connect using different ports.
Posted by Brandon.Tucker on 11/19/2008 at 11:45 AM
I don't understand the reasoning behind this. In our environment, all facets of the SQL Server product (Engine, SSAS, etc.) are moved to a non-default port. Why would a clustering environment make a difference? Will this change down the road? Is the best solution to restart the AS instance after a failover to catch the non-default port?
Posted by Microsoft on 11/19/2008 at 11:21 AM

The current behavior of clustered Analysis Services that it would always listen to the default port, regardless of the specified port number.

The Analysis Services Team.