Forum Discussion

Anonymous's avatar
Anonymous
Not applicable
2 years ago

Getting Datasource Exceeded Limit while deploying PowerBI Report

I am getting the below error while deploying a Report in PowerBI. I checked the size of the dataset, the size does not exceed the 1.5 GB Limit. Can anyone please provide some suggestions?

 

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

3 Replies

  • Hi Anonymous 

     

    The PBIX size is when it is compressed, when it is actually loaded it is 3-4x larger.

  • Anonymous's avatar
    Anonymous
    Not applicable

    Hi, Anonymous 

    Thanks for the reply from GilbertQ , please allow me to provide addition:

    Check the complexity of your dataset, even if the dataset size is less than 1.5 GB, the complexity of your data (e.g., number of columns, relationships, and calculated columns) can sometimes cause problems.
    If you're using a service principal for authentication, there might be an issue with their permissions or configuration. Some users have reported that reconfiguring the service principal or using a different service principal solves this issue.
    If you're using the Power BI REST API, make sure you haven't reached any API limits. Sometimes, repeated API calls in a short period of time can trigger this error.
    If you're using an on-premises data gateway, check its configuration and make sure it's up to date. Sometimes, gateway issues can cause data movement errors. You can check the following link:

    Troubleshoot gateways - Power BI | Microsoft Learn

     

    How to Get Your Question Answered Quickly 

    Best Regards

    Yongkang Hua

    If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

  • Anonymous's avatar
    Anonymous
    Not applicable

    Hi Anonymous , were you able to resolve this? We have ran into same issue, the application was running for a year without any issue and suddenly we have started encountering this issue.