Azure ADLS Connection Failure: Qlik Replicate

[zwatkinscovermymeds]

Trying to connect to our data lake using the adls connection.

Getting this error when trying to browse the file system:

• SYS-E-HTTPFAIL, Failed to browse storage.
• SYS,GENERAL_EXCEPTION,Failed to browse storage,JAVA_EXCEPTION, message: 'io.swagger.client.ApiException: java.net.ConnectException: Failed to connect to dssanalyticsprodhotsa.dfs.core.windows.net/10.5.64.67:443'

Working with our Azure expert and configurations are correct on that side. "test connection" also results in an error:

• SYS-E-HTTPFAIL, Failed to connect to Data lake store name 'dssanalyticsprodhotsa'..
• SYS,GENERAL_EXCEPTION,Failed to connect to Data lake store name 'dssanalyticsprodhotsa'.,JAVA_EXCEPTION, message: 'io.swagger.client.ApiException: java.net.ConnectException: Failed to connect to dssanalyticsprodhotsa.dfs.core.windows.net/10.5.64.67:443'

We are running replicate version 7.0.0.470

[tusharkaple]

HI @SushilKumar 

I tried by applying below  parameter but it didnt help in our case.

additionalConnectionProperties : SocketTimeout=180

Thanks,

Tushar

[tusharkaple]

Is anyone have any idea on this?

[Dana_Baldwin]

Hi @tusharkaple 

Has your network team looked into these occurrences?

There are two internal parameters that can extend timeouts, but they are more of a work around than resolving the root cause:

executeTimeout

loadTimeout

Increase the default values to 3x or 4x then stop and resume the tasks that use this endpoint so the new values take effect.

For more detailed examination of the issue, you might consider opening a support case.

Thanks,

Dana

[tusharkaple]

Hi @Dana_Baldwin ,

Thanks for checking.

We are already having executeTimeout and loadTimeout.

Also, we had connected with Microsoft support team (Storage and network team), Our internal firewall team. But they are saying there is no issue from firewall end.

The problem we are observing is, the connection will working, but intermittently it will break and cause task failure. 

Thanks,

Dana

[Dana_Baldwin]

Hi @tusharkaple 

Far as I can tell, the issue is something in the environment. You may need a packet sniffer running when the issue happens to gather more information.

You are welcome to open a support case if you would like us to look for more information in the logs, but it does not appear to be an application issue.

Thanks,

Dana

[Kohila]

@tusharkaple  - Can you please confirm if this parameter help with the Qlik job failure. We are facing the same issue and receiving below error.

00006536: 2025-11-21T15:49:20 [AT_GLOBAL ]E: JAVA_EXCEPTION, message: 'java.util.concurrent.CompletionException: com.microsoft.aad.msal4j.MsalClientException: java.net.ConnectException: Connection timed out: connect' [1002905] (at_jni.c:787)
00008936: 2025-11-21T15:49:20 [AT_GLOBAL ]E: JAVA_EXCEPTION, message: 'java.util.concurrent.CompletionException: com.microsoft.aad.msal4j.MsalClientException: java.net.ConnectException: Connection timed out: connect' [1002905] (at_jni.c:787)
00006536: 2025-11-21T15:49:20 [TARGET_APPLY ]E: Failed to check staging path '/data/qlikrep_prod_staging/'. [1020401] (databricks_delta_imp.c:759)
00008936: 2025-11-21T15:49:20 [TARGET_APPLY ]E: Failed to check staging path '/data/qlikrep_prod_staging/'

Thanks,

Kohila

[Kohila]

@tusharkaple  - Could you please update the resolution for the issue if it has been fixed from your end?

Thanks,

Kohila