Connect to a Cube Via Alteryx

[adam_rafael_18]

Hi,

I am trying to connect to a cube  (Microsoft Office Data Connection) via Alteryx. I have created the connection, and in the Visual Query Builder, I see the names of the various tables within the cube. I am using MDX to attempt to query the data, and when I test my query, it says successful. However, when I go to run the workflow, I get the following Error:

Error: Input Data (3): Error opening table "{MDX QUERY-}" Interface ISupportErrorInfo not available

How do I fix the ISupportErrorInfo Error?

[KGT]

This is not a solution, but may help to troubleshoot. This could be several different things but is most likely something in the query.

I hope this link goes straight to the 20th comment, if not, you are looking for the comment by @nbrenner at the bottom of page 2. This might give some assistance in finding out what the error is with the query.

Looking through a couple of different posts on this error, it seems it's mostly been found connecting to AD previously, but always connecting to MS items (I don't think this is exclusionary, I just couldn't find an example that didn't involve MS interfaces). It looks to be that if a field can't be found/matched or part of the query can't be resolved etc then this error can be thrown.

Extra Info not relevant to solving the error:

In order to get more info on the error, the underlying call would need to continue to call for InterfaceSupportsErrorInfo methodto get the details of the error. I imagine this would only be implemented if the connector was designed specifically for an MS connection, which an ODBC is not. I would like to say that I'm surprised the ODBC interface/driver (I think interface is more appropriate but to the layman, it seems the same as a driver) that sets up this connection doesn't handle it, but that wouldn't be on the core list of items and so MS is not going to make the driver/interface heavier if they don't need to, even though it would offer much better interoperability with their products.

[adam_rafael_18]

Thanks for the help - unfortunately I'm still running into the issue. Alteryx seems to be able to connect to the SSAS data, but it is not reading the inputs correctly (all of the fields in the Visual Query Builder are appearing as "objects" as opposed to Vstrings or Double). Do you know how I would be able to fix that?

[albert_alaluf]

Hi @adam_rafael_18 

When you say 'cube', is it essbase?

[KGT]

Just flagging that the issue could be in the connection type. You are using a Microsoft Office Data Connection and connecting to SSAS. 

I did a job about 2016 that connected to SSAS from Alteryx. Even then, there was very little support or updates to connect from non MS services. I ended up having to use a CLI to download the data in XML format and parse it. I built a tool for it at the time, but there were definitely straws holding up walls (and significant data limits). From that point I said "no" to connecting to SSAS. I can't even find that CLI now.

I only say this, as the issue might be right at the start with the type of connection. 

[apathetichell]

@albert_alaluf-> https://learn.microsoft.com/en-us/analysis-services/multidimensional-tutorial/lesson-2-2-defining-a-...