Lakehouse Acess Error

[malheirosJordan]

Since yesterday late afternoon, I’ve been unable to access some of my Lakehouses in Fabric. I keep getting the message “An exception occurred. Please refresh the page and try again.” and nothing loads. The Lakehouse endpoint appears to be working fine, and the pipelines seem to be running as expected, but I can’t access them through the UI at all.

Is anyone else experiencing this issue?

PS: This only appears in some specific Lakehouse's.

[vicenteajm · Accepted solution]

@MohamedOz  @malheirosJordan @sawilliams @UserNotFound @V-yubandi-msft 

here is the solutions.

You need to change the language to English and remove the browser's default language setting, and like magic, everything works.If this solution worked for you like it did for me, I’d appreciate your star and rating! 😊

[rafael_martins]

Thank you a lot @vicenteajm , it worked perfectly. However, it is a shame that kind of issue persist for such a long time, MS Fabric it is a really great platform, but suffer with a lot of anoying bugs.

[malheirosJordan]

It worked! I never imagined the issue was caused by something like this. Even so, I opened a ticket with Microsoft, as I believe this might be a bug worth reporting.

[vicenteajm]

@malheirosJordan  This is the best , is better open the ticket , this is not usual, but i glad this "solution" help

[MohamedOz]

I faced the same probelm since yesterday!

[sawilliams]

Has anyone found a solution to this issue?

For the past two days, I haven't been able to access my LH_Bronze from the UI. The strange thing is that other Lakehouses work just fine. I’m also seeing the same issue in a different Fabric environment for another client — the LH_Bronze there also throws an error when accessed from the UI.

[malheirosJordan]

Not yet, i'm going to open a ticket with Fabric support.

[UserNotFound]

I have had this error since yesterday and it persists today.

I tried using another account, different browser, clearing the cache, deleting cookies, using incognito mode, creating a new resource with a new Lakehouse, creating a new Lakehouse within the same resource, deleting every existing lakehouse and resource but nothing worked.

In order to give more details about the problem, here is something I tried:
I created a new Lakehouse and ingested test data provided by microsoft.

Using the explorer to navigate to tables works just fine, but navigating to files results in the exact same screen shown in @malheirosJordan's screenshot.

This problem occurs even when creating a new Lakehouse, creating a subfolder and refreshing the page, while no data was added to the Lakehouse.

@V-yubandi-msft , can you expand on the solution to "Force a metadata refresh to see if that resolves the issue. "?

[V-yubandi-msft]

Hi @malheirosJordan ,

Thank you for engaging with the Microsoft Fabric Community. It appears the issue may be due to metadata corruption or a service side problem affecting the UI for certain Lakehouses. Since clearing the cache didn’t fix it and multiple users are experiencing the same problem, here are my recommendations.

1. Force a metadata refresh to see if that resolves the issue. 

2. Test with a new Lakehouse to check if the problem persists.   

3. Check for any service outages that could be impacting functionality.

If these steps don’t work, it would be best to contact Microsoft Support they can inspect server side logs and investigate any potential bugs.

Meanwhile, you can continue working with your data through the SQL analytics endpoint or notebooks to minimize disruptions.

Regards,

Yugandhar.

[vicenteajm]

I've had an error since tonight: I can't use the new or old Lakehouses. I'm getting this error.

Please follow these steps.

1) Change browser: Doesn't work
2) Delete cookies: Doesn't work
3) Clear the cache: Doesn't work
4) Open the browser in incognito mode: Doesn't work

It fails exactly when I try to create a subfolder or when I try to upload a file to Lakehouse.

[vicenteajm]

I have de the same problem in this moment i change de browser and the incogn window but still down

[gslick]

Have you tried it in a different browser?

[malheirosJordan]

Yes, none of the other users in the workspace are able to access it either. We've already cleared cookies and reset the cache, but the issue persists.