KB43641: When connecting a Essbase 11, "Load Essbae API Library failure () Failed to dynamically load library essapinu.dll" error message appears when trying to open the MDX cube catalog

SYMPTOM:
When trying to connect to Essbase 11 using the Strategy Cube Provider the following error was shown:

Database error <>: XMLA Discover failed. SOAP Error. Error type: XMLA error. XMLAError:<faultcode>soap:Cliend</faultcode><faultcode>http://mhmap46atst.ad.upacc.com/StrategyMDX/StrategyMDX.asmx</faultactor><faultstring>System.Web.Services.Protocols.SoapException: Fault occurred at Service.Discover(String RequestType, XmlElement Restrictions, XmlElement Properties)</faultstring><detail><MSTRXmlaErrorCode xmlns=urn:schemas-Microsoft-com:xml-analysis String="Session Handler: ConnectionError: Load Essbae API Library failure (Server Message -1) Failed to dynamically load library 'essapinu.dll'. (Server message 305419896) The specified module could not be found. (Windows API error 126) (Server Message -1)"></MSTRXmlaErrorString><InternalErrorCode xmlns=urn:schemas-microsoft-com:xml-analysis Code="0"></InternalErrorCode><InternalErrorString xmlns=urn:schemas-microsoft-com:xml-analysis

• EPM_ORACLE_HOME=C:\Oracle\Middleware\EPMSystem11R1\
• ESSBASEPATH=C:\Oracle\Middleware\EPMSystem11R1\common\EssbaseRTC-64\11.1.2.0

Your actual paths will be different depending on your selection.
ACTION:
If these variables are not defined, you need to run the Oracle Essbase client install and the EssbaseConnector_SetEnv64_64 command file. You need to first run the Oracle EssbaseClient.exe installation which will define the system variable EPM_ORACLE_HOME. Unless this variable exists, you will not be able to run our command file. Then you run our command file, EssbaseConnector_SetEnv64_64.cmd which will define ESSBASEPATH and make changes to the PATH system variable. Make sure to run EssbaseClient.exe as Administrator as well as the EssbaseConnector_SetEnv_64_64.cmd as Administrator – the Client Tools installation will not succeed if you are not the Administrator, and one of the steps of the CMD file (modifying the registry) will not be successful if you are the Administrator.
Check the path for the additions, these will be based on the two variables above.
When you make changes to these variable make sure to restart IIS.  To restart IIS use a Windows Command Prompt.  MAKE SURE to right mouse click and select RUN AS ADMINISTRATOR. Then type ‘iisreset’.
If the same error still appears check the ‘PATH’ environmental variable. Try moving the PATH changes for the Essbase client to the beginning of the path variable and run iisreset command to restart IIS again.
Please follow up with your in house Essbase administrator for additional help with any modifications and/or questions on the Essbase platform.
43641