Home > Uncategorized > SQL 2012 Analysis Services Error: "No connection could be made because the target machine actively refused it"

SQL 2012 Analysis Services Error: "No connection could be made because the target machine actively refused it"

In Microsoft SQL Server 2012, you receive an error that resembles the following when you try to connect to a named instance of SQL Server Analysis Services (SSAS) :

No connection could be made because the target machine actively refused it: Port number

 

This issue can occur if the server that hosts the named instance of SSAS was configured to use IPv4 and IPv6 when SQL Server 2012 was installed. Then, the server was later reconfigured to use only IPv6.

 

To resolve this issue, follow these steps:

  1. Stop the SQL Server Analysis Services service.
  2. Open the Msmdredir.ini file in Notepad.
    Note By default, the Msmdredir.ini file is located in the following folder:

    %ProgramFiles%\Microsoft SQL Server\90\Shared\ASConfig

  3. In the Instances section, verify that the values for the Port property and the IPv6 property are different for the named instance.
  4. Delete the PortIPV6 property.
  5. Save the Msmdredir.ini file, and then exit Notepad.
  6. Start the SQL Server Analysis Services service.

 

Source KB

Advertisements
  1. October 15, 2015 at 2:46 pm

    For me id didn’t find this File (Msmdredir.ini) or this Folder (ASConfig) under this path (C:\Program Files\Microsoft SQL Server\120\Shared)

  2. Rajakrishnan
    October 19, 2016 at 5:19 pm

    It’s resolved my issue. Thanks for your post.

  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: