DMTS_OAuthFailedToGetResourceIdError (English translation needed)

[dbeavon3]

Can someone please share an English translation for this error message?

DMTS_OAuthFailedToGetResourceIdError

Here is the full error:
"error":{"code":"DMTS_OAuthFailedToGetResourceIdError","pbi.error":{"code":"DMTS_OAuthFailedToGetResourceIdError","parameters":{},"details":[],"exceptionCulprit":1}}} Table: Branch Data

There are lots of google results in this community, but I haven't seen a translation of this message into English.  It looks like Greek or Latin to me.

FYI, The failures started on Saturday in the Azure east region, when there was a massive SQL Server outage.  The outage lasted almost all day from 6 AM to 3 PM.  Ever since the outage, we have not been able to get our datasets to refresh.  One complicating factor is that our refresh operations are happening by way of the "azure-managed-vnet-gateway", and I'm not sure if this component is running the latest version of the gateway software.  It may be encountering a bug that doesn't happen in a recent release of the gateway.

Based on my google searches, it appears that other customers have been encountering this since March.  I don't think this type of failure existed prior to 2023.  I wish the PG would invest some time into fixing this bug, or at least improving the message that is displayed whenever the bug is encountered.

[dbeavon3]

Here is another brief follow-up related to the error message which is presented in Latin ("DMTS_OAuthFailedToGetResourceIdError").

The PG shared more information.  They will not share any explanation about the "DMTS" service component.  But they did say the OAuth bugs occur when transitioning from a PBI refresh token to a SQL Server access token.  Here is the new language/explanation from the PG: 


“For AAD SSO, the PBI internal service (DMTS) needs to obtain a OAuth resource ID (the resource is the sql server) in order to perform token exchange from a PBI user token to the SQL Server user token. This step is only performed if the dataset is configured for AAD SSO.”

I wish some of this explanation from the PG was provided in the error message itself.   (It would allow customers to independently disable the SSO, perhaps).  I also wish I was able to understand why it takes a full week to resolve an issue like this!  Hopefully they will not have week-long outages after the gateway becomes GA in January.

[dbeavon3]

Here is the RCA for the SQL outage.  I don't have a similar RCA yet for my ongoing Power BI outage.
I will attempt to work with CSS as well.  But in the meantime it would help if anyone can translate this PBI error into English for us.  These datasets have not refreshed for many days!

[dbeavon3 · Accepted solution]

I have reached the end of the CSS case now as well.  It turns out that a refresh token wasn't being renewed, possibly due to the SQL outage.

Based on the communication with the Power BI engineers, the error  ... ("DMTS_OAuthFailedToGetResourceIdError") ... almost always appears to be due to a bug.  The bug may be most severe in cases where the data source uses SSO features.  So you may want to turn off any fancy / flakey features if you want to avoid the OAuth bugs.

As far as my attempt to get a translation of that error message, none is forthcoming.  I'm guessing the reason is because it is almost always related to internal bugs, and it was never supposed to have been bubbled out or become visible to customers.  I'm still pretty sure that "DMTS" means data management token service, and I'd guess it represents some sort of software component like a fragile micro-service of some kind.

In my case the error was happening in an azure-managed-vnet-gateway but it would not surprise me if similar bugs exist within the on-premise gateway as well.  Here is a CSS explanation of the bug that was occuring in my azure gateway.  This caused an extended outage that lasted for a full week!

"we have checked internally for the Root cause of the issue and found that there was a bug where an s2s token is not being passed when creating a VNet gateway client for discovering the Oauth Resources and also the Refresh token was not getting renewed due to which this issue has occurred.

This prevents customers from refreshing their reports that point to a VNet gateway."