EducationSoftwareStrategy.com
StrategyCommunity

Knowledge Base

Product

Community

Knowledge Base

TopicsBrowse ArticlesDeveloper Zone

Product

Download SoftwareProduct DocumentationSecurity Hub

Education

Tutorial VideosSolution GalleryEducation courses

Community

GuidelinesGrandmastersEvents
x_social-icon_white.svglinkedin_social-icon_white.svg
Strategy logoCommunity

© Strategy Inc. All Rights Reserved.

LegalTerms of UsePrivacy Policy
  1. Home
  2. Topics

KB214492: "QueryEngine encountered error: XMLA Execute failed. SOAP Error" when running queries/reports against MDX Cube Provider in MicroStrategy Developer 9.x


Stefan Zepeda

Salesforce Solutions Architect • Strategy


This article provide a potential root cause of the error message "QueryEngine encountered error: XMLA Execute failed. SOAP Error" when running queries/reports against MDX Cube Provider with Essbase

SYMPTOMS:
After importing an Essbase cube and trying to expand the cube's dimensions hierarchies, the following error message is received:


QueryEngine encountered error: XMLA Execute failed. SOAP Error.

Error type: XMLA error. XMLAError[SOAP Fault]: <faultcode>soap:Client</faultcode><faultactor>http://10.99.201.38/StrategyMDX/StrategyMDX.asmx</faultactor><faultstring>System.Web.Services.Protocols.SoapException: Fault occurred

   at Service.Execute(XmlElement Statement, XmlElement Properties)</faultstring><detail><MSTRXmlaErrorCode xmlns=urn:schemas-microsoft-com:xml-analysis Code="00000000" ></MSTRXmlaErrorCode><MSTRXmlaErrorString xmlns=urn:schemas-microsoft-com:xml-analysis String="SessionHandler::executeMDX: Error: Unknown error. (Windows API error -2147467262)

UID=xxxxxx;Catalog=xxxxxx;OLAPProvider=ESSBASE;AuthMode=0;(Server message -1)" ></MSTRXmlaErrorString><InternalErrorCode xmlns=urn:schemas-microsoft-com:xml-analysis Code="0"

></InternalErrorCode><InternalErrorString

xmlns=urn:schemas-microsoft-com:xml-analysis String=""

></InternalErrorString><StackTrace

xmlns=urn:schemas-microsoft-com:xml-analysis String="   at XMLA.

 
When executing a report based on an Essbase Cube from Strategy Web 9.x, the following error message also appears:

QueryEngine encountered error: XMLA Execute failed. SOAP Error.

Error type: XMLA error. XMLAError[SOAP Fault]: <faultcode>soap:Client</faultcode><faultactor>http://10.99.201.38/StrategyMDX/StrategyMDX.asmx</faultactor><faultstring>System.Web.Services.Protocols.SoapException: Fault occurred

   at Service.Execute(XmlElement Statement, XmlElement Properties)</faultstring><detail><MSTRXmlaErrorCode xmlns=urn:schemas-microsoft-com:xml-analysis Code="00000000" ></MSTRXmlaErrorCode><MSTRXmlaErrorString xmlns=urn:schemas-microsoft-com:xml-analysis String="SessionHandler::executeMDX: Error: Unknown error. (Windows API error -2147467262)

UID= xxxxxx;Catalog= xxxxxx;OLAPProvider=ESSBASE;AuthMode=0;(Server message -1)" ></MSTRXmlaErrorString><InternalErrorCode xmlns=urn:schemas-microsoft-com:xml-analysis Code="0"

></InternalErrorCode><InternalErrorString

xmlns=urn:schemas-microsoft-com:xml-analysis String=""

></InternalErrorString><StackTrace

xmlns=urn:schemas-microsoft-com:xml-analysis String="   at XMLA.OCI.ExecuteHandler.executeMDX(StringBuilder sbRowXml, XmlElement RestrictionList, XmlElement PropertyList, XmlElement connectionInfo, String iUserID, String iPwd)

   at Service.Execute(XmlElement Statement, XmlElement Properties)" ></StackTrace></detail>. The embedded SOAP error is: TRXmlaErrorString MSTRXmla: String="SessionHandler::executeMDX: Error: Unknown error. (Windows API error -2147467262) UID= xxxxxx;Catalog= xxxxxx;OLAPProvider=ESSBASE;AuthMode=0; (Server message -1)" xmlns:MSTRXmla="urn:schemas-microsoft-com:xml-analysis" xmlns="urn:schemas-microsoft-com:xml-analysis" /><InternalErrorCode MSTRXmla:Code="0" xmlns:MSTRXmla="urn:schemas-microsoft-com:xml-analysis" xmlns="urn:schemas-microsoft-com:xml-analysis" /><InternalErrorString MSTRXmla: String="" xmlns:MSTRXmla="urn:schemas-microsoft-com:xml-analysis" xmlns="urn:schemas-microsoft-com:xml-analysis" /><StackTrace MSTRXmla: String="   at XMLA.OCI.ExecuteHandler.executeMDX(StringBuilder sbRowXml, XmlElement RestrictionList, XmlElement PropertyList, XmlElement connectionInfo, String iUserID, String iPwd)

   at Service.Execute(XmlElement Statement, XmlElement Properties)" xmlns:MSTRXmla="urn:schemas-microsoft-com:xml-analysis" xmlns="urn:schemas-microsoft-com:xml-analysis" /></detail></soap:Fault></soap:Body></soap:Envelope>. Connection String: HTTP://10.99.201.38/StrategyMDX/StrategyMDX.ASMX;. Connection String: HTTP://10.99.201.38/StrategyMDX/StrategyMDX.ASMX;. SQL Statement: with member [CONCEPTO].[FreeForm_0] as '1'

set [dim0_select_members] as '{[xxxxxxx].Levels(1).members,[xxxxxxx].Levels(2).members}'

set [dim1_select_members] as '{[xxxxxxx].Levels(1).members}'

set [dim2_select_members] as '{[xxxxxxx].Levels(1).members}'

set [dim3_select_members] as '{[xxxxxxx].Levels(1).members}'

select {[xxxxxxx].[FreeForm_0]} on columns,

non empty CROSSJOIN(CROSSJOIN(CROSSJOIN(hierachize{([dim0_select_members]}), [dim1_select_members]), [dim2_select_members]), [dim3_select_members]) on rows

from [MSTPG.xxxxxxx]

.. Error in Process method of Component: QueryEngineServer, Project AA, Job 296, Error Code= -2147212544.

 
 CAUSE:
“USE_MTOM;” is usually included by default when a database instance is created using one of the MDX Cube Provider options as the Database Connection type. However, the Database Connection is created using one of the old versions (using Essbase APS) and then the user switch to our new MDX Cube Provider, it won’t be added.
 
ACTION:
Enter “USE_MTOM;” in the Additional Parameters box in the Advanced tab of the Database Connection


Comment

0 comments

Details

Knowledge Article

Published:

April 14, 2017

Last Updated:

July 17, 2017