SQL Server Connection Failures After Upgrading to Applications Manager 9.6

Products

• Automic Applications Manager

Issue/Introduction

After upgrading Applications Manager to version 9.6 or above, SQL Server connections may fail if the SQL Job use a %net_connect% variable to resolve to it's SQL Login object's Network alias field value.

Environment

• Applications Manager 9.6.0 and higher
• Java 17 or 21
• SQL Server

Cause

Java 17 and 21 introduce enhanced security requirements for SSL connections. Additionally, configuration changes in the login object (specifically the replacement of "Network Alias" with "Additional Parameters") may cause issues if scripts rely on deprecated variables like %net_connect%.

Resolution

1. Configure Additional Parameters: Edit the SQL Server Login object and add the following to the Additional Parameters field:

   • If "Force Encryption" is enabled on the SQL Server: encrypt=true;trustServerCertificate=true;
   • If "Force Encryption" is disabled: encrypt=false;trustServerCertificate=true;
   • Values required may differ per SQL Server configuration

2. Define Custom Environment Variable (If Scripting Errors Occur): If your scripts rely on the %net_connect% variable to retrieve host information, you must create a custom variable:

   • Navigate to Object Admin > Development > Environment Variable > New.
   • Define a new variable for your database host.
   • Assign this variable to the relevant Agents, Applications, or Jobs.
   • Update your execution scripts (e.g., TSQLP.bat) to reference this new environment variable instead of the legacy %net_connect%.

Additional Information

• For documentation on defining environment variables, see: Applications Manager Documentation.
• To speak with a Support Engineer, see Contact Support. Scroll to the bottom of the page and click on your respective region.