Forum Discussion

KiaZ's avatar
KiaZ
Frequent Visitor
8 months ago
Solved

Error- Cant connect to the artefact

Hello, Here is the detailed context of the issue we are facing in Microsoft Fabric right now. What happened: I received an error in my semantic model indicating that a column was missing. I c...
lakehouse
  • KiaZ's avatar
    KiaZ
    8 months ago

    Hi There,

    The metadata in the Fabric Backend was not synced anymore, thats why i got the artefact issue. After 24h, it started to work again. So it was just a matter of waiting.

v-pnaroju-msft's avatar
v-pnaroju-msft
Community Support
8 months ago

Thankyou, Ugk161610, for your response.

Hi KiaZ,

Based on my understanding, your column change and overwrite caused Fabric’s workspace connection or gateway binding and the affected user’s session or connection metadata to fall out of sync. This explains why one administrator can open Manage Connections while your account becomes unresponsive. Your account is using a stale or partially created connection binding that is not recognized by the backend.

Please follow the steps below, which may help to resolve the issue:

  1. Sign out, clear the browser cache, or open Fabric in Incognito or Private mode and then retest Manage Connections. This forces the issuance of new tokens and often resolves per user UI freezes.
  2. Ensure your account has the role of Admin, Member or Contributor in the workspace, since Viewer or Guest roles cannot bind connections. If you are a Guest, either promote your account to a tenant user or ask an internal administrator to perform the binding.
  3. Attempt to delete the connection from Workspace → Settings → Connections. If the UI is blocked for your account, use the Fabric REST API to delete the stuck connection object. After deletion, reopen your dataflow or connection so that Fabric can create a fresh binding.
  4. On the gateway machine, confirm that the gateway service is running, that the gateway is updated to the latest version, and that outbound traffic is permitted.
  5. Open the Lakehouse SQL analytics endpoint → Manage → Refresh schema (or invoke the REST API to refresh endpoint metadata). This clears SQL endpoint caching.
  6. Create a new minimal Dataflow Gen2 and attempt a refresh. If it succeeds, the workspace is functioning correctly again.

Please refer to the links below for further information:
Troubleshoot the on-premises data gateway | Microsoft Learn
Lakehouse management API - Microsoft Fabric | Microsoft Learn
Manage an on-premises data gateway | Microsoft Learn
Items - Refresh Sql Endpoint Metadata - REST API (SQLEndpoint) | Microsoft Learn
SQL Analytics Endpoint Performance Considerations - Microsoft Fabric | Microsoft Learn

We hope this information helps to resolve the issue. If you have any further queries, please feel free to contact the Microsoft Fabric community.

Thank you.