Forum Discussion

lawrenceabith's avatar
lawrenceabith
Helper IV
2 years ago
Solved

Fabric Capacity F8 - Underlying Error: Capacity operation failed with error code CapacityLimitExceed

Dear,

 

We have a Fabric Capacity F8, and now we receive this error in all my reports. When I change to F64, for example, the error stops. Do you know how to solve this? I think this is an error. Can you help me? 

 

Cannot load model due to reaching capacity limits

The report cannot be opened because its workspace is assigned to a Power BI capacity that doesn't have enough resources. Please try again later and contact a capacity administrator to provision the required resources.

Please check the technical details for more information. If you contact support, please provide these details.

 

Underlying Error: Capacity operation failed with error code CapacityLimitExceeded

Activity ID: 195ba88123123123123

Correlation ID: 66627e123123123123

Request ID: 24b9a7a12312312312312

Time: Wed Nov 01 2023 09:03:42 GMT-0300 (Brasilia Standard Time)

Service version: 13.0.21891.85

Client version: 2310.4.16370-train

Cluster URI: https://wabi-south-central-us-redirect.analysis.windows.net/

 

Many thanks,

  • Anonymous's avatar
    Anonymous
    2 years ago

    Hi  lawrenceabith ,

     

    We have seen on the internal platform that other engineers have reported this issue and submitted it.
    The engineers on the product team are now aware and will do their best to resolve the issue. I will update here if there is any progress, so please be patient.

     

    Best Regards,

    Liu Yang

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

21 Replies

  • Anonymous's avatar
    Anonymous
    Not applicable

    Hi  lawrenceabith ,

     

    I went to follow up with ICM and the PG team is urgently working on this issue, but there is no specific ETA or workaround at this time.

    If it's really urgent and you are a Power BI Pro licensee, I suggest you open a support ticket and a dedicated Microsoft engineer will look into the issue for you.

    The link of Power BI Support: https://powerbi.microsoft.com/en-us/support/

    For how to create a support ticket, please refer to https://community.powerbi.com/t5/Community-Blog/How-to-create-a-support-ticket-in-Power-BI/ba-p/683031

    I will also continue to follow up on this ICM and will come back and update with results.

    It would be great if you continue to share in this issue to help others with similar problems after you know the root cause or solution.

     

    Best Regards,

    Liu Yang

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

  • Hi. Like the error message says, the F8 capacity is too small for processing the data you want. The complexity of the operation or amount of data is too much for F8. That's why it doesn't work on F8 but it do at F64. Consider reducing data or deep dive on the operations to improve the process if you need to keep it under F8.

    I hope that helps

    • lawrenceabith's avatar
      lawrenceabith
      Helper IV

      Hi ibarrau,

       

      We didn't do anything new. Last week, everything was working with Fabric F8 well. This error started yesterday. Do you know how to analyze and discover what report or reports may be causing this?

       

      Many thanks for your help.

      • Brunner_BI's avatar
        Brunner_BI
        Impactful Individual

        Take a look at where you added measures, calculated columns or where more data was added recently.

        I would encourage you to kick out any columns/measures that you do not need in your datasets. Leverage external tools like Measure Killer for that.

  • Anonymous's avatar
    Anonymous
    Not applicable

    Hi  lawrenceabith ,

     

    We have seen on the internal platform that other engineers have reported this issue and submitted it.
    The engineers on the product team are now aware and will do their best to resolve the issue. I will update here if there is any progress, so please be patient.

     

    Best Regards,

    Liu Yang

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

  • souldish's avatar
    souldish
    Frequent Visitor

    This error is currently happening for several datasets on F64 capacity, have opened a support ticket on it.

    [ValidateMarkupTags]<ccon>[ccon]DataSource.Error: Microsoft SQL: [ccon]This query was rejected due to current capacity constraints. Statement ID: {81A523EE-FAC6-4A62-94B8-EB3F77BAD2BD} | Query hash: 0xC7D828038BCF5C09 | Distributed request ID: {4A9146E9-A70F-4B23-AF09-14CF6E0D64BB}[/ccon]. DataSourceKind = [ccon]SQL[/ccon]. DataSourcePath = [ccon]77r35byqs75enmsrrfkiry3xo4-uuszo4u4b5wenaz2dopyuml7g4.datawarehouse.pbidedicated.windows.net;WO_Lakehouse[/ccon]. Message = [ccon]This query was rejected due to current capacity constraints. Statement ID: {81A523EE-FAC6-4A62-94B8-EB3F77BAD2BD} | Query hash: 0xC7D828038BCF5C09 | Distributed request ID: {4A9146E9-A70F-4B23-AF09-14CF6E0D64BB}[/ccon]. ErrorCode = [ccon]-2146232060[/ccon]. Number = [ccon]65000[/ccon]. Class = [ccon]17[/ccon]. State = [ccon]1[/ccon]. [/ccon]. The exception was raised by the IDataReader interface. Please review the error message and provider documentation for further information and corrective action.</ccon> Table: vw_dim_account.

  • Hey,

     

    I encountered the same problem again yesterday, and now I'm constrained to working solely in F64. Is this an issue for anyone else? My fabric capacity is in Brazil. Can Microsoft help me? This is going to lead us to additional costs.

     

     

    Thanks,

  • PWTRyanWhite's avatar
    PWTRyanWhite
    Frequent Visitor

    Hi,

     

    I'm running into capacity limits while running a F256 limit, which I would hope could just about handle anything at that price point.

    Here is the error:

     

    Here is the proof of F256: