Itgenclr009 error opening UniversalSQL editor

Our Power BI connections stopped working since January 7, 2026. While investigating the issue we noticed that accessing the UniversalSQL Editor from Invantive also does not work. We get an error while accessing the Editor:

Invantive Cloud: 25.0.147
Erroritgenclr009
Something went wrong.
Natural Key: 8CAB3D
Request ID: 0HNII51C2NFNH:00000009
7e48d0db-a026-4d7b-8c9d-e9c8c25aab4e

We tried searching the forum but found no (recent) posts related to this. Also we tried disabling our data containers but even with al data containers disabled the editor does not load.

From our Power BI it looks like the error is simplicate related but we can not confirm that using the UniversalSQL Editor.

We’d like to receive more information to get to the cause of this issue and fix this.

Topics are restrained to a single element. It is recommended to post the Power BI problem (with details from Monitoring) in a linked topic. The response will be on the itgenclr009 error.

itgenclr009 is actually a representation of a so-called ArgumentException. This can also be found in the form “System Messages”, which provides more technical details on such system level errors.

It is caused by an error on HubSpot, which leads to multiple objects with the same name being found.

An initial analysis revealed that the error related to HubSpot recording settings (CRM calling extensions) on data container hubspot/7481203, triggered during determination of the list of available objects.

An analyst will look into this issue and try to reproduce it outside without access to your environment.

As a workaround, it is recommended to split off HubSpot to a separate database. The HubSpot driver is not often used, but also the HubSpot release policies make it a challenging platform to maintain the level of stability we aim to provide and add.

Thank you for the quick response and the pointers. After disabling HubSpot we are fine (for now).

A number of changes have been included in release 25.0.205, scheduled to go live on the night of February 26 to 27.

Did these solve all HubSpot issues?

If not, can you include the error message?

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.

Dit topic is 3 dagen na het laatste antwoord automatisch gesloten. Nieuwe antwoorden zijn niet meer toegestaan.