Skip to main content
To homepage To homepage
Solved

Error when retrieving data

  • February 3, 2023
  • 5 replies
  • 336 views
R
Starter
Forum|alt.badge.img

Hello,

I’m using the CData ADO.NET Provider for JSON 2021 and get this error message in the logg file.

[HTTP|Res: 29] HTTP/1.1 200 OK, 548950 Bytes Transferred
[HTTP|Res: 29] Request completed in 6828 ms.
[EXEC|Page  ] Page successful: 1000 results (6844 ms) NextPage: [30000]
[EXEC|Messag] Executed query: [SELECT [Actualizations_id], [ActualizationType.Code],
[META|Schema] Engine Invalid object name 'sys_resultset_close'
[MDUL|SbMDUL] Drop BulkRows table:ErrorInfo
[INFO|Connec] Executed sys_disconnect: Success: (16 ms)
[INFO|Connec] Closed JSON connection

 

The execution log file reports:

Executing table [JSON].[LCSOC_EC_Actualizations]:
failed with error:
System.Data.SqlClient.SqlException (0x80131904): Execution Timeout Expired.  The timeout period elapsed prior to completion of the operation or the server is not responding. ---> System.ComponentModel.Win32Exception (0x80004005): The wait operation timed out

 

What does it mean and what to do about it?

Cheers

/Reith
 

Best answer by Christian Hauggaard

Hi @reiols are you using ODX or Business Unit?

If using Business Unit you can try editing the Staging Database for the BU and increase the timeout settings.

In terms of the JSON CData provider, if you select advanced settings, you should also be able to increase concurrent execution threads as well as the command timeout here.

For more information, please see the below guide on timeouts

 

View original
Did this topic help you find an answer to your question?

5 replies

S
Contributor
Forum|alt.badge.img+3
  • Syed Yousuf
  • Contributor
  • 82 replies
  • February 3, 2023

https://cdn.cdata.com/help/DJF/ado/pg_jsonadvancedconnection.htm

and 

https://cdn.cdata.com/help/DJF/ado/RSBJSON_p_Timeout.htm

  • Queries time out: A server that takes too long to respond will exceed the provider's client-side timeout. Often, setting the Timeout property to a higher value will avoid a connection error. Another option is to disable the timeout by setting the property to 0. Setting Verbosity to 2 will show where the time is being spent.
R
Starter
Forum|alt.badge.img
  • reiols
  • Author
  • Starter
  • 2 replies
  • February 5, 2023

Thanx for the links, the verbosity setting was really helpful.

I disabled the timeout, but got this error in the execution log:

System.Data.SqlClient.SqlException (0x80131904): Execution Timeout Expired.  The timeout period elapsed prior to completion of the operation or the server is not responding. ---> System.ComponentModel.Win32Exception (0x80004005): The wait operation timed out

 

Now it says “The wait operation timed out” is there another parameter to set?

/Reith

Christian Hauggaard
Community Manager
Forum|alt.badge.img+5

Hi @reiols are you using ODX or Business Unit?

If using Business Unit you can try editing the Staging Database for the BU and increase the timeout settings.

In terms of the JSON CData provider, if you select advanced settings, you should also be able to increase concurrent execution threads as well as the command timeout here.

For more information, please see the below guide on timeouts

 

R
1 person likes this
  • R
    reiols
R
Starter
Forum|alt.badge.img
  • reiols
  • Author
  • Starter
  • 2 replies
  • February 7, 2023

Hi @Christian Hauggaard 

I tweaked the settings on the ODX instance.

Increased the “Command timeout” and decreased the “BatchSize”

This was exactly what I was looking for, so the answer/link was most helpful.

Thank you

/Reith

Christian Hauggaard
Community Manager
Forum|alt.badge.img+5

@reiols Great! Glad that it’s resolved! 

Can you please help us by marking a best answer above?\

Reply


Terms and ConditionsCookie settings

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings