The .Net Agent fails to connect EM using SSL communications

Document ID : KB000107790
Last Modified Date : 30/07/2018
Show Technical Document Details
Issue:
When attempting to connect a .Net (DotNet) agent to an Enterprise Manager (EM) using an ssl (Secure Socket layer) url  (as described in the product documentation)

For example: agentManager.url.1=ssl://myserver.com:5101

it fails to connect and reports the following error.

[WARN] [IntroscopeAgent.Isengard] Could not add EM 1 because of invalid Connection Properties: Exception creating socket factory for 'client.socketfactory.1.default' property: com.wily.isengard.postofficehub.link.net.SSLSocketFactory: Can't find com.wily.isengard.postofficehub.link.net.SSLSocketFactory : Searched in domain: Name:PerfMonCollectorAgent.exe There are no context policies. mscorlib: Could not load type 'com.wily.isengard.postofficehub.link.net.SSLSocketFactory' from assembly 'mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'. .....
[IntroscopeAgent.Isengard] No valid Enterprise Manager locations were found in the property introscope.agent.enterprisemanager.connectionorder in IntroscopeAgent.profile. Using default settings.
[INFO] [IntroscopeAgent.Isengard] The Agent will connect to the Introscope Enterprise Manager using: FIXME target: localhost:5001 read buffer size: 32768 write buffer size: 32768
Environment:
APM 10.7
Resolution:
To workaround this issue use the HTTPS tunneling as workaround described in knowledge document 000037728 - The .NET Agent can only connect to the Enterprise Manager (EM) over SSL by tunneling through the HTTPS port of the Enterprise Manager (EM) Web Server, but what are the steps to achieve this.