DMTS_PowerBIDataMovementUserDatasourceExceededLimit error importing or taking over dataset

[pdudek-medius]

Hi,

I'm working on a project which involves Power BI reports being embedded in web application for our customers. This involves using Power BI REST API to import datasets after changes and refreshing data daily. The solution already works in production for almost 4 years, but recently we started getting 400 bad requests with

DMTS_PowerBIDataMovementUserDatasourceExceededLimit

error code when authenticating via service principal (app registration). After we start getting this error service principal seems to get "broken" and every import or take over action returns this error. Below are full responses for respective APIs:

Datasets - Take Over In Group - REST API (Power BI Power BI REST APIs) | Microsoft Learn

{"error":{"code":"DMTS_PowerBIDataMovementUserDatasourceExceededLimit","pbi.error":{"code":"DMTS_PowerBIDataMovementUserDatasourceExceededLimit","parameters":{},"details":[],"exceptionCulprit":1}}}

 Imports - Get Import In Group - REST API (Power BI Power BI REST APIs) | Microsoft Learn

{
  "@odata.context":"https://wabi-north-europe-f-primary-redirect.analysis.windows.net/v1.0/myorg/groups/<guid>/$metadata#imports/$entity","id":"guid","importState":"Failed","createdDateTime":"2024-08-05T09:33:07.807Z","updatedDateTime":"2024-08-05T09:33:07.807Z","error":{
    "code":"DMTS_PowerBIDataMovementUserDatasourceExceededLimit","details":[
      
    ]
  },"name":"name.pbix","connectionType":"import","source":"Upload","datasets":[
    
  ],"reports":[
    
  ],"dataflows":[
    
  ]
}

The error code suggests that some limits have been exceeded, but I cannot find information on exactly what this limit is and how to avoid exceeding it. Has anyone encountered it?

[ShubhamKapadnis]

@pdudek-medius Were you able to find solution for this problem? we have run into similar issue where the application was running fine for 3 years we started seeing this error since last week.
Any help would be appreciated, also note the datsets we use is pretty small, mostly in few mbs and we had regression suite which was running the reports with test data daily but nothing is working anymore

[pdudek-medius]

@ShubhamKapadnis Unfortunately not, so far we switch the service principal to new one if the current one breaks as workaround, but still looking for resolution of the issue.

[ShubhamKapadnis]

Hi @pdudek-medius , so we were able to find the root cause of the issue.

This error occurs when no of datasources per SPN crosss a certain limit, we were told the limit is1k, but for us reaching the no sources to 6.5k caused the problem and getting the no below 5k resumed the service operation.

So i guess the solution you are using is the alternative to this issue, also there is something called SPN profiles i think that can be used.

For us we were good to just delete the Datasources. So we just deleted old datasources associated with SPN.

[nandic]

@pdudek-medius 
What is the size of datasets? We had issues downloading datasets and then we found out that max allowed size is 1GB per dataset to be downloaded via REST API.

Does the process returns error each time or randomly?

Cheers,
Nemanja Andic

[pdudek-medius]

Hi @nandic, thanks for reply

We have separate datasets for our ~500 customers (for tenant data separation reasons) and sizes vary quite a lot, the smallest being 1 MB and the largest 1.5 GB. But we don't download any datasets via REST API.

Failure happens at some point during our daily job that triggers refresh for all of the datasets via REST API. As part of refresh preparation we used to update dataset parameters and proceeded with take over, so service principal is able to update parameters and data source credentials. Takeover seems to trigger this error, once it happens for single dataset, all further takeover and import REST API using the specific service principal for which that happens fails with above error. This failure happens both for small and large datasets, so far we haven't seen a pattern linking it to dataset size at all.

We were able to limit number of takeover actions in our jobs plus created additional service principals as backup, which helped so far, but I would like to understand what that error is about and what triggers it.