Forum Discussion

Timal's avatar
Timal
Helper I
2 years ago
Solved

SQL-Endpoint not working anymore

Hello,   Since today im Experiencing issues with the SQL-Endpoints from my Warehouses and also Lakehouses. I can access Data with Spark (Lakehouse) but i cannot Access Data via the SQL Endpoint ne...
data warehouse
Warehouse
  • Timal's avatar
    Timal
    2 years ago

    I've found the issue. The user who created the Warehouses/Lakehouses has been deactivated.

    Du to the Warehouses using delegate Permissions from the Owner for other users to access the Data, the User cannot be removed from the Workspace or Access will break.

    According to the following Guide PowerShell can be used to change Ownership.

    Change ownership of Fabric Warehouse - Microsoft Fabric | Microsoft Learn

    However so far this only worked with Warehouses and NOT Lakehouses for me.

    Hope this helps! ... and i find out how to fix the Lakehouses

     

    EDIT:

    Microsoft confirmed that the Owner of Lakehouses currently can only be changed by them. So you'll have to open a Ticket. They plan to allow the end user to change that in the future.

    I don't understand why the Access to the Warehouses is not managed via Service Principal (like other Services) instead of User Delegation but it is what it is.

Anonymous's avatar
Anonymous
Not applicable
1 year ago

I'm having the same issue as the initial poster. I can access my lakehouse data but the SQL enpoint is unavailable. This is casuing issues with my Dataflow Gen2s & I basically can't use the system at all. Unlike the solution here, the owner of the Lakehouse has not been deactivated or changed. I am getting the same error as above: "DataSource.Error: Microsoft SQL: Encountered operating system error 5(Access is denied.) while attempting to read physical metadata." 

 

Any other possible solutions to this issue? 

 

  • Timal's avatar
    Timal
    Helper I
    1 year ago

    Hey,

    Did you check if the user who created the resources (owner) has permission to use Fabric (Admin Settings) and has access to the Workspace?

    Could think that one of those might also cause the issues. Since Fabric is using the Owners delegated identity to access the Data it must be something with the owners permissions.

     

    Regards,

    Tim

    • Anonymous's avatar
      Anonymous
      Not applicable
      1 year ago

      So the owner does not have access to the workspace. But I have full admin rights for both the workspace and the lakehouse. Will I need to change the owner of the lakehouse to solve this issue?

       

      Thanks 

      L

      • Timal's avatar
        Timal
        Helper I
        1 year ago

        Since you're admin you could try adding the owner to the workspace as Contributor or Higher and see it it resolves the issue. It's not a 100% shot but since technically the Owner does't have Permissions on the Lakehouse it could cause the issue i suppose.

        If it works when re-adding it then you either have to keep it like that (if thats possible) or change the owner, yeah.

        You could check if there may be a way for us to change Owners ourselves now since it's been a while since my issue, otherwise you'd have to create a Ticket like i had to then.