We couldn't load your SQL endpoint

[cjfjones]

Hi,

Have started experiencing an issue today, loading the SQL Endpoint view in Fabric.

I am still able to consume the data in Power BI, and also through SSMS using the SQL Endpoint, but get the below error when using the Web Interface. I need to update the relationships in the model, and believe this can only be achieved through the SQL endpoint interface in the Lakehouse.

Any help appreciated.

Activity ID: d41e2f45-3639-4c48-8e12-c3464e05894f
Request ID: 88080a5f-1a86-0fee-d1c1-d06b4103e334
Correlation ID: b51ac36f-dcec-0760-6c69-d4aff3fc33d7
Status code: 0
Time: Thu Aug 03 2023 17:34:38 GMT+0100 (British Summer Time)
Service version: 13.0.21259.51
Client version: 2307.5.15071-train
Cluster URI: https://wabi-north-europe-redirect.analysis.windows.net/

[v-xiaoyan-msft]

Hi  @cjfjones ,

We have seen on the internal platform that other engineers have reported this issue and submitted it.
The engineers on the product team are now aware and will do their best to resolve the issue. I will update here if there is any progress, so please be patient.

Best regards.
Community Support Team_Caitlyn

[v-xiaoyan-msft]

Update :

A fix for this issue is being deployed and you can retry later.

Best regards.
Community Support Team_Caitlyn

[jvasaa]

Hello, @v-xiaoyan-msft.

I am getting the same error "We couldn't load your SQL endpoint" just now:

• Activity ID8f24deaf-dac1-490b-9495-2b3b19a094a2
• Request ID18428420-9fdd-a708-ccd3-18234db8413f
• Correlation IDe54cfdc5-361f-ba95-cefe-4c9d6984a19e
• Status code500
• TimeFri Aug 18 2023 07:27:00 GMT+0300 (Eastern European Summer Time)
• Service version13.0.21310.58
• Client version2308.1.15207-train
• Cluster URIhttps://wabi-north-europe-redirect.analysis.windows.net/

[Anonymous]

Hello,

I have the same problem, today 23th of August.

Thank you in advance

Best regards,

Barbara

[spp-101]

@v-xiaoyan-msft  I am also experiencing this issue. Batch was cancellecd with status code 400

Any help appreciated.

[FelixL]

Same exact issue here, today.

If I have read/admin permissions on the workspace in which the Lakehouse reside, the SQL endpoint seem to be working properly. But in the cases where access is provided directly (and only) on the Lakehouse artifact (no user view access on the workspace) the SQL endpoint will not load correctly.

However, if the user who has gotten the Lakehouse artifact shared (but no workspace read access) in turn create its own Lakehouse in its own Private Workspace it can successfully create shortcuts to the tables tables in the original Lakehouse, and successfully use the SQL endpoint in its own Private Lakehouse.

This is fully (100%) reproducable with multiple user accounts and newly created workspaces and lakehouses. 

[Anonymous]

Thank you Felix,

my colleagues seem to confirm your point, we have to test it exactly.