Error fetching data for visual in a direct lake semantic model

[Stevek-09]

Hello,

I'm working on a direct lake semantic model (connected to delta tables in a lakehouse) in my workspace which has a fabric capacity (F256).

I made a report connected to that model. It was working well yesterday. But today when trying to work with the report, i have this error :

Error fetching data for this visual Aucune connexion n'a pu être établie à la source de données portant le nom 499d -9a6f-dOb 1 -authentication query Détails techniques : RootActivityld : 4afac06eosc4a05-8d72-d2910850cb88

Has someone already encountered this error ?

[v-tejrama]

Hi @Stevek-09 ,

Thank you for providing the details. I reviewed the error, and it appears to be related to authentication with the SQL endpoint of your Direct Lake semantic model. Since it worked yesterday, it's likely that something changed with your credentials or token.

Here are a few things you can try:

• Refresh or clear your browser cache and cookies, then reload the report, as an expired token may be causing the issue.
• In your Fabric workspace, go to the semantic model settings and check the data source credentials. If the SQL endpoint shows “not configured” or “expired,” re-enter your credentials with your organizational account and enable SSO if possible.
• Verify that you still have access to the Lakehouse and semantic model (at least Viewer role). If unsure, check with your workspace admin.
• Open the Lakehouse in your workspace and access the SQL Analytics endpoint directly. If it works, the problem may be with user authentication.
• Check if your Fabric capacity (F256) is active and not paused. Occasionally, service health issues can cause connection failures, so it may help to review the Fabric service status page if problems persist.

Usually, re-authenticating the data source credentials resolves this issue. Please try these steps and let us know if the problem continues.

Best Regards,
Tejaswi.
Community Support

[v-tejrama]

Hi  @Stevek-09 

I wanted to follow up and see if you had a chance to review the information shared. If you have any further questions or need additional assistance, feel free to reach out.

Thank you.

[v-tejrama]

Hi  @Stevek-09 ,

I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions.

Thank you,

Tejaswi.

[AntoineW]

Hello @Stevek-09,

I understand your issue and it seems like an authentification problem.

Most Probable Causes

• Expired Authentication Token: This is the most common reason for a sudden failure. The token used to authenticate your session with the Fabric SQL endpoint has expired.

• Credential Issues: Your personal credentials or the credentials stored for the data source within the semantic model may have become invalid.

• Permission Changes: Permissions for your user account on the Lakehouse or the semantic model might have been changed or revoked.

Troubleshooting Steps

1. Refresh and Clear Cache:

   • First, simply refresh the report page in your web browser.

   • If that doesn't work, clear your browser's cache and cookies, then try again. This can often force a new authentication token to be acquired.

2. Verify Data Source Credentials:

   • In your Fabric workspace, open Semantic model → Settings → Data source credentials.

   • You’ll see a source like *.datawarehouse.fabric.microsoft.com with status Not configured (or expired).

   • Edit credentials → sign in with your Organizational account and (if offered) enable SSO.

   • Reopen the report and test.

3. Check User Permissions:

   • Confirm that you still have the necessary permissions (at least Viewer role) on both the Lakehouse and the semantic model.

   • Reach out to your workspace administrator to verify your access rights have not been changed.

4. Check the SQL Endpoint Status:

   • Navigate directly to the Lakehouse in your workspace.

   • Check if you can access the SQL Analytics Endpoint and browse the tables. If you can, the endpoint itself is likely functioning, which points more directly to a user-specific authentication problem.

Hope it can help you ! 

Best regards,

Antoine