SQL EndPoint of a Lakehouse not working even after changing ownership

[maxmerchant]

Hello Fabric community,

I'm encountering a strange issue.

We have a Lakehouse (say LH_A) created in a workspace (say WH_A) by a user (say User A) . However, that user (user A) is no longer with the organization. We opened a support ticket with Microsoft and changed the ownership of the said Lakehouse (LH_A) to another (say user B).  Everything was good after changing the owership and we could use the SQL EndPoint, however, since yesterday, we are encountering this issue when try to use SQL Endpoint for the said lakehouse (LH_A).  

See screenshot below for the error.

The weird thing is that we have another Lakehouse in another workspace with the same situation (i.e., user who created the LH left the company and we changed the ownership to the same user B) but we can use the SQL EndPoint without any issues.

Note: User B is still with the organization and is a workspace + tenant admin. Both these lakehouses were created prior to the schema previews being available.

Any help would be appreciated, thanks

[maxmerchant · Accepted solution]

We were finally able to resolve this issue.

We had a warehouse in the same workspace (WH_A) which was created by the user (user A) that is no longer with the organization. We used the instructions provided in the link below to change the ownership of the warehouse to another user (user B). And now the SQL EndPoint of the lakehouse (LH_A) is working fine and we no longer see this error. 

https://learn.microsoft.com/en-us/fabric/data-warehouse/change-ownership

We also did the same thing to resolve the SQL EndPoint error with another Lakehouse in another workspace i.e, changed the owner of the WH from inactive user to an active user. And it worked on that lakehouse too.

Not sure how the changing the ownership of the warehouse resulted in the lakehouse endpoint working but glad it did.

[v-huijiey-msft]

Hi @maxmerchant ,

Is my follow-up just to ask if the problem has been solved?

If so, can you accept the correct answer as a solution or share your solution to help other members find it faster?

Thank you very much for your cooperation!

Best Regards,
Yang
Community Support Team

If there is any post helps, then please consider Accept it as the solution  to help the other members find it more quickly.
If I misunderstand your needs or you still have problems on it, please feel free to let us know. Thanks a lot!

[v-huijiey-msft]

Hi @maxmerchant ,

It was working fine before and now it's suddenly wrong, I understand your frustration.

I have a couple suggestions:

Clear your browser cache and log back into your service account to check if the problem still exists.

Change the ownership of said Lakehouse (LH_A) to another (other than user B) user and check if the problem still exists.

Now that you have opened support ticket, follow up. Provide them with detailed information and screenshots to help diagnose the issue more effectively.

We hope this has been helpful!

Best Regards,
Yang
Community Support Team

If there is any post helps, then please consider Accept it as the solution  to help the other members find it more quickly.
If I misunderstand your needs or you still have problems on it, please feel free to let us know. Thanks a lot!

[maxmerchant]

Thanks for the suggestions.

Tried clearing the browser cache and still had the same issue.

In terms of changing the ownership of the Lakehouse, waiting on the tenant admin to help initiate the change in ownership of the Lakehouse.

I will keep everyone posted on this but it may take few more days.

Thanks

[v-huijiey-msft]

Hi @maxmerchant ,

Is my follow-up just to ask if the problem has been solved?

If so, can you accept the correct answer as a solution or share your solution to help other members find it faster?

Thank you very much for your cooperation!

Best Regards,
Yang
Community Support Team

If there is any post helps, then please consider Accept it as the solution  to help the other members find it more quickly.
If I misunderstand your needs or you still have problems on it, please feel free to let us know. Thanks a lot!