Unable to Connect to Analysis Services - SQL Server Security - LearnSqlServer.com's SQL Server Forums

Member of the LearnItFirst.com Video Training Network	\| LearnSqlServer.com \| SQL SSIS Training \| SQL Programming Tutorials \|

Welcome Guest

Search | New Posts | Members | Log In | Register

LearnSqlServer.com's SQL Server Forums » SQL Server Database Administration » SQL Server Security » Unable to Connect to Analysis Services

Unable to Connect to Analysis Services

Options

Previous Topic · Next Topic

PaulGr

Posted: Thursday, May 15, 2008 11:36:00 AM

Rank: Newbie

Joined: 1/11/2008
Posts: 3
Points: 9
Location: Yorkshire, England

I am unable to connect to analysis services because I can't configure remote connections in the sql server surface are configuration manager

The SQL Browser is running and according to a port scan I ran Analysis services is listening on port 2656. I also tried connecting to 2656 in the SSMS but that didn't work either.

I am logged in with an administrator account so it is not that. I can also connect to the database engine, SSIS, and reporting services fine.
I get the following message. Any help would be greatly appreciated. Thanks Paul.

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

To configure Analysis Service remote connections, you must be an administrator for the Analysis Services Windows service. (SQLSAC)

Program Location:

at Microsoft.SqlSac.MainPanel.UserControlASProtocols.ProcessOK(HashKey givenKey, String machineName)
at Microsoft.SqlSac.MainPanel.FormServicesAndProtocols.CommitChanges(String ServerName)

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

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

Program Location:

at Microsoft.AnalysisServices.XmlaClient.GetTcpClient(ConnectionInfo connectionInfo)
at Microsoft.AnalysisServices.XmlaClient.OpenTcpConnection(ConnectionInfo connectionInfo)
at Microsoft.AnalysisServices.XmlaClient.Connect(ConnectionInfo connectionInfo, Boolean beginSession)
at Microsoft.AnalysisServices.XmlaClient.GetInstancePort(ConnectionInfo connectionInfo)
at Microsoft.AnalysisServices.XmlaClient.GetTcpClient(ConnectionInfo connectionInfo)
at Microsoft.AnalysisServices.XmlaClient.OpenTcpConnection(ConnectionInfo connectionInfo)
at Microsoft.AnalysisServices.XmlaClient.Connect(ConnectionInfo connectionInfo, Boolean beginSession)
at Microsoft.AnalysisServices.Server.Connect(String connectionString, String sessionId)
at Microsoft.AnalysisServices.Server.Connect(String connectionString)
at Microsoft.SqlSac.Public.Amo.ConnectToServer(Credentials credentials)
at Microsoft.SqlSac.Public.Amo.SetSetting(Credentials credentials, AnalysisFeature analysisFeature, String value)
at Microsoft.SqlSac.MainPanel.UserControlASProtocols.ProcessOK(HashKey givenKey, String machineName)

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

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

Program Location:

at System.Net.Sockets.TcpClient..ctor(String hostname, Int32 port)
at Microsoft.AnalysisServices.XmlaClient.GetTcpClientByAddress(String hostName, Int32 port)
at Microsoft.AnalysisServices.XmlaClient.GetTcpClient(ConnectionInfo connectionInfo)

Scott Whigham

Posted: Saturday, May 17, 2008 10:39:43 AM

Rank: Super Mod

Joined: 3/20/2006
Posts: 329
Points: 700
Location: Dallas, TX

Hi Paul -

I'm a know-nothing about SSAS but I'll suggest a few things: one - the Surface Area Configuration Manager for SQL Server's remote connections will not have an effect on SSAS; that's just for the SQL Server service. If there's a setting in the SAC for SSAS I don't know.

Next, you mention remote connections but it appears from the error that you can't log in locally - is that correct? I get that from the error for 127.0.0.1:2382

Heck, I don't know why I'm even asking - I only know the absolute basics about SSAS Frown

PaulGr

Posted: Tuesday, May 20, 2008 3:52:50 AM

Rank: Newbie

Joined: 1/11/2008
Posts: 3
Points: 9
Location: Yorkshire, England

Hi

After much trial and error I finally got this to work. Unfortunately, I'm not exactly sure why. I simply changed the SQL browser to run under the local system account. I think I'll have to watch Scott's videeos on service accounts again.

Basically everything was running under the localsystem account apart from the browser and integration services which were running under the NTAUTHORITY\Network Service account. I had no trouble connecting to Integration Services.

The instance of sqlserver is running on my laptop so I'm not sure which accounts I should use if running on Windows Server.

Paul

Users browsing this topic

Guest

Forum Jump

You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.