CONN.SQL inconsistent connectivity between environments

[timjcw32767]

I am looking for reasons why I get inconsistent connectivity results when using the same CONN.SQL values in different Automation Engine environments. For example, I can create a successful connection to database server ABC and database def in my DEV environment, but the same CONN fails in all the rest.

I have a /bin/jdbc folder with a version of mssql-jdbc-12.8.1.jre11.jar for every SQL agent.

I am required to use Windows logins ie uafp_domain/jdoe

I have tired variations of this string for the database field in the CONN:  def;integratedSecurity=true;encrypt=true;trustServerCertificate=true

I can use the IP address, the alias or the database server name and get the same results.

I've also noticed that some environments don't read the alternative login (when the LOGIN is blank) and attempt to connect with the environment's service account.

I'm using V21.13

[Olgun Onur Ozmen]

you must to try some jdbc jar and auth dll combination in jdbc or main bin folder.

------------------------------
Olgun Onur Ozmen
https://www.linkedin.com/in/olgunonurozmen/
------------------------------

[timjcw32767]

I have the same ...\bin\jdbc\mssql-jdbc-12.8.1.jre11.jar and ...\bin\jdbc\mssql-jdbc-12.8.1.jre11.jar in every environment.

[timjcw32767]

To add, what it looks like is that unless the LOGIN or alternative login has a sql user, the CONN uses the service account which starts Service Manager.  This seems limiting in capabilities.