SQL Server Home
2008 RTM, SSAS: named Analysis Services instance port doesn't adjust to the configured port after a failover
as By Design
10/24/2008 4:03:29 PM
User(s) can reproduce this bug
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
SQL Server 2008 - Enterprise Edition
Windows Server 2008
Operating System Language
Steps to Reproduce
-Create a n-node cluster.
-Install a named instance of Analysis Services.
-Change the default port.
-Restart the Analysis Services service on the active node.
-Attempt to connect (should succeed).
-Move Analysis Services to the passive node.
-Attempt to connect (should fail).
The port specified in OLAP\Config\msmdsrv.ini should be the listening port after a failover.
Listening port reverts back to the default port most of the time.
to post a comment.
Please enter a comment.
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.
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?
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.
to post a workaround.
Please enter a workaround.
on 10/24/2008 at 4:04 PM
An apparent workaround seems to be to restart the Analysis Services service on the newly active node after the failover has occurred.
© 2013 Microsoft