SQL SERVER – FIX – A connection cannot be made to redirector. Ensure that ‘SQL Browser’ service is running. (Microsoft.AnalysisServices.AdomdClient)

Life gives you learning lessons from unexpected times, here is one such experience that I felt is worth sharing. It may be a surprise to my blog readers that I also have SQL Server Analysis Services installed on my primary machine. I use it occasionally because most of the time I work with the SQL Server Database engine. One fine day, I opened SQL Server Management Studio and instead of a database engine, I selected analysis services (this was a mistake) and pressed on the connect button. Below is the error which I received for SQL Browser:

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)

This is the first time I saw such error while connecting to SQL Server, but soon I realized that I was trying to connect to SQL Server Analysis Services. I could have left it there because I don’t use it, but I did not. Since there was a little time, I thought it is worth solving this challenge in front of me. Here is the step by step resolution of what I did:

  1. Made sure that SQL Server Analysis Service was up and running. This got confirmed from my SQL Server Configuration Manager.
  2. As I do always, read the error message again and verified that the SQL Browser service was up and running.
  3. Since this was a local connection, I turned off the firewall as well.

None of the above solved the problem. The Port resolution is done by the SQL browser service in case of SQL Server connectivity. So I thought that it could be a permission issue – just a guess based on the error message.

I noticed that SQL Browser was running with the local system account. I found on the internet that changing account helped many. So I used the SQL Server Configuration Manager to change the service account for the SQL Server Browser. I have used below.

SQL SERVER - FIX - A connection cannot be made to redirector. Ensure that 'SQL Browser' service is running. (Microsoft.AnalysisServices.AdomdClient) browser-ssas-01

Here are the steps:

  • Open SQL Server Configuration Manager
  • Right click “SQL Server Browser” and choose “Properties”
  • In the “Log On” Tab select “Local System” under “Built-In” account.

Have you ever seen such error and found some other way to fix it? Please comment and let others also know. The best way to learn something is by sharing.

Reference: Pinal Dave (https://blog.sqlauthority.com)

, ,
Previous Post
SQL SERVER – How to Add User Across Databases
Next Post
SQL SERVER – Error – Msg 6401, Level 16: Cannot roll back Transaction

Related Posts

52 Comments. Leave new

  • Error 6 The project could not be deployed to the ‘compy-PC\SQLEXPRESS’ server because of the following connectivity problems : A connection cannot be made to redirector. Ensure that ‘SQL Browser’ service is running. To verify or update the name of the target server, right-click on the project in Solution Explorer, select Project Properties, click on the Deployment tab, and then enter the name of the server. 0 0

  • Can you share link for sql server 2005 full edition 64 bit

  • Ignacio Fiesco
    August 15, 2018 7:52 am

    I get this error on our cluster enviroment, so if I connect with ip:port it works, I was looking for logs and I review error that it says a dns:port. We have 4 SSAS instances so I decide to force error SSAS port, to number displayed on error screen, so It works!! I get connection with dnsname\instancename as well

  • Thanks! It was really helpful!

  • Got the same error message but none of the solutions in the web lead to solution.
    As I was able to connect via SQL Server Management Studio to the SSAS instance, my only problem was that I wasn’t able to connect in SSDT (for example in the Cube Browser).
    I was using a named instance on my local machine for which I had to edit the Properties in SSD of my project, go to Configuration Properties | Deployment and change “localhost” to “servername\namedinstance”.
    That was my solution.
    Hope that helps other guys.

  • Thank you! It was helpful for me.

  • I have the same error and i have done everything you all said and nothing has changed. Please help :(

  • Dobin Fernandes
    May 22, 2019 11:14 am

    wow, this worked like a charm… should analysis services also be running under ‘local system’ account or ‘network service’ is fine…

  • Does SQL Browser need to be running for SSAS or is there a way to run it without that service enabled? Per the Security Technical Implementation Guide, if not needed turn off SQL browser. If there is no way around it, then I will have to Hide Instance. I have already changed from dynamic to static ports. I had hoped I could do the same for SSAS and SSRS, but I don’t believe I can and still leave the browser off. Thoughts?

  • Jack Whittaker
    April 24, 2020 7:50 pm

    I’ve tried with Browser On and with it off – neither works
    I’ve tried it with Local system and local service – neither works
    Any other suggestions Pinal-ji?

  • I am able to connect to server after providing entire name in CAPITAL Letters, my dba suggested it could be because of COLLATION property used while installation of server.

  • Ashwani Rawat
    March 6, 2021 4:21 pm

    Getting the same error while connecting to the Analysis Service from SSMS. I am using SQL server express edition 2019. Although I have installed SSAS, SSIS and SSRS from the Manage Extensions in the Visual Studio.

    I don’t see the SSAS, SSIS or SSRS services appearing in the Configuration manager but these options are coming in the SSMS in the Object Explorer. I have tried opening the ports, changed the log on for SQL server browser to all the three options.


Leave a Reply