Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Register now to learn Fabric in free live sessions led by the best Microsoft experts. From Apr 16 to May 9, in English and Spanish.

Internal error prevented loading the schema

Hi everyone!

 

Since this morning (or even earlier) we can't open reports in the Power BI service. We keep getting this error:

 

Internal error prevented loading the schema

An internal error prevented loading the model schema associated with this report. Please try again later. If the issue persists, contact Power BI support.

Please check the technical details for more information. If you contact support, please provide these details.Hide details
  • Underlying ErrorException while parsing CSDL to create Conceptual Schema. Model ID=1519909
  • Activity ID8ce202a0-b44d-48b6-819d-b87444962581
  • Correlation ID293e6f5b-6658-e0c5-98ca-0d03655a11ac
  • Request ID2c60e6d3-d470-45c6-9a44-e7a7a543951a
  • TimeFri Dec 16 2022 11:42:42 GMT+0100 (Mitteleuropäische Normalzeit)
  • Service version13.0.19635.59
  • Client version2212.1.11454-train

Cluster URIhttps://wabi-west-europe-d-primary-redirect.analysis.windows.net/

 

Power BI desktop is working fine. I also published one of the reports in my personal workspace but the error message was the same.

 

I hope someone can help.

 

Many thanks!

 

Best

Status: Needs Info

Hi @K4bal 

Can you open your reports on Service normally now ? I have not seen a similar known issue so far . 

 

Best Regards,
Community Support Team _ Ailsa Tao

Comments
K4bal
Frequent Visitor

@v-yetao1-msft and I also found this in the network log:

 

        "response": {
          "status": 401,
          "statusText": "Unauthorized",
          "httpVersion": "HTTP/1.1",
          "headers": [
            {
              "name": "Access-Control-Allow-Credentials",
              "value": "true"
            },
            {
              "name": "Access-Control-Allow-Origin",
              "value": "https://app.powerbi.com"
            },
            {
              "name": "Access-Control-Expose-Headers",
              "value": "RequestId,X-PowerBI-Error-Info,X-PowerBI-CannotAccessV2WorkspaceAsV1"
            },
            {
              "name": "Content-Length",
              "value": "0"
            },
            {
              "name": "Date",
              "value": "Mon, 19 Dec 2022 07:10:02 GMT"
            },
            {
              "name": "RequestId",
              "value": "e25da5b0-d4a1-4aeb-9d69-3646622c2e46"
            },
            {
              "name": "Strict-Transport-Security",
              "value": "max-age=31536000; includeSubDomains"
            },
            {
              "name": "X-Content-Type-Options",
              "value": "nosniff"
            },
            {
              "name": "X-Frame-Options",
              "value": "deny"
            },
            {
              "name": "X-PowerBI-CannotAccessV2WorkspaceAsV1",
              "value": "8fb421c2-0604-4e70-b9a8-866e9303b1ac"
            },
            {
              "name": "X-PowerBI-Error-Info",
              "value": "GroupNotAccessible"
            }
          ],
LiamRall
Frequent Visitor

Hi everyone.

 

I am also experiencing the same issue and it has affected most of my reports. If support gets back to you then please keep us posted! @K4bal 

 

All the reports affected by this error have connections to Azure SQL and Salesforce if that helps at all. I have a report that is connected to SharePoint Lists that is in the same workspace and does not have this error.

K4bal
Frequent Visitor

Hi @LiamRall 

 

for me the problem were calculation groups. Although I'm not 100% certain which part of the calculation groups was the problems origin. I highly suspect the "KPI Format" option.

 

I solved the problem by deleting one by one calculation group and after every delete I published to report to a test workspace to check if it's working again. But in the end I had to recreate all my calc. groups without the KPI Formatting and this solved the problem by now.

 

But the support told me that the product team is still investigating the problem.

 

I hope this helps!

 

Best  

LiamRall
Frequent Visitor

Hi @K4bal 

 

Your suspicion is correct! I had a single KPI format attached to a measure in my report (I was trying them out last week). I deleted that and republished, and it has fixed the error! The KPI format was on a measure and not a calculation group, so I think the error is specifically to do with KPIs.

 

Thanks for your assistance!