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

Topics: Developer Forum, Project Management Forum, User Forum
Jun 19, 2014 at 1:25 AM
Edited Jun 19, 2014 at 1:27 AM
Hope this saves someone else some time.

This was on a clustered instance but assuming it could happen with any named instance.

The assemblies in ASSPP connect to the analysis services instance via Context.CurrentServerID (Microsoft.AnalysisServices.AdomdServer). All of our internal connections have always been made via a CNAME so the issue never came up before migrating to a named instance.

The SQL Browser was trying to direct ASSPP connections to the IPv6 port rather than the IPv4. The resolution was to remove the IPv6 entry from Msmdredir.ini. Microsoft published the fix instructions here: