Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
bpollitt
Starting Member
4 Posts |
 Posted - 2006-06-08 : 11:55:41
|
| I am trying to configure a non-default port on a clustered instance of (Analysis Services (AS) 2005 running on a Windows 2000 box. The AS port property was changed to the correct port and the config (.ini) file was also changed, but the port still does not open.Recently, I came across this blog ->> http://dbaiq.blogspot.com/2006/02/clustered-analysis-services-port.html, which suggests there is a problem with changing the default port from 2383 to another port. Has anyone heard of this problem? and Could anyone point me to some reputable references, test cases, or workarounds for the issue? Ben |
|
|
bpollitt
Starting Member
4 Posts |
Posted - 2006-06-08 : 11:58:39
|
| Here's the detail of the referenced link on blogger.com in orig post:"Clustered Analysis Services port settingsOne of my favorite updates to Analysis Services in SQL 2005 is the native clustering support. The installer works well, it sets up on a cluster in the same manner as SQL Server, and it fails over easily (although we have yet to test its availability through a variety of failure scenarios). However, we've uncovered a minor but irritating flaw in the clustering implementation.If you have multiple network segments separated by firewalls, as we do, you probably have difficulty connecting to named instances on a cluster. This happens because of the dynamic port setting process, to be detailed in an upcoming post, but also documented in various places on the web. The quick workaround is to set static TCP/IP ports for the named instances (in the Server Network Utility) and define aliases on every client connecting to them (in the Client Network Utility, or with a registry script). We've done this with a number of named instances on clusters, and it's fine, if a little clunky because of the individual setup on each client. We have a limited range of ports defined for this purpose and opened on the firewall.I set up our first clustered instance of Analysis Services 2005 a few days ago and immediately ran into this problem again. After talking with Microsoft product support, I edited the msmdsrv.ini file in the \Microsoft SQL Server\MSSQL.1\OLAP\Config directory, changing the tag from the default 0 to our desired port. Restarted Analysis Services and... still couldn't connect.So I fired up Ethereal and checked out some packets while connecting from machines inside and outside the firewall. From outside, I got nothing. From inside, all the traffic was on 2382 and 2383. I got back on with Microsoft, and after exhausting all the simple options, a tech there reconstructed my problem in his lab. He got back to me with the disappointing answer the next day.Clustered Analysis Services is hard-coded to use port 2383.You can change the port setting in the .ini file or the Properties tab, but it won't do anything. I'm hoping they support changing the port in an upcoming SP, but for now I get to go persuade my security team to open another port on the firewall..."Ben |
 |
|
|
|
|
|
|
|
Analysis Services Default port bug?