Forum Discussion

rubayatyasmin's avatar
rubayatyasmin
Community Champion
1 year ago
Solved

Encountered operating system error 5(Access is denied.) while attempting to read physical metadata.

Hi everyone,

I'm currently working with a Lakehouse and associated warehouses in my Fabric environment. I’m able to access the Lakehouse, and while it takes some time, I can preview data for tables. However, I’m running into an issue when trying to execute queries.

I’ve tried connecting to the SQL endpoint using the connection string and managed to connect via MS SQL Server Management Studio, but I’m unable to run any queries on the tables in the Lakehouse database.

Has anyone faced a similar issue or have any insights on how to run queries in the Lakehouse using the SQL endpoint?

Thanks in advance!

 

The error in WH:

 

  • rubayatyasmin's avatar
    rubayatyasmin
    1 year ago

    Thanks for the information. I checked the known issues already. My problem solved after reauthenticating all the connections. 

10 Replies

  • v-veshwara-msft's avatar
    v-veshwara-msft
    Community Support

    Hi rubayatyasmin ,

    Thank you for reaching out to the Microsoft Fabric Community.

    Appreciate your insights, nilendraFabric 

    There have been some known issues reported related to this.


    1. Table Sync Issues in West Europe Region.

    Symptoms:

    • Users may experience table latency issues when syncing tables, schema, or semantic models.

    Workaround:

    • Retry the sync operation as a temporary fix while Microsoft’s engineering team is working on a permanent solution.

    Known issue - Sync for data warehouse and SQL analytics endpoint fail in West Europe - Microsoft Fabric | Microsoft Learn

     

    2. Table Sync Failures Due to Unsupported Columns

    Symptoms:

    • If column mapping includes unsupported columns, the metadata sync may fail.

    Workaround:

    • Check for unsupported columns in the Lakehouse table and remove them before reattempting the sync.

    3. SQL Analytics Endpoint Permissions Not Persisting After Schema Changes

    Symptoms:

    • Table permissions in the SQL analytics endpoint may not persist after a successful sync.

    Workaround:

    • If a schema change was made, reapply permissions on the SQL analytics endpoint after sync completion.

    Known issue - SQL analytics endpoint tables lose permissions - Microsoft Fabric | Microsoft Learn

     

    Additionally, When using SQL Server Management Studio (SSMS), queries may fail due to local permission restrictions.

    Try running SSMS as an administrator to rule out local permission issues on your machine.

     

    Thank you for your patience while the Microsoft Engineering team works on resolving these issues.

    Since you've already raised a support ticket, hopefully, it will be addressed and resolved soon.

     

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

     

    Best Regards,
    Vinay.

     

    • rubayatyasmin's avatar
      rubayatyasmin
      Community Champion

      Thanks for the information. I checked the known issues already. My problem solved after reauthenticating all the connections. 

      • aflath's avatar
        aflath
        Frequent Visitor

        Yea.  I had to reauthenticate as well.  Basically went into the Data Source setting, and re-logged in. 

  • Hello rubayatyasmin 

     

    I am facing similar issue with LH tables for last few days.

     

    Newly added or updated tables may not yet be visible due to stale metadata

     

    Try Trigger metadata synchronization manually, although it didn't worked for me.

     

     

    Seems like something has been changes behind the scenes, worth raising the support ticket 

     

     

    • rubayatyasmin's avatar
      rubayatyasmin
      Community Champion

      Yeah, the tables are not new. Sync was perfect but from 2 days it started throwing errors. Raised a support ticket already at the time of posting. But as the matter needs to solve urgently thought of posting it here as well.