Cannot connect to named instances of Analysis Services after fresh installation or rename of server

Many a times when a new SQL Server 2008 R2 analysis services instance is installed or a server is renamed then following error is received while trying to connect to named instance of analysis service,



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 ::1:2383 (System)


This is mostly because of browser service account not given appropriate privileges or permissions are not set correctly, in this scenario do following,


1. Go to Start > Computer > right click, select Manage > Server Manager > Configuration > Local Users and Groups > Groups


2. Check for SQL Server Browser Group name, for e.g. (Note down the name)


3. Now navigate to following folder,

    c:\Program Files (x86)\Microsoft SQL Server\90\Shared


4. Inside it there will be ASConfig folder,




5. Right click ASConfig folder > Go to Properties > Go to Security tab


6. Check if same SQL Browser Service group present or not, if present then edit the permissions and give Write permissions and If SQL browser group not present then add it and give write permissions as below,



7. Now go to “SQL Server Configuration Manager” (Start > All Programs > Microsoft SQL Server 2008 R2 > Configuration Tools >     SQL Server Configuration Manager)

8. Store SQL Server Browser Services

9. Stop SQL Server Analysis Services

10. Start SQL Server Browser Services

11. Start SQL Server Analysis Services

12. Try to connect SQL Server Analysis Services using SSMS or Powershell, etc. it should work fine!



Above solution shall work perfectly, in case it doesn’t then follow below links, they have provided few more workarounds for similar kind of issue,

For e.g. Restart Browser Service with –c switch or Connect Analysis services using port number, etc.

Download PDF

About the Author: Nitin G

Indian born, trekker, biker, photographer, lover of monsoons. I've been working full time with SQL Server since year 2005 and blogs to post the content aquired during my research on new topics or fixing issues faced by me as a DBA while working in different kind of projects, hope some of my posts may helps others in SQLDBA community. Everything you read on my blog is my own personal opinion and any code is provided "AS-IS" with no warranties!

3 Comments + Add Comment

  • Above solution is working for me…!!!

  • Hi,
    I renamed my AS instance to ‘Tabular’ from what it previously was. Before the rename, the connection was successful from the MS SQL Management Studio. Now, after the rename, I get the same error as on the first screenshot of this page. I tried your proposed solution but it still doesn’t work.
    What I can see in the SQL Config Manager is that the Analysis Service is also stopped and tells that the service couldn’t respond in a timely manner when I try to ‘Start’ it.

    What could be the problem now? Can I rename it to what it was earlier? (I tried leaving the name blank since it was the default name before too but it says that a server with the name MSSQLSERVER already exists).

    Any help would be appreciated, thanks.

  • Thank you for your detailed solution. Just wanted to give you props for helping me out. 🙂

Leave a comment

Subscribe to this blog via Email

Enter your email address to subscribe to this blog and receive notifications of new posts by email.

Join 265 other subscribers

Translate this blog!



March 2021
« Nov    

View Post by Categories

%d bloggers like this: