Itgenboe562: Invalid credentials and error 500

I have a problem with updating the data in Power Bi.

First it shows that credentials are invalid. I checked the paths and both link matches (from Invantive website and Power BI).

I’ve changed the log in method by signing in with Invantive log in and password, without any success.

It shows error 500 now:

Microsoft.Mashup.Engine1.Library.Resources.HttpResource:
Request failed:
OData Version: 3 and 4,
Error: The remote server returned an error: (500) Internal Server Error.

My colleagues have no issue with accessing the data. My account is freshly opened, is it possible I’m missing some setting on my side?

Supplementary Information

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

You can find the details by clicking on the download request which is the subject of this issue.

The download request usually contains a SQL statement in which the table name is visible.

Please ensure at least the following information is visible from both columns:

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

For example:

Check Correct Server and User

Carefully check that you log into the Invantive Cloud website with the same username you use to process data via, for example, Invantive Bridge Online. You only see the requests of the Invantive Cloud user with which you log into the website.

Check Correct Request and Details

Ensure that you first select the request to display the details. There should only be one request visible in the screenshot.

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

Error Message and Tips via Email

Additionally, the Invantive Cloud user who encountered the error message will usually receive an email with an error message and tips if there is an error message in Power BI, Power Query, Azure Data Factory, Qlik, or Tableau.

It is advisable to check the spam of the involved user for such emails sent from support@invantive.eu.

The advice is to use the screenshot showing the error message as described under “Check correct request”:

So I’ve tried to look for the log you are requesting but it seems I cannot find it. The only one that looks like it’s related to Power BI could be this?

I’ve never used this kind of software before, and I’m bit lost.

itgeneor562
eol: Toegang tot de OAuth-gegevensbron vereist een geldig access token.
Het access token kon niet worden verkregen.
De Exact Online gebruiker is niet actief.

The error code itgeneor562 appears if all is well except for a few hints. Check these or use:

The advice is to follow the steps described there to transfer the environment to an existing Exact Online user.

I don’t have the “Refresh Authorization” button that is mentioned in that article.


This is how I access "Refresh Authorization”, but it still doesn’t work. Could you please advice what should be the next step?

Callback URI ‘Log on’ is not valid.

Screenshot 2026-09-30 145935

itgeneor562
eol
Access to the OAuth data source requires a valid access token.
The access token could not be acquired.
The Exact Online user is not active.

The “Refresh Authorisations” button is located on the data container, not on the database.

The error message occurs because the authorisation is done from the URL https://cloud.invantive.com.

Invantive is working on replacing the domain invantive.com with invantive.eu. Unfortunately, on some platforms, it is not possible to use multiple so-called Redirect URLs.

We are still working on improving this process so that users experience less of an impact.

The advice is to change the URL under “Choose App” from invantive.com to invantive.eu. You may need to log in again.

Afterwards, the refresh of the authorisations will work.