SSIS 2012 - Analysis Services Processing task - Connection cannot be made - by Trevor Howe

Status : 

  Not Reproducible<br /><br />
		The product team could not reproduce this item with the description and steps provided.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 778516 Comments
Status Closed Workarounds
Type Bug Repros 3
Opened 2/4/2013 10:10:12 PM
Access Restriction Public


We are busy migrating our packages from SQL 2008 R2 to SQL 2012. Some of our packages process Analysis Services objects as part of the package flow. I have set the connection to the correctly to the 2012 Analysis Services server and Test Connection works fine. When I open up the AS task in the control flow of the package and use the above mentioned connection it give me the error: "A connection cannot be made. Ensure that the server is running". I can connect and browse the cube in Management studio. I am using the Native OLEDB\Microsoft OLE DB Provider for Analysis Services 11.0. Here is the connection string: 
Data Source=<Server>\<Instance>;Initial Catalog=<cube>;Provider=MSOLAP.5;Integrated Security=SSPI;Location=<Server>\<Instance>;
Sign in to post a comment.
Posted by timvdh on 12/19/2014 at 12:02 AM
I received the same error message when executing an SSIS package in a remote server through management studio. When I started the package in management studio on the server itself (or via server agent) it worked. May be a kerberos issue since three hops were required when starting from a remote machine. The "Connection cannot be made" message is misleading since a crendential error will show up differently and the typical kerberos error message is that "ANONYMOUS" cannot connect.
Posted by Microsoft on 6/28/2013 at 11:33 AM
Thanks, we'll investigate.
Posted by kameshperi on 4/4/2013 at 5:21 PM
I have this issue while creating a connection to ssas tabular model (11.03) from SSIS analysis services processing task(11.0). Not sure if it is a bug. Earlier i was able create a connection and see objects when connecting to a ssas tabular 11.0 model.
Posted by Trevor Howe on 2/6/2013 at 1:52 AM

I have managed to solve this issue. Not sure if it is a workaround or whether this is the proper way to do it. To solve the above problem you have to delete the connection to the cube in the Connection Mangers. Then open up the Analysis Services Processing task and recreate the connection (Click New and go through the usual connection stuff). Once this has been done you should be able to see the AS objects that you want to process. It looks like even though you recreate the connection information for the 2012 environment on the migrated package, something about the connection manager object is incompatible with the new package. Deleting this connection and recreating it clears that up.