[Intelligence Server Name]: Connection failed: Unable to find path to the certification target. Please verify that the path to the certification is correct and restart the Strategy Web server.
This error will occur despite the fact that the root CA and server certificate have already been added to the cacerts trustore for the JRE.
CAUSE:This is an identified defect in Strategy Web 10.2 and Strategy Intelligence Server 10.2. Starting with 10.2, the Strategy Intelligence Server only accepts TLS v1.2 connections when using SSL encryption, but when using JRE 1.7, the ASP version of Strategy Web 10.2 only initiates contact using TLS v1.0. Due to the initial connection version mismatch, the Intelligence Server rejects the connection attempt.
ACTION:This issue has been addressed in Strategy Web 10.3 Hotfix 1. Upgrade to this version to take advantage of this fix.
WORKAROUND:There are two workarounds available for this issue:
A. Upgrade to JRE 1.8. This can be done by following the steps below:- Download JRE 1.8 to match the server version in use, either x86 or 64-bit: http://www.oracle.com/technetwork/java/javase/downloads/jre8-downloads-2133155.html
- Unpack/install the JRE in a stable location that can be referenced via the registry.
"Stable location" can be further defined as a location that will not have its drive path changed, and where the JRE will not need to be moved from. - Change the registry path for the JVM per tech ntoe KB15443. The path should lead to a file called "jvm.dll."
Note: If using a 64bit machine, the path is:
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\MicroStrategy\JNI Bridge 64\Configuration.
- Add the Intelligence Server root CA and server certificate to the JRE 1.8 cacerts truststore.
- Restart Microsoft IIS.
B. Use a custom trust store.
- Create a custom truststore and add the Intelligence Server root CA and server certificate.
- Open WebASPx/WEB-INF/Strategy.xml and find the entries listed below:
<parameter name="sslTruststore" value="/WEB-INF/trusted.jks" />
<parameter name="sslTruststorePwd" value="mstr123" />
- Modify the entries to match the location of the truststore, and the password set for the truststore.
- Restart IIS.
Following either of the workarounds above will cause the Web server to use TLSv1.2.
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.
