Hi Folks!

I have been trying to deploy my AdventureWorksDW solution
in Analysis Services 2005 and it fails consistently with
a connection message.

Futhermore, I noticed that the Analysis Services stops
itself each time I start it.

Could someone please give me some guidance? Here is the
error message I am getting:

-----------------------------------------------

TITLE: Connect to Analysis Server
----------------------------------------

Cannot connect to gateway\kdkeys.

----------------------------------------
ADDITIONAL INFORMATION:

A connection cannot be made. Ensure that the server is
running.
(Microsoft.AnalysisServices.AdomdClient)

----------------------------------------

No connection could be made because the target machine
actively
refused it (System)

----------------------------------------
BUTTONS:

OK
----------------------------------------

=============================================

Cannot connect to gateway\kdkeys.

=============================================

A connection cannot be made. Ensure that the server is
running.
(Microsoft.AnalysisServices.AdomdClient)

----------------------------------------
Program Location:

at
Microsoft.AnalysisServices.AdomdClient.XmlaClient.GetTcpCl
ient(ConnectionInfo
connectionInfo)
at
Microsoft.AnalysisServices.AdomdClient.XmlaClient.OpenTcpC
onnection(ConnectionInfo
connectionInfo)
at
Microsoft.AnalysisServices.AdomdClient.XmlaClient.Connect
(ConnectionInfo
connectionInfo, Boolean beginSession)
at
Microsoft.AnalysisServices.AdomdClient.XmlaClientProvider.
Microsoft.AnalysisServices.AdomdClient.AdomdConnection.IXm
laClientProviderEx.ConnectXmla()
at
Microsoft.AnalysisServices.AdomdClient.AdomdConnection.Con
nectToXMLA(Boolean
createSession, Boolean isHTTP)
at
Microsoft.AnalysisServices.AdomdClient.AdomdConnection.Ope
n()
at
Microsoft.SqlServer.Management.UI.ConnectionDlg.Connector.
ConnectorThread()

=============================================

No connection could be made because the target machine
actively
refused it (System)

----------------------------------------
Program Location:

at System.Net.Sockets.TcpClient.Connect(String
hostname, Int32 port)
at
Microsoft.AnalysisServices.AdomdClient.XmlaClient.GetTcpCl
ient(ConnectionInfo
connectionInfo)

-----------------------------------------------

Thanks for your help,

Kingsley Tagbo

---

Sign-up For Data Mining Source Code Newsletter

Raman Iyer [MS - SQL Server Data Mining] wrote:

It's possible that your Analysis Server crashed due to some reason in the past and it didn't release the TCP port (this is a known issue). This would prevent you from restarting the service and would explain the connection error you're seeing. Your current workaround would be to reboot the machine, unfortunately. Another thing to check would be the value of ConfigurationSettings\Port in the msmdsrv.ini file under the Bin folder of your Analysis Services install directory (typically, \Program Files\Microsoft SQL Server\MSSQL.x\OLAP\bin). Did you edit this configuration file and change the port number, by any chance? That could cause a clash with the port number that the default instance of AS listens on, leading to a server startup failure. Please check your event log for additional information about the startup failure as well. -- Raman Iyer SQL Server Data Mining

---

Sign-up For Data Mining Source Code Newsletter

I re-installed SQL Server Analysis Services with the Beta 2 CD.

In the first installation, I had installed both the SQL Server and Analysis Services as a named instance, but, in the re-installation, I installed both as Default Instances under a new Windows XP2 Admin Account (not recommended) and it worked.

Additionally, I had to export the AdventureWorksDW dataabse in the named instance to the new default instance.

---

Sign-up For Data Mining Source Code Newsletter