Analysis Services Stored Procedure Project

New Post: SSAS 2012 using ASSP : "No connection could be made because the target machine actively refused it."

fpatou — Mon, 29 Apr 2013 15:39:50 GMT

Ok i found the answer...it deals with the msmdredir.ini.

refering this : http://support.microsoft.com/kb/2658571

after removing the IPV6 entry from msmdredir.in int this section it works :
before :

<Instances>
    <Instance>
        <Name>SSAS</Name>
        <Port>2383</Port>
        <PortIPv6>50825</PortIPv6>
    </Instance>
</Instances>

After :

<Instances>
    <Instance>
        <Name>SSAS</Name>
        <Port>2383</Port>
    </Instance>
</Instances>

Thank you for your help.

New Post: SSAS 2012 using ASSP : "No connection could be made because the target machine actively refused it."

fpatou — Mon, 29 Apr 2013 15:39:50 GMT

Ok i found the answer...it deals with the msmdredir.ini.

refering this : http://support.microsoft.com/kb/2658571

after removing the IPV6 entry from msmdredir.in int this section it works :
before :

<Instances>
    <Instance>
        <Name>SSAS</Name>
        <Port>2383</Port>
        <PortIPv6>50825</PortIPv6>
    </Instance>
</Instances>

After :

<Instances>
    <Instance>
        <Name>SSAS</Name>
        <Port>2383</Port>
    </Instance>
</Instances>

Thank you for your help.

New Post: SSAS 2012 using ASSP : "No connection could be made because the target machine actively refused it."

furmangg — Mon, 29 Apr 2013 14:33:41 GMT

I ran into a strange installation of SSAS recently where it was a named instance but the port had been changed to the default port and SQL browser had been stopped. So when one of those sprocs mentioned above ran, AdomdServer.Context.CurrentServerID was saying the instance name was SERVERNAME\SSAS and since SQL Browser wasn't running, it failed.

I know you said SQL Browser was running. But the point is that you may be connecting to the instance with a different server and instance name than SSAS internally thinks it is... then the sprocs will try to connect to SSAS under the server and instance name it knows.

If you connect Object Explorer in Management Studio to SSAS, then right click on the server node and choose Properties, does SSMS show you the server name? Can you connect using the name shown rather than how you're connecting now? (That's a new feature, if I recall. I can't recall when they added the new tab in the properties window to show you instance info.)

New Post: SSAS 2012 using ASSP : "No connection could be made because the target machine actively refused it."

furmangg — Mon, 29 Apr 2013 14:33:41 GMT

New Post: Clr Assembly must have main file specified

RyanDev — Mon, 29 Apr 2013 13:39:22 GMT

Hi,

I had the same issue but I found out what was going on. I had copied the 2012 ASSP.DLL to C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP and tried to register it after unblocking it - no joy. Then I double checked it was unblocked, and sure enough, it wasn't - even if I tried to unblock it repeatedly, it would appear to be working (no error appears when you click OK or Apply in Properties), but it had not unblocked it - clearly this is related to the folder being part of Program Files. I am a server admin by the way.

I then moved the file to my desktop, unblocked it again, went back in to Properties and checked and now it was unblocked - it then registered fine.

New Post: SSAS 2012 using ASSP : "No connection could be made because the target machine actively refused it."

fpatou — Mon, 29 Apr 2013 10:05:18 GMT

CALL ASSP.DMV("SELECT * FROM $SYSTEM.DISCOVER_SESSIONS") : This doesn't work ! :-( same error message

SSAS instance run under domain account and i gave ImpersonateServiceAccount and Unrestricted to the permission set...

SQL browser is running

thanks for your help ...

New Post: SSAS 2012 using ASSP : "No connection could be made because the target machine actively refused it."

fpatou — Mon, 29 Apr 2013 10:05:18 GMT

New Post: SSAS 2012 using ASSP : "No connection could be made because the target machine actively refused it."

dgosbell — Mon, 29 Apr 2013 09:42:46 GMT

Usually this "actively refused" error means that the SSAS Service or SQL Browser service is not running. (see http://msdn.microsoft.com/en-us/library/cc917670.aspx)

Can you run other ASSP functions like CALL ASSP.DMV("SELECT * FROM $SYSTEM.DISCOVER_SESSIONS") ?

Is your SSAS instance running under a domain account or one of the built-in accounts like local system or network service.

What permissions and impersonation options did you choose when you installed ASSP?

New Post: SSAS 2012 using ASSP : "No connection could be made because the target machine actively refused it."

dgosbell — Mon, 29 Apr 2013 09:42:46 GMT

New Post: SSAS 2012 using ASSP : "No connection could be made because the target machine actively refused it."

fpatou — Mon, 29 Apr 2013 07:51:41 GMT

Hello...on SSAS 2012 i'm trying to use this command

CALL ASSP.DiscoverXmlMetadataFull("\Databases\Database", "State<>'Processed'" ,"<ObjectExpansion>ExpandObject</ObjectExpansion>")

and get error :

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

Any ideas to solve it ?

Regards

New Post: SSAS 2012 using ASSP : "No connection could be made because the target machine actively refused it."

fpatou — Mon, 29 Apr 2013 07:51:41 GMT

New Post: ASSP2012 in MVS2008 cannot reference msmgdsrv 2012

fpatou — Thu, 25 Apr 2013 13:06:57 GMT

You are right !!!!

For your information as I was in a hurry i used http://monodevelop.com/ as a free alternative to VS2010 ! and it works great now i can manage to compile !!!!!

thank you

New Post: ASSP2012 in MVS2008 cannot reference msmgdsrv 2012

fpatou — Thu, 25 Apr 2013 13:06:57 GMT

You are right !!!!

For your information as I was in a hurry i used http://monodevelop.com/ as a free alternative to VS2010 ! and it works great now i can manage to compile !!!!!

thank you

New Post: ASSP2012 in MVS2008 cannot reference msmgdsrv 2012

furmangg — Thu, 25 Apr 2013 12:46:33 GMT

I believe msmgdsrv.dll for Analysis Services 2012 is a .NET 4 DLL. So I think you're right. you need to upgrade to a newer version of Visual Studio.

New Post: ASSP2012 in MVS2008 cannot reference msmgdsrv 2012

furmangg — Thu, 25 Apr 2013 12:46:33 GMT

I believe msmgdsrv.dll for Analysis Services 2012 is a .NET 4 DLL. So I think you're right. you need to upgrade to a newer version of Visual Studio.

New Post: ASSP2012 in MVS2008 cannot reference msmgdsrv 2012

fpatou — Thu, 25 Apr 2013 12:10:15 GMT

i use VS2008....i i cannot have a target on .net4....i guess i cannot use it with VS2008, do you confirm ?

Regards

New Post: ASSP2012 in MVS2008 cannot reference msmgdsrv 2012

fpatou — Thu, 25 Apr 2013 12:10:15 GMT

i use VS2008....i i cannot have a target on .net4....i guess i cannot use it with VS2008, do you confirm ?

Regards

New Post: ASSP2012 in MVS2008 cannot reference msmgdsrv 2012

furmangg — Thu, 25 Apr 2013 12:07:07 GMT

If you haven't already seen, there's a separate ASSP2012.csproj file in the source control for our project. I would definitely start from there then include your changes. It's a VS2010 project, but you should be able to upgrade it to VS2012 if you like.

On my laptop, I do compile ASSP2012 using a msmgdsrv reference that points to:
C:\Program Files\Microsoft Analysis Services\AS OLEDB\110\msmgdsrv.dll

Did you change your project to target .NET 4?

If you have Analysis Services installed on your laptop, you can also find this DLL under the bin directory (depending on your instance name and where you installed it):
C:\program files\microsoft sql server\MSAS11.MSSQLSERVER\OLAP\bin

Let us know if the above doesn't help and we'll research further.

New Post: ASSP2012 in MVS2008 cannot reference msmgdsrv 2012

furmangg — Thu, 25 Apr 2013 12:07:07 GMT

New Post: ASSP2012 in MVS2008 cannot reference msmgdsrv 2012

fpatou — Thu, 25 Apr 2013 09:14:32 GMT

Hello..

Switching form SSAS 2008R2 to 2012, i would like to recompile ASSP with our update :-)...but

"Warning 29 The referenced component 'msmgdsrv' could not be found."

Please help as i reference msmgdsrv from V11 (2012).

of course this DLL is present in 64 and 32 bit in folder :

C:\Program Files\Microsoft Analysis Services\AS OLEDB\110
C:\Program Files x86)\Microsoft Analysis Services\AS OLEDB\110

what is wrong ?

Regards