Invantive Cloud Power BI error: itgenboe072

Questions (nl)
, ,
1

Since last night, the Power BI datasets are no longer loading from Invantive Bridge Online. Are there no notifications visible in the Invantive Cloud log?

There have been no logbook entries since yesterday afternoon.

Power BI notification:

Error in data source: DataSource.Error: Microsoft.Mashup.Engine1.Library.Resources.HttpResource: 
Request failed: 
OData Version: 3 and 4, Error: 
The remote server returned an error: (500) Internal Server Error. 
(An internal error has occurred. 
Please contact your provider. (itgenboe072, 9b50efff-c961-460e-9c8d-ad7457e5de7c))
Microsoft.Data.Mashup.ErrorCode = 10122. 
Microsoft.Data.Mashup.ValueError.DataSourceKind = OData. 
DataSourcePath = https://bridge-online.invantive.com/acme-exact-online/odata4. . 
The exception was raised by the IDbCommand interface.
URI cluster: WABI-WEST-EUROPE-E-PRIMARY-redirect.analysis.windows.net
Time: 2026-05-31 10:04:22Z
2

The underlying error message can be found in the System Messages screen:

itgenboe072:
The user startup SQL statements of the database raised an internal error itgenbed003.
Please contact Invantive.
(acme-exact-online-2)
—> Invantive.Basics.InvantiveSystemException:
itgenbed003:
An element with the key ‘2354550’ already exists in a dictionary of String and Partition.
(itgenpcn007)
—> System.ArgumentException:
An item with the same key has already been added.
Key: 2354550

The advice is to follow up on this issue via Systeemfout itgenbed003: UniversalSQL-editor - Database Exact Online.

3

A bug fix has been implemented and deployed into production on Invantive Cloud.

The root cause found is that the Exact Online driver also contains a module for Exact Online Premium, as described in Beperk toegang tot specifieke administraties op de Exact Online Premium-database op SQL Server. We are currently not allowed to make this available, but the module is running (inactive).

Recent adjustments had not been applied to the Exact Online Premium component. This has been corrected. This also explains why only some users were affected; it only concerned users of Exact Online Premium. Exact Online SaaS users were not affected because the module cannot run.

More information can be found at:

4

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

Please ask a new question in a separate topic if the issue occurs again. In the new question, please include a link to this topic by pasting its URL in the text.