Hello,
I'm having issues connecting to a remote Microsoft SQL 2014 server after we've changed our SQL servers to required Force Encryption. I was able to connect to it fine prior to this change.
I've tried updating the connection URL and added ssl=request as below, and have even tried values such as require, authenticate, etc. according to http://jtds.sourceforge.net/faq.html :
Original Connection URL: jdbc:jtds:sqlserver://sqlserver.ad.mydomain.com:1433/Database;useNTLMv2=true;domain=mydomain
New Connection URL: jdbc:jtds:sqlserver://sqlserver.ad.mydomain.com:1433/Database;useNTLMv2=true;domain=mydomain;ssl=request
I've also imported the SAN certificate we use on the SQL servers into the Orchestrator configuration and restarted services and rebooted the entire system. Is there a potential problem with using a SAN certificate ( the certificate has our DC as the name, but we add multiple SAN names to it to validate other hosts internally, including our SQL servers and the SQL virtual name)
Originally I had tried using the Update database workflow but it kept giving me the java.sql.SQLException: I/O Error: Connection reset error. I restarted the orchestrator service and my existing database under Inventory -> SQL Plug-in disappeared. Now when I try to run the SQL workflow to Add a database, I keep getting the same java.sql.SQLException: I/O Error: Connection reset error message.
Any thoughts from the community? This should be pretty straightforward but it's giving me all kinds of heck.
Thanks,
Kevin