Issues loading Exact Online data daily into Power BI

[drx]

Since the migration from your former platform to your new platform, we have been experiencing regular problems with a number of datasets loading into Power BI. Over the last few months it has started to become unworkable, as the daily data loads keep failing. We then pull them manually into Power BI (using refresh dataset), and that works in about 50% of cases.

Immediately after the migration we also had this problem to an extreme extent, and reported it in this ticket:

Itgentmm007 Cannot get free slot on throttle ‘ThrottlingBasedOnLicense’ for cap group ‘lic:...’ after waiting 1,920 seconds

Power BI geeft sinds een week foutmeldingen op verschillende datasources. Waardoor de data niet wordt geladen en momenteel een deel van het facturatie proces stil ligt. Foutmelding Power BI Datasource: Fout in de gegevensbron: DataSource.Error: OData: Request failed: The underlying connection was closed: An unexpected error occurred on a receive… Microsoft.Data.Mashup.ErrorCode = 10122. DataSourceKind = OData. DataSourcePath = https://bridge-online.cloud/acme-exact-online/odata4/ExactOn…

Business data process:

Every day at 7am we retrieve the following Exact Online tables in Power BI for the dataset “Invoice data” from Invantive Cloud:

• SalesInvoiceLinesIncremental (filtered on invoicedate (last 15 days))
• AccountsIncremental (full table)
• ContactsIncremental (full table)
• GLAccounts (full table)

Load details PowerQuery for table:

Monitoring Invantive Cloud

In the Invantive Cloud monitoring log I can find the following data. See below.

Request ID	IP address	Status Code	Network size (b)	Start date (UTC)	End date (UTC)	Duration (ms)	Path	Node
0HNH7MEBR4E8S:00000001	::ffff:68.219.160.18	500	0	20-11-2025 07:50:18	20-11-2025 08:44:15	3.236.999	/<<>>/odata4/ExactOnlineREST.Incremental.SalesInvoiceLinesIncremental@eol	SPBA0401
0HNH7MEBR4E50:00000001	::ffff:68.219.160.18	500	708	20-11-2025 07:45:43	20-11-2025 08:13:43	1.680.318	/<<>>/odata4/ExactOnlineREST.Incremental.SalesInvoiceLinesIncremental@eol	SPBA0401
0HNH7MEBR4DI1:00000003	::ffff:68.219.160.18	500	0	20-11-2025 07:21:57	20-11-2025 08:06:20	2.663.430	/<<>>/odata4/ExactOnlineREST.Incremental.SalesInvoiceLinesIncremental@eol?$filter=Division%20eq%201483520%20and%20InvoiceDate%20ge%202025-11-05T00%3A00%3A00Z%20and%20Item%20ne%20null	SPBA0401
0HNH7MEBR4D8K:00000001	::ffff:68.219.160.18	500	0	20-11-2025 07:15:15	20-11-2025 07:44:37	1.761.651	/<<>>/odata4/ExactOnlineREST.Incremental.SalesInvoiceLinesIncremental@eol	SPBA0401
0HNH7MEBR4D10:00000001	::ffff:68.219.160.18	500	0	20-11-2025 07:10:40	20-11-2025 07:59:01	2.901.500	/<<>>/odata4/ExactOnlineREST.Incremental.SalesInvoiceLinesIncremental@eol	SPBA0401
0HNH7MEBR4C78:00000001	::ffff:68.219.160.18	500	708	20-11-2025 06:56:54	20-11-2025 07:51:51	3.296.716	/<<>>/odata4/ExactOnlineREST.Incremental.SalesInvoiceLinesIncremental@eol?$filter=Division%20eq%201483520%20and%20InvoiceDate%20ge%202025-11-05T00%3A00%3A00Z%20and%20Item%20ne%20null	SPBA0401
0HNH7MEBR4C4B:00000001	::ffff:68.219.160.18	500	0	20-11-2025 06:52:20	20-11-2025 07:37:31	2.710.831	/<<>>/odata4/ExactOnlineREST.Incremental.SalesInvoiceLinesIncremental@eol?$filter=Division%20eq%201483520%20and%20InvoiceDate%20ge%202025-11-05T00%3A00%3A00Z%20and%20Item%20ne%20null	SPBA0401
0HNH7MEBR4C3N:00000001	::ffff:68.219.160.18	500	708	20-11-2025 06:51:28	20-11-2025 07:22:52	1.883.770	/<<>>/odata4/ExactOnlineREST.Incremental.SalesInvoiceLinesIncremental@eol?$filter=Division%20eq%201483520%20and%20InvoiceDate%20ge%202025-11-05T00%3A00%3A00Z%20and%20Item%20ne%20null	SPBA0401
0HNH7MEBR4BTV:00000003	::ffff:68.219.160.18	500	0	20-11-2025 06:42:18	20-11-2025 07:08:32	1.573.665	/<<>>/odata4/ExactOnlineREST.Incremental.SalesInvoiceLinesIncremental@eol?$filter=Division%20eq%201483520%20and%20InvoiceDate%20ge%202025-11-05T00%3A00%3A00Z%20and%20Item%20ne%20null	SPBA0401
0HNH7MEBR4BJK:00000001	::ffff:68.219.160.18	500	0	20-11-2025 06:32:01	20-11-2025 07:01:24	1.763.265	/<<>>/odata4/ExactOnlineREST.Incremental.SalesInvoiceLinesIncremental@eol	SPBA0401
0HNH7MEBR4BH0:00000001	::ffff:68.219.160.18	500	0	20-11-2025 06:27:26	20-11-2025 06:47:06	1.180.668	/<<>>/odata4/ExactOnlineREST.Incremental.SalesInvoiceLinesIncremental@eol	SPBA0401
0HNH7MEBR4BB6:00000001	::ffff:68.219.160.18	500	0	20-11-2025 06:18:17	20-11-2025 06:54:24	2.167.549	/<<>>/odata4/ExactOnlineREST.Incremental.SalesInvoiceLinesIncremental@eol?$filter=Division%20eq%201483520%20and%20InvoiceDate%20ge%202025-11-05T00%3A00%3A00Z%20and%20Item%20ne%20null	SPBA0401
0HNH7MEBR4B6A:00000001	::ffff:68.219.160.18	500	708	20-11-2025 06:13:41	20-11-2025 06:40:13	1.591.364	/<<>>/odata4/ExactOnlineREST.Incremental.SalesInvoiceLinesIncremental@eol?$filter=Division%20eq%201483520%20and%20InvoiceDate%20ge%202025-11-05T00%3A00%3A00Z%20and%20Item%20ne%20null	SPBA0401
0HNH7MEBR4B48:00000001	::ffff:68.219.160.18	500	0	20-11-2025 06:12:49	20-11-2025 06:25:51	782,034	/<<>>/odata4/ExactOnlineREST.Incremental.SalesInvoiceLinesIncremental@eol?$filter=Division%20eq%201483520%20and%20InvoiceDate%20ge%202025-11-05T00%3A00%3A00Z%20and%20Item%20ne%20null	SPBA0401
0HNH7MEBR4AT9:00000001	::ffff:68.219.160.18	500	0	20-11-2025 06:08:14	20-11-2025 06:18:29	614,974	/<<>>/odata4/ExactOnlineREST.Incremental.SalesInvoiceLinesIncremental@eol?$filter=Division%20eq%201483520%20and%20InvoiceDate%20ge%202025-11-05T00%3A00%3A00Z%20and%20Item%20ne%20null	SPBA0401
0HNH7MEBR4AMC:0000000F	::ffff:68.219.160.18	500	0	20-11-2025 06:03:39	20-11-2025 06:11:04	444,405	/<<>>/odata4/ExactOnlineREST.Incremental.SalesInvoiceLinesIncremental@eol?$filter=Division%20eq%201483520%20and%20InvoiceDate%20ge%202025-11-05T00%3A00%3A00Z%20and%20Item%20ne%20null	SPBA0401

Errors from Power BI

The errors are reported for several Exact Online tables / Invantive Bridge endpoints that are queried within the Power BI dataset “Invoice data”. Two examples:

Other Power BI reports / data loads

We have dozens of datasets / reports active in Power BI based on the Exact Online data via Invantive Bridge. Only this dataset is currently experiencing issues on a daily basis. The other data loads run fairly smoothly, and are only refreshed on Monday mornings.

[forums]

Additional information

Is it possible to add a (anonymised) screenshot of the details of the request in Invantive Bridge Online Monitoring as described in Meer inzicht met nieuwe Online Monitoring?

You can find the details by clicking on the download request representing the subject of this topic.

The download request usually has an SQL statement in which the table name is visible.

Please keep at least the following information visible in both columns:

• the title bar with the request ID,
• the status code, network size, path and timestamps in the left-hand column,
• the error code and error message right at the bottom of the left-hand column,
• the entire right-hand column including the SQL statement, table name and parameter values.

For example:

Check the correct server and user

Please check carefully that you are logging in to the Bridge Online website that is also used from Power BI, and with the same username. You will only see the requests of the Invantive Cloud user with which you log in to the website.

Four servers are in use:

• bridge-online.cloud
• app-online.cloud
• bridge-online.invantive.com
• app-online.invantive.com

You can see which server is used in your script or the report’s source code.

Check the correct request and details

Make sure you select the request first so that the details are displayed. Only one request should be visible in the screenshot.

Also check carefully that the request has a path with odata4 or apps. Requests with other paths are generally not relevant for this purpose.

Error message and tips by email

In addition, the Invantive Cloud user who received the error message will usually receive an email at their email address with an error message and tips if there is an error in Power BI, Power Query, Azure Data Factory, Qlik or Tableau.

We advise checking the spam folder of the relevant user for such emails sent from support@invantive.com.

[drx]

Thank you for the response. Please see the requested information below:

Table: SalesInvoiceLinesIncremental
Message: itgeneor754
Text:

Could not acquire the lock for the incremental table based on service URL ‘/…’ within 1,830 seconds.
Please make sure that the other request with ID ‘0HNIO6CD07DTN:00000003’ holding the lock releases it.
Then try again.

[forums]

More explanation about itgeneor754 can be found in the answer to:

How to make Exact TransactionLines even more efficient?!

Het blijft maar niet lukken om 2 dagen van TransActionLines van Exact op te halen, wat doe ik verkeerd? let // Stap 1: Ophalen van de volledige dataset via de OData-feed Bron = OData.Feed("https://bridge-online.cloud/XXX-exact-online/odata4", null, \[Implementation="2.0", ODataVersion=4, OmitValues=ODataOmitValues.Nulls, Headers=\[Referer = "TransactionLines"\], Timeout=#duration(0,4,0,0)\]), // Stap 2: Verwijzen naar de specifieke tabel binnen de feed #"ExactOnlineREST.Incremental.…

[forums]

This question has been automatically closed after 1 week of inactivity. The last answer given has been marked as the solution.

If the problem occurs again, please ask a new question via a separate topic. Please include a link to this topic in the new question by pasting the URL of it into the text.