Underlying connection was closed, an unexpected error occurred on a send with Qlik GeoAnalytics

[Sonja_Bauernfeind]

You may experience issues when using Qlik GeoAnalytics Connector due to TLS 1.2 not being enabled.

The following error can be seen in the log file C:\ProgramData\QlikTech\Custom Data\IdevioGeoAnalyticsConnector\Log\StackTrace.txt

System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a send. ---> System.IO.IOException: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. ---> System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host

   at System.Net.Sockets.Socket.Receive(Byte[] buffer, Int32 offset, Int32 size, SocketFlags socketFlags)
   at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size)
   --- End of inner exception stack trace ---
   at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size)
   at System.Net.FixedSizeReader.ReadPacket(Byte[] buffer, Int32 offset, Int32 count)
   at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.ForceAuthentication(Boolean receiveFirst, Byte[] buffer, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.ProcessAuthentication(LazyAsyncResult lazyResult)
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)

Environment:

Qlik GeoAnalytics 

The issue is due to the site https://ga.qlik.com no longer allows connections using TLS 1.0 and TLS 1.1, but only supports TLS 1.2 as part of security requirements.

To solve the issue do one of the following:

1. Upgrade to .NET 4.6 or newer. TLS 1.2 should then be enabled by default.
2. Make sure that you have a version of .NET that supports TLS 1.2, see https://docs.microsoft.com/en-us/configmgr/core/plan-design/security/enable-tls-1-2#update-net-frame..., then update the connector to the February 2018 version or newer.