SQL2012 SP1 breaks connection to Essbase through ADOMD.NET - by GregGalloway

Status : 


Sign in
to vote
ID 774580 Comments
Status Active Workarounds
Type Bug Repros 5
Opened 12/17/2012 12:24:22 PM
Access Restriction Public


It looks like SQL2012 SP1 changes to ADOMD.NET broke connections to Essbase via ADOMD.NET. Now we’re getting this error:
Element 'return' was not found. Line 1, position 252.
   at System.Xml.XmlReader.ReadStartElement(String name)
   at Microsoft.AnalysisServices.AdomdClient.XmlaReader.ReadStartElement(String name)
   at Microsoft.AnalysisServices.AdomdClient.XmlaClient.SupportsProperty(String propName)
   at Microsoft.AnalysisServices.AdomdClient.XmlaClient.Connect(ConnectionInfo connectionInfo, Boolean beginSession)
   at Microsoft.AnalysisServices.AdomdClient.AdomdConnection.XmlaClientProvider.Connect(Boolean toIXMLA)
   at Microsoft.AnalysisServices.AdomdClient.AdomdConnection.XmlaClientProvider.Microsoft.AnalysisServices.AdomdClient.AdomdConnection.IXmlaClientProviderEx.ConnectXmla()
   at Microsoft.AnalysisServices.AdomdClient.AdomdConnection.ConnectToXMLA(Boolean createSession, Boolean isHTTP)
   at Microsoft.AnalysisServices.AdomdClient.AdomdConnection.Open()
.ClientVersion returns:
11.0.3000.0 ((SQL11_PCU_Main).121019-1325 )
Disassembling the DLL, it looks like the XmlaClient.SupportsProperty function is new. I guess Essbase doesn’t support DISCOVER_PROPERTIES? If there was a property you could set on the connection string to have it skip this code path, that would be nice.
I was able to install a prior version of ADOMD.NET and it’s working again. But a fix would be nice for the sake of others who might be using ADOMD.NET for this purpose.
Sign in to post a comment.