How to determine and change the port of an SSAS Instance
- Open Task Manager and get the Process Id (PID) for msmdsrv.exe.
- Open command Prompt type netstat /abo >>c:\output.txt .
- Look for the PID in output file and corresponding TCP IP:Port information for same PID.
- To confirm whether you got right Port number, Open Management Studio and connect to AS using IP Address:Port Number (For example:192.168.1.1:5585)
Another way to get the port number for a SSAS instance is to look at the following file:
%ProgramFiles%\Microsoft SQL Server\90\Shared\ASConfig\msmdredir.ini
This file will have information about all the named instances and the current port each of them is listening on. The file will have entries that are similar to the following:
For additional information you can refer to the following topic on Microsoft TechNet:
SQL Server 2005 Analysis Services (SSAS) Server Properties
How to change Port for SSAS Service (SSAS 2005 & SSAS 2008):
Non-clustered environment (Default Instance or Named Instance)
You can configure a named instance to run under a specified port by changing the Port property for the Analysis Services instance to a specified value by using SQL Server Management Studio (this is an advanced property) or by editing the Port server property (<Port>0</Port>) in Msmdsrv.ini file directly (in the ../OLAP/Config folder). A value of zero (the default value) means that Analysis Services dynamically assigns the port at startup
Note: To ensure that the new port information for the instance is relayed by the SQL Browser services to the client applications that are connecting to this instance ensure that the InstanceVisible property for the instance is set to 1. Otherwise you may experience connectivity issues from your client applications.
Clustered environment (Default Instance or Named Instance)
SSAS will start listening on all Public IP addresses of the cluster group using the default port (2383). Any alternate port configuration is ignored.
- Resolving Common Connectivity Issues in SQL Server 2005 Analysis Services Connectivity Scenarios
- 2429685 Cannot connect to a named instance of a clustered analysis services
- How to: Configure Windows Firewall for Analysis Services Access
- Managing Multiple Instances of Analysis Services
Article ID: 2466860 - Last Review: 11/19/2010 17:54:00 - Revision: 2.0