Cannot connect to named analysis service

I am trying to use SQL Server Management Studio to connect to a named analysis service running on a local machine (XP Pro). The studio can see the analysis service because the dialogbox of "Browse for Servers" shows the correct analysis service name, but it just cannot connect to it. I stopped and restarted the service, rebooted the machine, uninstalled and reinstalled the analysis service. Nothing works so far. I can connect the database engine server or reporting service on the same machine without any problem. Could anyone offer any type of hint for me to address this problem?

Thanks in advance!

H

Here are the error message and technical details:

TITLE: Connect to Server

Cannot connect to HP-AMD64\ANALYSIS.

ADDITIONAL INFORMATION:

A connection cannot be made to redirector. Ensure that 'SQL Browser' service is running. (Microsoft.AnalysisServices.AdomdClient)

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

BUTTONS:

OK

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

Cannot connect to HP-AMD64\ANALYSIS.

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

A connection cannot be made to redirector. Ensure that 'SQL Browser' service is running. (Microsoft.AnalysisServices.AdomdClient)

Program Location:

at Microsoft.AnalysisServices.AdomdClient.XmlaClient.GetTcpClient(ConnectionInfo connectionInfo)
at Microsoft.AnalysisServices.AdomdClient.XmlaClient.OpenTcpConnection(ConnectionInfo connectionInfo)
at Microsoft.AnalysisServices.AdomdClient.XmlaClient.Connect(ConnectionInfo connectionInfo, Boolean beginSession)
at Microsoft.AnalysisServices.AdomdClient.XmlaClient.GetInstancePort(ConnectionInfo connectionInfo)
at Microsoft.AnalysisServices.AdomdClient.XmlaClient.GetTcpClient(ConnectionInfo connectionInfo)
at Microsoft.AnalysisServices.AdomdClient.XmlaClient.OpenTcpConnection(ConnectionInfo connectionInfo)
at Microsoft.AnalysisServices.AdomdClient.XmlaClient.Connect(ConnectionInfo connectionInfo, Boolean beginSession)
at Microsoft.AnalysisServices.AdomdClient.AdomdConnection.XmlaClientProvider.Microsoft.AnalysisServices.AdomdClient.AdomdConnection.IXmlaClientProviderEx.ConnectXmla()
at Microsoft.AnalysisServices.AdomdClient.AdomdConnection.ConnectToXMLA(Boolean createSession, Boolean isHTTP)
at Microsoft.AnalysisServices.AdomdClient.AdomdConnection.Open()
at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.ObjectExplorer.ValidateConnection(UIConnectionInfo ci, IServerType server)
at Microsoft.SqlServer.Management.UI.ConnectionDlg.Connector.ConnectionThreadUser()

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

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

Program Location:

at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
at System.Net.Sockets.Socket.Connect(EndPoint remoteEP)
at System.Net.Sockets.TcpClient.Connect(IPEndPoint remoteEP)
at System.Net.Sockets.TcpClient.Connect(IPAddress address, Int32 port)
at Microsoft.AnalysisServices.AdomdClient.XmlaClient.GetTcpClientByAddress(String hostName, Int32 port)
at Microsoft.AnalysisServices.AdomdClient.XmlaClient.GetTcpClient(ConnectionInfo connectionInfo)

Out of frustration, I have just installed another analysis service on my machine, but a default one (i.e. not a named instance). Now I can connect to this instance without any problem.

I am going to uninstall every component of SQL 2005 on my machine and reinstall them again to see if there is any chance for named instances to work.

I have all kinds of connection issues with SQL 2005 that have made the migration from SQL2000 to SQL2005 to be very painful so far. I do not remember I ever had any type of connection issue with SQL2000.

H

|||

I have a variation of hipswich's problem

I am running MsSQL2005 and AS on a server .I have built cubes in server .Have had great difficulty in browsing the cube from any remote machine .

Initial problems were associated with the AS server not being able to authenticate the client .

I then put the server and client into the same domain .

I registered an existing user in the domain , into the server users , as member of the various sql groups (olap and other ) .

I also granted this domain user login to the sqlserver .

The client is now able to connect to the sqlserver and the Analysis server , using "windows authentication" with one catch .(Previously the cliebnt could connect to the sqlserver using username -pwd authentication .

There are no AS databases listed , no cubes shown etc . The client also has no authority to create a new database in the analysis server .

I am just wondering , what are all the prerequisites to get the client to be able to view the analysis service cubes ?

How can one verify that you have correctly setup the windows authentication required for AS , while you are logged into the server and sql manager ?

What is the correct setting for datasource property ?

Sorry for making such a long story .

any comments appreciated

|||

This looks like the same problem as was posted in "SQL2005 AS Named instance - SQL Browser issue?" a couple of months back. Unfortunately in that case the conclusion was that it resulted from a known bug.

Try reading that posting and see if it helps.

Regards,

Richard

(p.s. I have no idea why this post is in different font sizes and in bold, and it won't let me change it!)