Forum Discussion

rgrisi's avatar
rgrisi
Brass Contributor
Jun 06, 2023

Edge Workspaces error V114

I'm having an issue when selecting the workspaces menu it will "Error: Unable to load workspaces" How do I troubleshoot this issue? I need this resolved and functional as MS has enabled by default and it has rolled out to all users. I was expecting to be able to test this feature before enabling by GPO.

 

  • itsAMeUrrego's avatar
    itsAMeUrrego
    Copper Contributor
    I was Panicking about loosing all my workspaces but found a solution after reading a post on reddit.

    Turns out the problem was that my browser was not syncing so I removed my account, logged back in and voila... workspaces started working again
      • maisonhai3's avatar
        maisonhai3
        Copper Contributor
        Sign-out then sign-in back does not help me.

        I got this error after Edge update from V114 to V115, with the same details:
        "Failed to initialize Fluid"

        I remove Edge and then re-install it, this issue was gone for a while, some days, then re-appear.
    • Arti-G's avatar
      Arti-G
      Copper Contributor

      To solve this problem:
      1. Close Edge

      2. Remove Preferences file in C:\Users\     \AppData\Local\Microsoft\Edge\User Data\Default (or Profile 1 2 ...). 

      3. Open Edge and restore closed windows.

      4. Preferences file will appear, change its preferences (right click) to Read Only - this will prevent Preferences file from getting corrupted every time.

       

      It solved problem for me on V122.

  • gnuhel's avatar
    gnuhel
    Copper Contributor

    I also have the same problem on Version 116.0.1938.54 (Official build) (arm64)

     
    I have all my bookmarks on the workspace and cannot access it. Signing out and in does not help.
     
    Workspace Internals: 
    Spaces Event: EdgeFluidCSPStorageHelper failed at OnGetContainerListComplete
    {"Date":"13337166505000000","ErrorCode":503,"PrimaryError":17,"SecondaryError":36}
     
    Spaces Event: Fluid Manager Process
    Failed"Failed to initialize Fluid"
    • rgrisi's avatar
      rgrisi
      Brass Contributor

      Kelly_Y Hi- Thanks for the quick reply. Yes, all prerequisites have been met. Should I open a ticket with support to get this looked into? I'm not seeing any blocks using Fiddler or the Developer tools.

      • Kelly_Y's avatar
        Kelly_Y
        Icon for Microsoft rankMicrosoft

        rgrisi Hi! I just sent you a direct message on Tech Community.  Thanks! 

         

        -Kelly

  • ColumbiaLion23's avatar
    ColumbiaLion23
    Copper Contributor
    I am experiencing the same issue on version 114.0.1823.58. Workspaces work fine on my other Mac with the same version. Tried to remove the sync data and reload it, as well as remove and reinstall Edge.
    • rgrisi's avatar
      rgrisi
      Brass Contributor
      My issue was on a Windows 10 build. I'm not sure about MACs but after you receive the error open a new tab and run edge://workspaces-internals/ Submit the log to the Browser Team to help trouble shooting.
      • Kelly_Y's avatar
        Kelly_Y
        Icon for Microsoft rankMicrosoft

        Thank you, rgrisi

         

        ColumbiaLion23 ivelin_tanev Hi!  You can either submit the information from edge://workspaces-internals/ to the team via feedback through the browser ("..." menu > Help and feedback > Send feedback) or you can send it to me via direct message on Tech Community.  Thanks! 

         

        -Kelly

  • JayceonJonas's avatar
    JayceonJonas
    Copper Contributor

    I'm experiencing an issue with the workspaces menu in Microsoft Teams. Whenever I try to access it, I receive an error message stating, "Error: Unable to load workspaces." This problem is quite frustrating as I rely on this feature for seamless collaboration and organization within Teams. It's especially concerning because Microsoft has recently enabled this feature by default for all users, and I was hoping to test it before rolling it out via Group Policy Objects (GPO).

    • Kelly_Y's avatar
      Kelly_Y
      Icon for Microsoft rankMicrosoft

      JayceonJonas Hello - Can you send a screenshot of the issue in Microsoft Teams?  Thanks! 

       

      -Kelly

      • Maurice_Jutten's avatar
        Maurice_Jutten
        Copper Contributor
        Similar issue here.
        Workspaces was working perfectly... since a week the error keeps showing up. Whether I'm on home on work network. With or without VPN connection.

        I was testing this.
        moved favorites to workspace.
        And now I just want to revert back ... and keep my favorites. get them all back into the old situation

        need some help either to resolve the issue or export favorites
  • Answered's avatar
    Answered
    Copper Contributor

    rgrisi try visiting:

     

    edge://settings/profiles

     

    Click on Sign Out.

    And Sign-in again.

     

    This fixed the issue for me as I was getting errors earlier, and can now see my all my Workspaces properly.

     

    Hope this fixes the issue for you too. 🙂

  • Maurice_Jutten's avatar
    Maurice_Jutten
    Copper Contributor
    I quit Workspace.
    Could be a usefull feature. But this is not stable.

    twice I lost the workspaces , which is not that bad, but all the favorites that were there and connected to the workspace are no longer accesable.

    Last time I moved the Favorites back to the main EDGE version (non workspace... )
    But they disappeared.

    Deleted all workspaces ! And rebuilding my favorites.
    lets stick with the old way of working.... that at least worked.
  • TrevorSleight's avatar
    TrevorSleight
    Copper Contributor
    I'm a first-time Microsoft Edge user and I am immediately experiencing this problem. I am completely unable to use Workspaces despite the fixes that I'm trying. When I pull up the Workspaces window, it usually gives me an error, and when it doesn't, it crashes the browser.
    This isn't a good first impression of this browser for me. Might as well go back to OperaGX if this just isn't being fixed.

Resources