KB414191: Error "The resource cannot be found" and "Errors in the OLE DB provider" occur when connecting to cubes on Microsoft Analysis Services 2012 via MDX Cube Catalog in MicroStrategy Developer 9.4.1

SYMPTOM:
 
In Strategy Developer 9.4.1, the user is unable to view the cubes on Microsoft Analysis Services 2012 via MDX Cube Catalog since it returns error message "The resource cannot be found".
 
Then use XMLA Connectivity Test tool to test the connection between the Strategy Developer client machine and the Microsoft Analysis Service host machine, error messages are seen in the test outputs as below.
 

Fault occurred
at Service.Discover(String RequestType, XmlElement Restrictions, XmlElement Properties)</faultstring><faultactor>http://localhost/StrategyMDX/StrategyMDX.asmx
</faultactor><detail><MSTRXmlaErrorCode MSTRXmla:Code="00000000" xmlns:MSTRXmla="urn:schemas-microsoft-com:xml-analysis" xmlns="urn:schemas-microsoft-com:xmlanalysis" /><MSTRXmlaErrorString MSTRXmla:String="SessionHandler: ConnectionError: HResult: 2147467259
Description: Errors in the OLE DB provider. An error occurred while named instance information was beingretrieved from the SQLBrowser service on the 'xxx' server.
Source: Microsoft OLE DB Provider for SQL Server 2012 Analysis Services.
 (Server message -1)        HResult: -2147467259
Description: Errors in the OLE DB provider. Could not connect to the redirector. Ensure that the SQLBrowser service is running on the 'xxx' server.
Source: Microsoft OLE DB Provider for SQL Server 2012 Analysis Services.
 (Server message -1)            UID=xxx;Catalog=xxxx;OLAPProvider=MSOLAP;AuthMode=3; (Server message
-1)" xmlns:MSTRXmla="urn:schemas-microsoft-com:xml-analysis" xmlns="urn:schemas-
microsoft-com:xml-analysis" />

 
CAUSE:
 
One possible cause is that the SQLBrowser service is not running on the Analysis Service host server.
 
In this case, the Microsoft Analysis Service is not deployed properly on its host machine. It refuses the client machine to browse the named instance. This is verified since the cubes are not accessible even using a third-party application such as SQL Server Management the same client machine where Strategy Developer is installed. Neither can the user ping the Analysis host machine from the client machine.
 
 
ACTION:
 
Since this issue is separate from Strategy dependencies, the user should contact their Analysis Service administrator or Microsoft to further troubleshoot the problem.
 
For usage of XMLA Connectivity Test tool, refer to following document:
KB14715 - How to use the XMLA Connectivity Test Tool available in Strategy 9.x
 
 
Third Party Software Installation WARNING
 
The third-party product(s) discussed in this technical note is manufactured by vendors independent of Strategy. Strategy makes no warranty, express, implied or otherwise, regarding this product, including its performance or reliability.
 
 
 
 
 

KB414191