Solved

ADF - PostGreSQL 'queryTimeout' error

  • 29 January 2024
  • 2 replies
  • 44 views

Userlevel 2
Badge +1

We are using the Azure Data Factory - PostgreSQL 14.0.0.0 data source connector and cannot run the synchronize task. We have selected ‘All tables’ in the data source setup but get an error in ADF:

“Failure happened on 'Source' side. ErrorCode=UserErrorInvalidValueInPayload,'Type=Microsoft.DataTransfer.Common.Shared.HybridDeliveryException,Message=Failed to convert the value in 'queryTimeout' property to 'System.TimeSpan' type. Please make sure the payload structure and value are correct.,Source=Microsoft.DataTransfer.DataContracts,''Type=System.ArgumentException,Message=Object of type 'System.Int64' cannot be converted to type 'System.String'.,Source=mscorlib”

The error seems to be related to the ‘Command timeout’ setting in the TX portal, which we set to 1440 but ADF wants it to be a ‘System.TimeSpan’ type?

When we want to use ‘Select tables’ on the ODX data source the screen runs ‘Search tables’ for a split second and then the results remain empty, no tables appear at all.

The Linked Service in ADF works fine, Test Connection is OK. We are using an Azure Integrated Runtime in ‘West Europe’ for extracting the data which should not give errors.

How can we proceed? We are on TX version 6521.1 by the way.

Best regards,

Kaj

icon

Best answer by Christian Hauggaard 30 January 2024, 11:58

View original

2 replies

Userlevel 6
Badge +5

Hi @KajEmergo 

I am not able to reproduce the issue you describe, I am also using 6521.1 please see my settings below

Do you notice anything different in our setups?

Did you set up the data source connection in 14.0.0.0, or did you upgrade from an older version of the provider?

I did initially got this error when trying to setup the data source connection in 14.0.0.0, however it did not complain after I changed it manually and then saved and then edited the data source connection again and set the command timeout to 1440. Can you please try changing the value and refreshing TimeXtender and then execute the sync task?  

 

Userlevel 2
Badge +1

@Christian Hauggaard, to my knowledge we initially did the setup in 14.0.0.0 but I am not completely sure. I see you get the message in the TX portal, but we never got it there. Only on executing the transfer task in ODX.

I currently do not have access to the machine on which TX is running, that will be the next time when I work on site (probably in 1.5 weeks). Anyways, we got the sync task working by adjusting the settings in the ADF pipeline json format manually:

 

Next time we will try to configure the data source in the TX portal from scratch again and see if we get the message you got in the portal as well.

For now, the issue is mitigated!

Best,

Kaj

Reply