KB322001: When utilizing Oracle Essbase 11.1.2.4 Client and Server Applications, an error occurs when trying to add a MDX Cube to a Project in MDX Cube Catalog in MicroStrategy 9.x and 10.x.

• Strategy

This Technical Note describes an issue after upgrading Oracle Essbase Client and Server to version 11.1.2.4. After completion of the upgrade, an error is received in MDX Cube Catalog when trying to move over a cube to be accessible for the project. This is known issue in MicroStrategy 9.x and 10.x.

Summary:
This Technical Note describes an issue after upgrading Oracle Essbase Client and Server to version 11.1.2.4. After completion of the upgrade, an error is received in MDX Cube Catalog when trying to move over a cube to be accessible for the project. This is known issue in Strategy 9.x and 10.x.

Symptom:
After completing the upgrade in Oracle, try to add an ASO (Aggregated Storage Option) cube or BSO (Block Storage Option) cube to a project through MDX Cube Catalog in Strategy Developer. An error is returned as demonstrated in the screenshot below.


Error: XMLA Discover failed. SOAP Error. Error type: XMLA error. XMLA[SOAP Fault]:<faultcode>soap:Client</faultcode><faultactor>http://localhost/StrategyMDX/StrategyMDX.asmx</faultactor><faultstring>System.Web.Services.Protocols.SoapException:Fault occurred at Service.Discover(StringRequestType, XmlElement Restrictions, XmlElement Properties)</faultstring><detail><MSTRXmlaErrorCode xmlns=urn:schemas-microsoft-com:xml-analysis Code= "00000000"></MSTRxmlaErrorCode>.....Logging in user [admin@NativeDirectory]1-(Server message -1) (Server message -1)"></MSTRXmlaErrorString><InternalErrorCode xmlns=urn:schemas-microsoft-com:xml-analysis Code="0"></InternalErrorCode><InternalErrorString xmlns=urn:

Cause:
This is an identified limitation of MDX Cube Provider with the newest version (11.1.2.4) of Oracle Essbase.

Action:
This issue has been addressed starting in version 10.9 or 10.4 Hotfix 5. Please upgrade to these versions to take advantage of this fix.

Workaround:
We have observed a possible workaround of utilizing the 11.1.2.2 or 11.1.2.3 Oracle Essbase Client with the 11.1.2.4 Oracle Essbase Server, but this will only allow the cube to be added to the project if it is a BSO (Basic Storage Option) MDX cube. If using an ASO MDX Cube (Aggregate Storage Option) this workaround will not apply.

The Strategy Internal Reference Number for the issue discussed in this technical note is DE53449.

Comment

0 comments

Details

Knowledge Article

Published:

April 14, 2017

Last Updated:

November 9, 2017

Error: XMLA Discover failed. SOAP Error. Error type: XMLA error. XMLA[SOAP Fault]:<faultcode>soap:Client</faultcode><faultactor>http://localhost/StrategyMDX/StrategyMDX.asmx</faultactor><faultstring>System.Web.Services.Protocols.SoapException:Fault occurred at Service.Discover(StringRequestType, XmlElement Restrictions, XmlElement Properties)</faultstring><detail><MSTRXmlaErrorCode xmlns=urn:schemas-microsoft-com:xml-analysis Code= "00000000"></MSTRxmlaErrorCode>.....Logging in user [admin@NativeDirectory]1-(Server message -1) (Server message -1)"></MSTRXmlaErrorString><InternalErrorCode xmlns=urn:schemas-microsoft-com:xml-analysis Code="0"></InternalErrorCode><InternalErrorString xmlns=urn: