Forum Discussion

Anonymous's avatar
Anonymous
Not applicable
3 years ago

Corrupted dataset/report?

This error just started happening with one of our scheduled dataset refreshes (with no recent changes to the dataset itself). Manually refreshing reproduces the same error. 

 

Error: "Server could not find database folder with detach log. Database: '2754b0bf-2766-465b-aca3-b60977a9e6b2', SearchPath: 'D:\PF\pbipnorthcentraluspf8\data\AS\80\888\2754b0bf-2766-465b-aca3-b60977a9e6b2\2754b0bf-2766-465b-aca3-b60977a9e6b2.*.db'"

 

I also get a "Cannot load model" error when trying to view the report that references this dataset:

 

Underlying Error: PowerBI service client received error HTTP response. HttpStatus: 503. PowerBIErrorCode: OpenConnectionError
OpenConnectionError: Server could not find database folder with detach log. Database: '8aa19c80-6a27-4452-a5f4-e0440c3924d1', SearchPath: 'D:\PF\pbipnorthcentraluspf5\data\AS\46\085\8aa19c80-6a27-4452-a5f4-e0440c3924d1\8aa19c80-6a27-4452-a5f4-e0440c3924d1.*.db'.
Correlation ID: 6dc64de7-eaab-7ec7-c1cb-5dde34e3eb3e
Activity ID: f9f98942-c369-4f35-99d9-d0ce99dfb84e
Request ID: 3ac96758-6b7e-4eed-a85e-5001045106b5
Time: Tue Jan 31 2023 08:34:53 GMT-0600 (Central Standard Time)
Service version: 13.0.19958.49
Client version: 2301.4.12022-train
Cluster URI: https://wabi-us-north-central-b-redirect.analysis.windows.net/

Not sure how to clear this other than wiping and redeploying the dataset and report. This seems like it may be a bug/corruption in the power bi portal/service itself.

Need Help

3 Replies

  • aj1973's avatar
    aj1973
    Community Champion
    3 years ago

    Hi Anonymous 

    The error is in the path "The connection string"

     

    • Anonymous's avatar
      Anonymous
      Not applicable
      3 years ago

      You may be right, but I have nothing to do with generating that path as it is entirely something generated internally by the power bi cloud service. This is occurring in a power bi premium workspace hosted on app.powerbi.com. Therefore, it looks like a bug/corruption with Microsoft's service.

      • Anonymous's avatar
        Anonymous
        Not applicable
        3 years ago

        p.s. I was able to manually refresh the dataset via the XMLA endpoint using SQL Server Management Studio which seems to have cleared this error for now. Still no clue what created the issue but it seems like some transient condition with the cloud service (perhaps at the storage layer) that has now cleared/failed over. Will keep an eye out to see if it reoccurs.