Azure SQL connection works in TEST, fails in PROD env

[martinkaru]

We're loading data in batches from an on-premise Oracle DB to a cloud Azure SQL DB.
2 environments: TEST and PROD.
Both have the same connection to the Azure SQL DB (same service account, same url, same DB even).

In PROD, after stopping the task, it will not start again.
In TEST, the task can start. Tested with other sources as well.

When we start the task in PROD, it gets an error:
Failed while preparing stream component 'target-xx-prod'.
[ODBC Driver 18 for SQL Server] TCP Provider: An existing connection was forcibly closed by the remote host.

"Test connection" works in both PROD and TEST.
The service account can also BROWSE the databases (in the endpoint setup view).

PROD VM can connect to the DB directly (via PowerShell) and run the SQL.

What's the probable cause (driver? authentication?)?
We changed the certificates in both PROD and TEST. I'm rather certain that PROD Qlik Service hasn't been restarted afterwards.

[john_wang]

Hello @martinkaru ,

Thanks for reaching out to Qlik Community!

Let's compare the 2 environments to see if any settings caused the difference:

1. Export the task to JSON file and compare the 2 files (or download the task Diagnostics Packages then compare the two tasks JSON file definition)

         

2. Set TARGET_APPLY & TARGET_LOAD to Verbose in the 2 tasks, run them and then compare the two task log files to understand why the behavior is different.

       

3. If you still need help, please open the support ticket and attach the above information/files, Support Team would like to help on further investigations.

Regards,

John.