KB36325: "Could not initialize dynamic link library sapjcorfc...." error is seen when attempting to connect to an SAP BW datasource from MicroStrategy Intelligence Server.

 

Database error <>: Connect failed. Unable to connect.
Error type: JCO layer error. JCOConnection.connect failed. java.lang.ExceptionInInitializerError: JCO.classInitialize(): Could not load middleware layer 'com.sap.mw.jco.rfc.MiddlewareRFC'
JCO.nativeInit(): Could not initialize dynamic link library sapjcorfc . java.library.path [C:\Program Files (x86)\Common Files\Strategy;.;C:\WINDOWS\Sun\Java\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\Program Files (x86)\MicroStrategy\Desktop\;C:\Program Files (x86)\Common Files\Strategy;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files (x86)\Common Files\Strategy;C:\Program Files (x86)\MicroStrategy\Desktop;C:\Program Files (x86)\MicroStrategy\Command Manager;C:\Program Files (x86)\MicroStrategy\Enterprise Manager;C:\Program Files (x86)\Common Files\MicroStrategy\JRE\160_07\Win32\bin;C:\Program Files (x86)\Common Files\MicroStrategy\Docume

 
 
It is verified that the connector files being used are 32-bit libraries. The same error is received when using the HelloSAP utility.
 
CAUSE
This error can be seen when the Windows operating system is missing certain run-time dependencies. Most commonly MSVCR71.DLL and/or MSVCP71.DLL are missing from the machine where Strategy Intelligence Server is installed. These DLLs should be in the location: C:\WINDOWS\SysWOW64, for a 64-bit Windows operating system. For 32-bit Windows operating system, these should be located at: C:\WINDOWS\System32.
 
ACTION
If one of the above mentioned DLL is missing, obtain this DLL from a different Windows installation running the same operating system version and place it in the required location.
 
If the above mentioned DLLs are present and the error is still seen, the 3rd party tool Dependency Walker  (http://www.dependencywalker.com/) can be used to verify which dependent DLL is missing. The following Strategy Knowledge Base document can be used as a reference for how to use dependency walker. The DLL shown in the error message (SAPJCORFC.DLL) can be directly opened from Dependency Walker to find the missing dependent libraries.
 
KB19006 (KB1100-8X-0642): How to use Dependency Walker to profile DLL's accessed by an application