Forum Discussion

vicenteajm's avatar
vicenteajm
Most Valuable Professional
1 year ago
Solved

Lakehouse Acess Error occurred

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.

Falla exactamente cuando intento crear una subcarpeta o cuando intento cargar un archivo a Lakehouse.

  • Hi vicenteajm,

    Thanks for reaching out to the Microsoft fabric community forum.


    Permissions Issue
    You may not have the correct write or edit permissions on the Lakehouse.
    Even if you can view it, uploading or folder creation usually requires additional privileges.
    Lakehouse Service Outage
    There might be a temporary service outage or backend issue with the Lakehouse platform (especially if it's hosted on services like Microsoft Fabric or Azure Synapse).
    Check service health status pages.
    File Size or Type Restrictions
    Some platforms restrict the size, format, or type of files that can be uploaded.
    Uploading unsupported file types or files that exceed size limits can trigger errors.
    Lakehouse Quota Limits
    The Lakehouse or storage account may have reached its quota limit (e.g., storage space or number of files/folders).
    This could prevent new folders or files from being created.
    Browser Extensions or Corporate Network Policies
    A browser extension (like ad blockers or security plugins) or company firewall may be interfering with requests.
    If you’re on a corporate VPN or secured network, those policies might be blocking some API endpoints.
    Corrupted Metadata or Sync Issues
    The metadata or internal structure of the Lakehouse may have become corrupted or unsynchronized, especially after failed upload attempts.
    How to Fix It
    Basic Troubleshooting (Already Done)
    Change browser
    Clear cache/cookies
    Use incognito mode
    Advanced Checks

    Check Permissions
    Ensure you have Contributor or Owner access to the Lakehouse.
    Ask your admin to re-grant permissions or test with a different user account.
    Test on a Different Network
    Try accessing from a different Wi-Fi/network or turn off VPN.
    This rules out firewall or proxy-related issues.
    Check File Restrictions
    Try uploading a very small .txt file or creating a test folder with a simple name like testfolder.
    If that works, the issue may relate to file size/type or naming conflicts.
    Inspect Console Logs
    Press F12 in your browser > go to the Console or Network tab.
    Attempt the upload/folder creation again and look for any error messages or failed network requests.
    Create a New Lakehouse as a Test
    Try creating a brand-new Lakehouse and test file upload/folder creation there.
    If it works in the new one, your original Lakehouse may be corrupted or misconfigured

     

     

    If this post helped resolve your issue, please consider giving it Kudos and marking it as the Accepted Solution. This not only acknowledges the support provided but also helps other community members find relevant solutions more easily.

    We appreciate your engagement and thank you for being an active part of the community.

    Best regards,
    LakshmiNarayana.

4 Replies

  • v-lgarikapat's avatar
    v-lgarikapat
    Community Support

    Hi vicenteajm,

    Thanks for reaching out to the Microsoft fabric community forum.


    Permissions Issue
    You may not have the correct write or edit permissions on the Lakehouse.
    Even if you can view it, uploading or folder creation usually requires additional privileges.
    Lakehouse Service Outage
    There might be a temporary service outage or backend issue with the Lakehouse platform (especially if it's hosted on services like Microsoft Fabric or Azure Synapse).
    Check service health status pages.
    File Size or Type Restrictions
    Some platforms restrict the size, format, or type of files that can be uploaded.
    Uploading unsupported file types or files that exceed size limits can trigger errors.
    Lakehouse Quota Limits
    The Lakehouse or storage account may have reached its quota limit (e.g., storage space or number of files/folders).
    This could prevent new folders or files from being created.
    Browser Extensions or Corporate Network Policies
    A browser extension (like ad blockers or security plugins) or company firewall may be interfering with requests.
    If you’re on a corporate VPN or secured network, those policies might be blocking some API endpoints.
    Corrupted Metadata or Sync Issues
    The metadata or internal structure of the Lakehouse may have become corrupted or unsynchronized, especially after failed upload attempts.
    How to Fix It
    Basic Troubleshooting (Already Done)
    Change browser
    Clear cache/cookies
    Use incognito mode
    Advanced Checks

    Check Permissions
    Ensure you have Contributor or Owner access to the Lakehouse.
    Ask your admin to re-grant permissions or test with a different user account.
    Test on a Different Network
    Try accessing from a different Wi-Fi/network or turn off VPN.
    This rules out firewall or proxy-related issues.
    Check File Restrictions
    Try uploading a very small .txt file or creating a test folder with a simple name like testfolder.
    If that works, the issue may relate to file size/type or naming conflicts.
    Inspect Console Logs
    Press F12 in your browser > go to the Console or Network tab.
    Attempt the upload/folder creation again and look for any error messages or failed network requests.
    Create a New Lakehouse as a Test
    Try creating a brand-new Lakehouse and test file upload/folder creation there.
    If it works in the new one, your original Lakehouse may be corrupted or misconfigured

     

     

    If this post helped resolve your issue, please consider giving it Kudos and marking it as the Accepted Solution. This not only acknowledges the support provided but also helps other community members find relevant solutions more easily.

    We appreciate your engagement and thank you for being an active part of the community.

    Best regards,
    LakshmiNarayana.

    • v-lgarikapat's avatar
      v-lgarikapat
      Community Support

      Hi vicenteajm ,

      If your issue has been resolved, please consider marking the most helpful reply as the accepted solution. This helps other community members who may encounter the same issue to find answers more efficiently.

      If you're still facing challenges, feel free to let us know—we’ll be glad to assist you further.

      Looking forward to your response.

      Best regards,
      LakshmiNarayana.

      • v-lgarikapat's avatar
        v-lgarikapat
        Community Support

        Hi vicenteajm ,

        If your question has been answered, kindly mark the appropriate response as the Accepted Solution. This small step goes a long way in helping others with similar issues.

        We appreciate your collaboration and support!

        Best regards,
        LakshmiNarayana