Forum Discussion
Lost access to lakehouse Files functionality
Hello everyone,
Since yesterday (05/20/2025), I have lost all functionality in the "Files" folder of Lakehouse. If I create a new folder, I am able to open it. However, when I upload a new file to it, the file does not appear, and Fabric displays the error:
"An exception occurred. Please refresh the page and try again."
This issue occurs even if I create a new Lakehouse or a new Lakehouse in a new workspace.
In OneLake Explorer, the uploaded file in the new test Lakehouse only appeared today (05/21/2025).
If I delete this file via OneLake Explorer, access is restored. However, if I upload the same file again, I lose access once more, and the newly uploaded file does not appear in the Explorer.
In my "official" Lakehouse, only 1 out of 3 files uploaded at the same time is visible.
All files are 5 megabytes or less, so size doesn’t seem to be the issue.
Is anyone else experiencing this? I’ve checked with others in my organization, and it doesn't seem to be happening to them.
A clean new Files folder.
After loading one file:
The issue will be fixed by EOD, May 22nd.
7 Replies
I apologize for this issue. This is a regression error from Microsoft affecting non-English locales in the Files section. Switching PBI to English is an immediate fix, and a permanent fix will be rolled out by May 25.
The issue will be fixed by EOD, May 22nd.
Hi daPaga ,
This sounds like a potential sync or metadata issue between Fabric and OneLake. A few things you can try:
- Try uploading the file with a simplified name (e.g., testfile.csv) – avoid special characters.
- Use a different file format (e.g., .txt or .parquet) to see if the issue persists.
- Clear your browser cache or try a different browser – sometimes the UI gets stuck.
- If the file appears in OneLake Explorer the next day, it might be a delayed sync issue.
- Since it happens even in new Lakehouses, I’d recommend opening a support ticket – this might be a backend issue.
If my response resolved your query, kindly mark it as the Accepted Solution to assist others. Additionally, I would be grateful for a 'Kudos' if you found my response helpful.
Hi daPaga
Just to add a few more things that might help:
- Try switching the browser language to English temporarily and see if the issue persists. There have been cases where locale-specific bugs affected the UI behavior.
- Check the DevTools console (F12) for any specific error codes or failed network requests – sometimes that gives more clues than the UI message.
- If you're using a corporate network or VPN, try accessing from a different network to rule out any proxy/firewall interference.
Also, if this started happening suddenly on a specific date, it might be worth checking the Microsoft Fabric Status page for any known incidents around that time.
Let me know if any of this helps or if you want to dig deeper into one of the angles.
You need to change the language to "English (United States)"
Hi daPaga,
As we haven’t heard back from you, we wanted to kindly follow up to check if the solution provided for your issue worked? or let us know if you need any further assistance here?
tvilutis1, kalebe_barros, burakkaragoz Thanks for your prompt response.
Thanks,
Prashanth Are
MS Fabric community support
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly and give Kudos if helped you resolve your query
Hello everyone,
I confirm that the bug has been fixed in my native language (not English). Before the fix, changing the UI language to english was a good workaround.
Thank you so much for all the replies.
