Network: Failure to communicate with Strategy Intelligence Server.
This may also manifest as Developer hanging on startup if this Project Source was the last Project Source used, since Developer will also attempt to automatically connect to the last Project Source on startup.
CAUSEThis behavior is a known defect in Strategy 10.x and is associated with another known defect documented here:
KB290104: The error "invalid procedure call or argument" is seen when trying to connect to an Intelligence Server using SSL with the setting "verify certificate" in Strategy Secure Enterprise 10
Once a connection attempt has been made through Developer using the "Use SSL" and "Verify server certificate" options (which fails according to the defect discussed in KB290104), further connection attempts from Developer to the SSL port will also fail even if the "Verify server certificate" option is disabled. This behavior will also be seen from other different computers attempting to connect to the same Project Source over SSL without "Verify server certificate". Connections not using SSL will be successful.
ACTIONThis issue has been fixed in Strategy version 10.5 and 10.4 Hotfix 2. Please upgrade to one of these versions to receive this fix.
WORKAROUNDSSL connections not using the "Verify server certificate" option will continue to fail until the Strategy Intelligence Server is restarted or till the client which initially tries to connect using the "verify certificate" option is closed. After restarting, normal SSL connections will work. However, if another connection attempt is made using the "Verify server certificate" option, normal SSL connections will begin failing again until the Intelligence Server is restarted again or that client is closed.
The Strategy internal reference number for the issue described in this Technical Note is DE37792.
