Is there any update to this thread?
I am facing the same issue
OS: Server 2016
ODBC Driver: ODBC Driver 17 for SQL Server
SQL: 2016 SP2
App Volumes: 2.15 / 2.14.2
I can create the connection using ODBC Driver 17 64bit/32bit and it connects to the Database but if I use the App Volumes Wizard I get the same errors.
I checked and my Cipher Suites and allowed protocols match up with the SQL server (also evident by the successful manual configuration of a ODBC connection). The solution better not be: Allow SSL 3.0 for the initial configuration then modify the ODBC connection. I cannot do that to a production SQL instance.
Thinking of having the DBAs delete the database and start again. The only thing that might be an issue, is that I had them create the database under one name and then rename it at a later date. Not sure how that would matter as nothing was written to the database and I had them add a domain service account as db_owner after it was renamed. At this point I am willing to try anything.
I'm experiencing the same issue. I can manually specify the 'svmanager' ODBC connection with the correct SQL driver and it works in ODBC administrator. I then run the installer which changes it to an older ODBC driver that will not connect to our SQL instance.
Has anyone found a way out of this loop?
Got the same thing, got this response from support
Yes, believe App Volumes requires TLS1.0 to be enabled due to the SQL ODBC connector it attempts to use.
The installer doesn’t have the capability currently to use the SQL Native Client which supports TLS 1.1 and 1.2. Yes, App Volumes requires TLS1.0 to be Yes, App Volumes requires TLS1.0 to be enabled due to the SQL ODBC connector it attempts to use. The installer doesn’t have the capability currently to use the SQL Native Client which supports TLS 1.1 and 1.2.
Planned to be supported in later releases
Well I hope that is not the case. I cannot re-enable TLS 1.0 on a production SQL server just to get App Volumes installed and working.
I was really hoping for some quirky command line install that would force it to load the SQLNC 11 drivers.