Itgenboe313: Error at fetching data from Qlik from Exact Online in Germany

[4hf1]

Unfortunately I am getting an error by fetching data from Exact. Here I try to get the ExactOnlineREST_Cashflow_Receivables_eol table.

In Qlik I get after an hour a timeout error, on the other hand in Invantive Bridge Online Monitoring I get an error after 10 minutes (see screenshots below). So in Qlik I have a job to fetch the data, after 10 minutes in Invantive Bridge Online I am getting an error, but the job in Qlik still runs. After an hour I am getting a timeout in Qlik.

Here the screenshots:

The following error occurred:
Internal error. (Connector error: Failed on attempt 1 to GET. (The operation has timed out.))
The engine error code: Connector error:22013
The error occurred here:
SELECT *
      FROM JsonV4GetData
      WITH PROPERTIES (
        oDataResourcePath='ExactOnlineREST_Cashflow_Receivables_eol',
        oDataQueryOptions='',
        maxDepth='',
        maxResult=''
      )

itgenboe313
Das Herunterladen der Daten wurde nach 9 Minuten, 0 Sekunden abgebrochen, z. B. indem der Benutzer in einem Browssre wegnavigierte.

[4hf1]

Maybe that helps:

I also fetch the data via postman and here I get the data after 7 minutes.

[forums]

Typically a itgenboe313 indicates that the download client disconnected, but the numbers seem strange.

Increase Time-out

You might want to extend the timeout as described in Avoid timeout error on Power BI OData download.

Test using Curl

To factor out Qlik as a cause, please try to run the download using curl as described in:

How do I use curl to execute an Invantive Cloud OData4 request?

Go to Dutch version Some issues are specifically tied to Power BI Desktop, Excel or powerbi.com. Therefore, you may be asked to perform a download also via the program curl. Curl comes standard with Microsoft Windows PCs and MacOS. This topic explains how to reproduce a download using curl. Preparations The first step is to retrieve the hyperlink of the download you want to reproduce in Bridge Online Monitoring. First, search the list for the request in question for you; usually this is a req…

Possibly related: Germany

But given the German text and 7 minutes on a single API call from Postman to Exact Online it may also relate to a seemingly common problem in Exact Online Germany environments, where time-outs occur. You might want to check the screen Session I/Os for response times of API calls. They should all be below 10 seconds, and typically way below 1 second for this specific table.

In case there are larger response times, it is recommended to reach out to Exact Online Support. Their formal stance is that there are no guarantees on response times on the API, but in practice they also know that when such problems occur ultimately the customer will leave the Exact platform.

[forums]

This question was automatically closed after at least 1 week of inactivity after a possible solution was provided. The last answer given has been marked as a solution.

Please ask a new question via a separate topic if the problem occurs again. Please include a link to this topic in the new question by pasting its URL into the text.