Clever Geek Handbook

ADOMD connection error

I am getting the following error from ADOMD when trying to connect to my SSAS server.

An unhandled exception of type 'System.Xml.XmlException' occurred in Microsoft.AnalysisServices.AdomdClient.dll

Additional information: Element 'return' not found. Line 5, position 2.

I can confirm the following:

My connection string:

Data Source=<MyServer>;Catalog=<My SSAS DB>; UID=<MyDomain>\<MyDomainUser>;PWD=<MyPassword>;

I can confirm that the connection string is correct (or at least the data I am using in the above connection string is correct). If I change any part of the connection string to an invalid value, ADOMDConnection will return "Unable to connect to server". I also looked at the audit logs on the server itself and confirmed that I am successfully logging into the server. Conversely, with incorrect credentials, the server logs confirm a failed login.

I am trying to connect to SSAS 2014 Enterprise

The faulty connection returns within a few seconds. Several Internet posts suggest increasing the Connection Timeout property. This doesn't sound like my problem as I bumped it up to 120 and it fails over 5.

I am using ADOMD 12.0 Runtime 2.0.50727

My domain user is a domain administrator and has been added to the administrator role in SSAS.

I'm not sure what else might be wrong or how to debug this or is this a known bug in ADOMD?

Any advice would be greatly appreciated.

thank!

Jason

+3


source to share


1 answer


This occurs regularly when the version of the ADOMD client DLL is not a version that matches the target version of the server instance. For example, Azure Analysis Services as of 09/13/2017 does not work with Microsoft.AnalysisServices.AdomdClient.dll version 13. Only version 14 and higher.

For reference, the ADOMD DLL for Azure Analysis Service is available at the following link: https://docs.microsoft.com/en-us/azure/analysis-services/analysis-services-data-providers



Double check to make sure the client DLL is the exact version required for the target server instance. This solved this problem in my case.

+1


source






More articles:


All Articles