Error during update

[Jc_madrid]

Hello everyone, I hope you're having a good day. I'm having a problem updating the dashboard in Power BI Web. The error in question is:
Error del origen de datos: {"error":{"code":"DMTS_OAuthTokenRefreshFailedError","pbi.error":{"code":"DMTS_OAuthTokenRefreshFailedError","details":[{"code":"DM_ErrorDetailNameCode_UnderlyingErrorMessage","detail":{"type":1,"value":"Exception of type 'Microsoft.Mashup.Engine.Interface.ResourceAccessForbiddenException' was thrown."}}],"exceptionCulprit":1}}}
URI de clúster: WABI-WEST-EUROPE-D-PRIMARY-redirect.analysis.windows.net
Identificador de actividad: 2a6fc96e-2d31-4874-99db-d7976fda4ea1
Identificador de la solicitud: 7cbbc082-95fb-165f-6dc8-e60b194e10cf
Hora: 2025-12-03 12:06:50Z

The API gateway was reinstalled, and it is currently being added. The dashboard already existed, but there was a change in the accounts, so the API gateway had to be redone. However, it is not updating now. I already changed the access within the data sources, but it still does not work.
Thank you in advance for any response.

[v-saisrao-msft]

Hi @Jc_madrid,

Checking in to see if your issue has been resolved. let us know if you still need any assistance.

Thank you.

[v-saisrao-msft]

Hi @Jc_madrid,

Have you had a chance to review the solution we shared by @rohit1991 @Zanqueta @Anonymous ? If the issue persists, feel free to reply so we can help further.

Thank you.

[Anonymous]

Hi @Jc_madrid ,

Try below steps.

1. Take ownership of the dataset

If the dataset was created under a different account, use “Take over” in the dataset settings.

This ensures the refresh token is regenerated under your account.

2. Check gateway mapping

In Manage Gateways, confirm that the new gateway is online and mapped to the dataset.

Re‑add the data source in the gateway with the correct credentials.

Ensure the dataset is pointing to the correct gateway cluster.

3. Verify permissions

Confirm the new account has access to the underlying data source (SharePoint, SQL, API, etc.).

If the error persists, check whether the resource itself is blocking access (e.g., disabled device or revoked permissions).

4. Refresh manually

After updating credentials and gateway mapping, try a manual refresh in Power BI Service.

If successful, scheduled refreshes should resume.

Refer community thread.

https://community.fabric.microsoft.com/t5/Service/DMTS-OAuthTokenRefreshFailedError/m-p/2704341

If my response as resolved your issue please mark it as solution and give kudos.

[Zanqueta]

Hi @Jc_madrid,

Just to contributet in discussion: Can you successfully connect to the same data source in Power BI Desktop using the same credentials? If not, the issue may be with permissions or authentication at the source level rather than the gateway.

Please follow the steps mentioned by @rohit1991 

If your data source is a cloud service such as SharePoint Online or OneDrive, you do not need an on-premises gateway. These sources use direct cloud-to-cloud connections. In such cases, the error is almost always due to expired or invalid OAuth credentials. Re-authenticating in Dataset Settings should resolve the issue.

If this response was helpful in any way, I’d gladly accept a 👍much like the joy of seeing a DAX measure work first time without needing another FILTER.

Please mark it as the correct solution. It helps other community members find their way faster (and saves them from another endless loop 🌀.

[rohit1991 · Accepted solution]

Hii @Jc_madrid 

This error means the gateway is using old/invalid OAuth credentials, so Power BI Service cannot get a new token.
When you reinstalled or changed accounts on the gateway, the data source credentials in Power BI were not fully updated.

Fix:

1. Go to Power BI Service >> Settings >> Gateway >> Manage Connections.

2. Edit each data source and re-enter the credentials using the same account the gateway now runs under.

3. Also go to Dataset >> Settings >> Data source credentials and re-authenticate every connection.

4. Save >> Refresh again.

Once both are updated with the same valid OAuth account, the refresh will work again.