We've been connecting to a vendor, Heartland, using a web service task in SSIS to consume our data and bring it down and insert the data into a SQL server table.
This last Wednesday, they upgraded their environment to only accept TLS 1.2 protocols and gave us no notice. Unfortunately, we can no longer send a request as our connection is immediately closed.
We've been working to find a solution to help us use a TLS 1.2 value within our SSIS package as we cannot make a change on the SQL Server or OS to use the TLS 1.2 protocol because other apps are using TLS 1.0 and TLS 1.1.
We're working on SQL Server 2014 and SSIS 2013. Our understanding is that TLS 1.2 is enabled in these environments by default. But I'm not finding that to be the case. When I look at the value of this class: System.Net.ServicePointManager.SecurityProtocol
in my C# script were I try to set a TLS value for the security protocol I see Ssl3 | Tls in the AUTOS window. And when I change the value of the protocol I see Tls12 value. Then I execute my web service task and get this error:
[Web Service Task] Error: An error occurred with the following error message: "Microsoft.SqlServer.Dts.Tasks.WebServiceTask.WebserviceTaskException: The Web Service threw an error during method execution. The error is: The underlying connection was
closed: An unexpected error occurred on a send..
at Microsoft.SqlServer.Dts.Tasks.WebServiceTask.WebMethodInvokerProxy.InvokeMethod(DTSWebMethodInfo methodInfo, String serviceName, Object connection)
at Microsoft.SqlServer.Dts.Tasks.WebServiceTask.WebServiceTaskUtil.Invoke(DTSWebMethodInfo methodInfo, String serviceName, Object connection, VariableDispenser taskVariableDispenser)
at Microsoft.SqlServer.Dts.Tasks.WebServiceTask.WebServiceTask.executeThread()".
Any suggestions on a work around? Any help/direction would be appreciated. Thanks.