Fabric Lakehouse SQL endpoint access to physical metadata denied

[Anonymous]

Hello everyone,

the SQL endpoint of my Development Workspace stopped working over the weekend without conscious input from my side. When I try to query it from a .pbix file on Desktop or execute a query on a table in the Fabric SQL dialogue directly, I get the following error that I don't know what to do about:

Encountered operating system error 5(Access is denied.) while attempting to read physical metadata.
Statement ID: {9C5D09AC-90E5-40CE-8C51-13F68ACD16ED} | Query hash: 0x8985B227F510CFB1 | Distributed request ID: {A842FCEB-66A0-4800-8A60-D42097D5AB7D}
10:12:37 AM SQL Server execution time: 00:02:08.231 | Total duration: 00:02:18.800

In case it's something about permissions: My account is admin in the workspace, and in the test and production workspaces, so far everything works as expected.

Any info is much appreciated, thanks!

[walkermullin]

I had the same issue as the above, but I was unable to access the SQL analytics Endpoint of a Lakehouse and the owner of the Artifacts account was still active, yet he had not logged into the Fabric tennant in about 6 months. Even though the account was technically still active the ownership of a user that had not authenticated in a while locked up the endpoint where I could not even preview in the fabric UI let alone run querries against the endpoint. When I used our Fabric service account to take over the Lakehouse all went back to normal. I believe this is a known issue that the Microsoft team is working on. 

[rafiqahmed]

Hello, 

I am having the same issue for all tables in lakehouse using the sql endpoint

Just doing a select query 

select * from colors

Got error

Encountered operating system error 5(Access is denied.) while attempting to read physical metadata.
Statement ID: {2107E84B-4817-45DC-A5FC-D3834C163F93} | Query hash: 0x3399F53E3092180D | Distributed request ID: {63004657-ADBB-43CE-9331-E193DF348C6C}

The data appear correctly in lakhouse explorer view.

[rafiqahmed]

Hello,

My problem is solved. The person who created the lakehouse left the company. We deactivated his account. We have to contact Microsoft to change the ownership of the lakehouse. After changing ownership of lakehouse. Now the problem is solved. Mightbe anyone can relate. 

Best Regards, 

[Anonymous]

HI @Anonymous,

Any change that you applied on your source data? Can you please share some more detail information about this issue? They should help us clarify your scenario and test to troubleshoot.

Regards,

Xiaoxin Sheng

[Anonymous]

The last thing I did before the problem became apparent was adding a column to a table with SQL via notebook, then the model refresh failed. But the whole SQL endpoint is broken, not just the affected table.

I will update this reply with further infos when I get them.

[Anonymous]

HI @Anonymous,

According to your description, it seems like the last operation(add column) not correctly applied.

I'd like to suggest you check exist table if the previous operations succeed committed and re-configure the schedule refresh if the old refresh brokens.

Regards,

Xiaoxin Sheng

[lbendlin]

physical metadata

This made my day.  Smh.

If you have a Pro license you can open a Pro ticket at https://admin.powerplatform.microsoft.com/newsupportticket/powerbi
Otherwise you can raise an issue at https://community.fabric.microsoft.com/t5/Issues/idb-p/Issues .

[Anonymous]

Picture of physical data: