Unable to query Sequel Analytics Endpoint of table in Lakehouse

[Rocco_Praelexis]

Hi,

My dataflows failed due to the same reasona above, when they try to access a table in a lakehouse. I can't run query within Fabric on the table within the lakehouse either using the sequel analytics endpoint. This happened inexplicably overnight and never reverted. 

The image contains the details, bear in mind I am an admin on the workspace within which the lakehouse lives.

Please help. 

[Anonymous]

HI @Rocco_Praelexis,

Any update on this? Did this issue fixed or still occurred on your side?

Regards,

Xiaoxin Sheng

[Rocco_Praelexis]

Hi Xioxin,

The issue was resolved by the microsoft technical support team, but the reason for the error wasn't disclosed.

Thanks.

[KevinChant]

Just to check, did you make sure the permissions for the Lakehouse did not change? Might be worth checking if a colleague has the same issue because this can occur if a permission changed or a a Lakehouse has been shared without the SQL analytics endpoint option enabled...

[Anonymous]

HI @Rocco_Praelexis,

Based on the error messages, it mentions these operations encounter operating system error when 'attach the physical metadata'.
Have you tried to use you or other account to manually access the target Lakehouse to ensure its status normal and the table is existed?
Any important changes that applied to the Lakehouse and its tables before the error occurred? (e.g. data warehouse restore point operations)

Please provide some more detailed information to help us clarify your scenario and test to troubleshoot.
Regards,
Xiaoxin Sheng

[Rocco_Praelexis]

Hi @Anonymous 

I can access the delta tables correctly from the lakehouse, but not the sql endpoint. To my knowledge there were no important operations applied to the warehouse restore point operations. 

@miguel 

This still pertains specifically to Dataflows Gen 2 since the dataflow refresh fails with the error same message.

Please advise what information to provide to resolve the issue.

[miguel · Accepted solution]

As previously mentioned, the dataflow is just exposing the error from the source. The Dataflow trying to execute its code is not really the culprit of the issue.

Based on the info that you've shared, I'd suggest reaching out to the support team by raising a support ticket so they can get to the bottom of the issue around the SQL endpoint. It seems that regardless of the client application that you use, you simply can't query that SQL endpoint.

[Rocco_Praelexis]

How does one typically raise such a support ticket? Is there a best way of going about it?

Appreciate the responses btw.

[miguel]

Here's the link to the page where you can raise the support ticket:

https://support.fabric.microsoft.com/support

[miguel]

I've moved this to a forum different from Dataflows Gen2 as this appears to be a question around the data source itself and an error coming from it and not one coming directly or originated by a Dataflow Gen2 logic.