Note: the hotfix referenced herein is not officially supported. However, it's being provided as-is for convenience.

Symptoms

Using sfconnect connector can result in a "System.Net.WebException: The request was aborted: Could not create SSL/TLS secure channel." error in the VSI Launcher console output. This will result in the targets not being connected to.

Here's an example screenshot.

Cause

It could be that TLS 1.2 is being used.

Login VSI uses the .NET framework version 4.5.2. .NET 4.5.2 cannot automatically negotiate some of the more recent security protocols for HTTP communication. When SFConnect tries to communicate with the StoreFront server it can't agree with the Storefront server on which protocol to use. As, it doesn't support any of the protocols offered. This is why the message is that a secure channel couldn't be established.

Resolution

1. If possible, un-use TLS 1.2; follow the Microsoft reference to do this
2. Or download the attached file on this article, TLS12.zip, and extract LoginVSI.Connectors.Model.dll out
   1. Close out of the Login VSI Management Console and the Target Launcher(s)
   2. Backup the existing file: \\{VSIserver Share}\{Login VSI Share}\_VSI_Binaries\Connectors\LoginVSI.Connectors.Model.dll by renaming it or moving it out of the Login VSI share
   3. Into this directory, copy in the LoginVSI.Connectors.Model.dll file which was extracted from TLS12.zip
   4. Start a new test to verify the issue is no longer present

Properties

Applies to

Login VSI 4.x

See also

1. Microsoft reference on enabling and disabling TLS 1.2
2. Login VSI sfconnect reference