SSIS OData cannot acquire a managed connection from the run time connection manager

Questions
, ,
23

That is interesting. We are not aware that SSIS does not support TLS 1.2 or not completely.

Invantive Cloud (including Invantive Bridge Online) have always been running on TLS 1.2 and TLS 1.3. Perhaps the suite of ciphers has changed recently due to the switch to a load balancer and some new components. This was previously not possible on AWS due to the use of websockets, but on the new French datacenter of Scaleway it runs fine.

Some alternatives that might be possible when SSIS indeed does not completely support TLS 1.2:

  • Use curl from a batch file to download the data to a file and then pick it up using SSIS. Run batch from SSIS.
  • Use curl from a batch file to download the data to a file and then pick it up using SSIS. Run batch from task scheduler.
  • Use a local proxy website that removes HTTPS altogether or downgrades to a previous TLS version. Maybe Caddy, but might have the same TLS issues.
  • Wait till Invantive UniversalSQL Server becomes available for general use on Invantive Cloud.
  • Use a local deployment of Invantive UniversalSQL Server, but it is only available in BETA currently. Note that UniversalSQL Server also focuses on new technology, including TDS 8 and TDS 7.3 (first one complete TLS stream, second one only for payload in packets).