Configuring SQL Server 2012 Analysis Services Port

You may know how to configure the listening port for SQL Server database engine service, via SQL Server Program Group --> Configuration Tools --> SQL Server Configuration Manager by looking into protocols and choose TCP/IP. The port number can be identified by looking into SQL Server error log or run command line: 'netstat -ano | findstr <ProcessID>'. To use a specific TCP/IP port or use dynamic ports, you can configure these instances to use a specific port, see Configure a Server to Listen on a Specific TCP Port (SQL Server Configuration Manager).

By default the firewall helps to prevent unauthorized access to server services, when you are using Windows Firewall then certain settings need to setup for incoming & outgoing options (also similar for third party Firewall tools). 

Similarly SQL Server Analysis Services also requires such a level of authorization (security) and by default it uses the port number 2383 for default instances and dynamically assigned port if its a named instance. BOL defines the method to follow:

Port settings are specified in the msmdsrv.ini file and in the General properties page of an Analysis Services instance in SQL Server Management Studio. If Port is set to a positive integer, the service is listening on a fixed port. If Port is set to 0, the service is listening on port 2383 if it is the default instance or on a dynamically assigned port if it is a named instance.

Dynamic port assignments are only used by named instances. The MSOLAP$InstanceName service determines which port to use when it starts up. You can determine the actual port number in use by a named instance by doing the following:

• Start Task Manager and then click Services to get the PID of the MSOLAP$InstanceName.
• Run netstat -ao -p TCP from the command line to view the TCP port information for that PID.
• Verify the port by using SQL Server Management Studio and connect to an Analysis Services server in this format: <IPAddress>:<portnumber>.

Although an application might be listening on a specific port, connections will not succeed if a firewall is blocking access. In order for connections to reach a named Analysis Services instance, you must unblock access to either msmdsrv.exe or the fixed port on which it is listening in the firewall. The remaining sections in this topic provide instructions for doing so.

This page to configure windows firewall for Analysis Services access says it all!

Say if you have installed SSAS on a Cluster then it is ideal to  change the default port for SSAS. Since SQL Server 2012 it is possible to change the default port by choosing Service Properties or editing msmdsrv.ini file that can be located in BIN folder under \%Program Files\. During the setup process of SSAS the default security settings to control communication stream is saved in msmdsrv.ini file and it is essential to change the 'default 'properties to ensure security settings are controlled. Also see thisKBA2466860  to determine and change port of SSAS instance.