SQL-Endpoint not working anymore

[Timal]

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 neither via Web Browser or PowerBI.

This issue seems to only persist on some tenants since it works on another Tenant i have access to. Yesterday (and before that) they were no issues, this occured just today.

I'm using an Account with Admin on the Workspace (and also Fabric Admin).

When i let the queries run i will eventually end up with the following error message:

Sounds like a backend error to me, considering i'm using an Admin Account to access it (so i definitely have access).

Tried clearing cookies and credentials in the Browser and PowerBI but no success.

Any ideas?

Update: Dataflows also crash so basically everything accessing the SQL Endpoint is broke at this point. Fabric is basically unoperable at this point.

Thanks,

Tim

[Jameopw]

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]

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

[Jameopw]

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]

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.

[Jameopw]

Heya, 

So I added the owner back to the workspace. Got them to go into the SQL enpoint & refresh the warehouse. This has solved the issue! While less than ideal, i will be taking this as a temporary solution and changing the owner further down the line! 

Thanks for your support 🙂

L

[Anonymous]

Hi @Timal ,

Have you renamed Lakehouse or Warehouse? Trying to access the SQL endpoint or Warehouse item using client tools after renaming may encounter failures.

If the suggestions above do not help you, could you provide some details such as whether the error is persistent or intermittent, and whether you have done anything else prior to the error. Detailed information can help us better understand and solve the problem you are experiencing.

Best Regards,

Ada Wang

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

[Timal]

Forgot to answer the remainder of your question. 

We haven't changed any configuration. Built a Dataflow the day before and it was working fine suddenly the day after nothing works anymore.

Thanks

[Timal]

Hey @Anonymous ,

Neither the Warehouse or Warehouse has been renamed. I double checked the linked DevOps git repo if it ever has been renamed just to be sure (because the folder will have the original name) but that is not the case.

I can basically reproduce this issue with any lakehouse or warehouse in one of the tenants i have access to. Unfortunately the issue still did not resolve. I've tested with another user in the tenant and that user is also experiencing the same issue on all SQL Endpoints.

I've tried updating the lakehouse and warehouse connections (tho it shouldnt matter) with ne Oatuh Tokens in the Connection Settings too but that didnt do anything as expected.

Im trying to restart the capacity right now if that fixes the issue but that somehow made it worse. Stuck pausing. Cant restart. 

Help would be appreciated, thanks!

EDIT: Capacity did finally pause after ~15mins and has been restarted but the issue did not resolve.

Tim

[Timal · Accepted solution]

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]

Hi @Timal ,

Thank you for your reply, I am very glad you found the problem. Can I ask if your problem is solved at the moment, please feel free to ask me any questions you may have. If the problem has been resolved, I suggest you could mark your reply as a solution, it looks like it could help more people experiencing similar problems!

Best Regards,

Ada Wang