Forum Discussion

Anonymous's avatar
Anonymous
Not applicable
1 year ago
Solved

OneLake Explorer crashes after login

Hi all

 

We have set up OneLake Explorer for more than 10 users and it has worked, but on one User it crashes everytime when he logs into the app.

 

What caught my eye was this error in debug.log:


2025-02-18 11:17:47.4170 f117abd2-7898-45a4-8a87-c16a40fb5cbb 32880 10 ERROR|Initialization of core failed: Microsoft.OneLake.FileExplorer.Common.Exceptions.LakeStorageErrorException: User details not found for user id Redacted USERID (NotFound)

 

Does someone know what could be the problem? The user is configured same as all of our Users.

 

Here is the whole debug.log

 

 

 

2025-02-18 11:17:38.9497 00000000-0000-0000-0000-000000000000 32880     1  INFO|Get Registry value for Diagnostics-EnableDebug
2025-02-18 11:17:38.9774 00000000-0000-0000-0000-000000000000 32880     1  INFO|Debug logging switch is disabled by default.
2025-02-18 11:17:38.9914 00000000-0000-0000-0000-000000000000 32880     1  INFO|Args: 
2025-02-18 11:17:39.0942 00000000-0000-0000-0000-000000000000 32880     1  INFO|Application version: 1.0.13.0
2025-02-18 11:17:39.1149 00000000-0000-0000-0000-000000000000 32880     1  INFO|Another instance running: False
2025-02-18 11:17:39.1220 00000000-0000-0000-0000-000000000000 32880     1  INFO|OneLake file explorer Start.
2025-02-18 11:17:39.1220 00000000-0000-0000-0000-000000000000 32880     1  INFO|Reading startup configuration
2025-02-18 11:17:39.2103 00000000-0000-0000-0000-000000000000 32880     1  INFO|Initialized MSAL token cache under dir: C:\Users\XXX\AppData\Local
2025-02-18 11:17:39.2497 00000000-0000-0000-0000-000000000000 32880     1  INFO|Creating core
2025-02-18 11:17:39.2696 00000000-0000-0000-0000-000000000000 32880     1  INFO|Processor:12. ConnectionLimit: 144. Upload: 24/48.
2025-02-18 11:17:39.2696 00000000-0000-0000-0000-000000000000 32880     1  INFO|UploadBufferChunkSize: 8388608
2025-02-18 11:17:39.3908 00000000-0000-0000-0000-000000000000 32880     1  INFO|FEATURE_SYNC_OFFLINE_CHANGES: False
2025-02-18 11:17:39.4906 00000000-0000-0000-0000-000000000000 32880     1  INFO|Login token requires refresh: []  [18.02.2025 10:17:39 +00:00].
2025-02-18 11:17:39.4906 00000000-0000-0000-0000-000000000000 32880     1  INFO|Login token requires refresh: []  [18.02.2025 10:17:39 +00:00]. Refreshing
2025-02-18 11:17:46.9169 f117abd2-7898-45a4-8a87-c16a40fb5cbb 32880     5  INFO|Initializing application
2025-02-18 11:17:47.3205 f117abd2-7898-45a4-8a87-c16a40fb5cbb 32880    10  INFO|Initializing core in regular mode
2025-02-18 11:17:47.3217 f117abd2-7898-45a4-8a87-c16a40fb5cbb 32880    10  INFO|Fetching artifacts list
2025-02-18 11:17:47.4066 f117abd2-7898-45a4-8a87-c16a40fb5cbb 32880    10 ERROR|Response Received [ID:XXXX ] [RAID:XXXX ] status: NotFound [404]. GET https://api.onelake.fabric.microsoft.com/?comp=list
2025-02-18 11:17:47.4170 f117abd2-7898-45a4-8a87-c16a40fb5cbb 32880    10 ERROR|Initialization of core failed: Microsoft.OneLake.FileExplorer.Common.Exceptions.LakeStorageErrorException: User details not found for user id XXXX (NotFound)
   at Microsoft.OneLake.FileExplorer.Common.Operations.OneLakeOperationsExtensions.ReadLakeResponse[T](HttpResponseMessage response, Boolean parseXml)
   at Microsoft.OneLake.FileExplorer.Common.Operations.OneLakeArtifactOperations.ListWorkspacesAsync(String oneLakeEndPoint)+MoveNext()
   at Microsoft.OneLake.FileExplorer.Common.Operations.OneLakeArtifactOperations.ListWorkspacesAsync(String oneLakeEndPoint)+System.Threading.Tasks.Sources.IValueTaskSource<System.Boolean>.GetResult()
   at Microsoft.OneLake.FileExplorer.Common.Operations.OneLakeArtifactOperations.ListWorkspacesFlatAsync(String oneLakeEndPoint)+MoveNext()
   at Microsoft.OneLake.FileExplorer.Common.Operations.OneLakeArtifactOperations.ListWorkspacesFlatAsync(String oneLakeEndPoint)+MoveNext()
   at Microsoft.OneLake.FileExplorer.Common.Operations.OneLakeArtifactOperations.ListWorkspacesFlatAsync(String oneLakeEndPoint)+System.Threading.Tasks.Sources.IValueTaskSource<System.Boolean>.GetResult()
   at Microsoft.OneLake.FileExplorer.Common.ArtifactsProvider.OneLakeArtifactsProvider.RefreshRoot()
   at Microsoft.OneLake.FileExplorer.Common.ArtifactsProvider.OneLakeArtifactsProvider.RefreshRoot()
   at Microsoft.OneLake.FileExplorer.Common.ArtifactsProvider.OneLakeArtifactsProvider.RefreshRootAndArtifacts()
   at Microsoft.OneLake.FileExplorer.Core.SyncEngineCore.RegularStartAsync()
   at Microsoft.OneLake.FileExplorer.Core.SyncEngineCore.Start(Boolean requestingBackgroundServiceOnly)
2025-02-18 11:17:47.4170 f117abd2-7898-45a4-8a87-c16a40fb5cbb 32880    10  INFO|Stopping. Is running: True
2025-02-18 11:17:47.4170 f117abd2-7898-45a4-8a87-c16a40fb5cbb 32880    10  INFO|Stopping engine.
2025-02-18 11:17:47.4170 f117abd2-7898-45a4-8a87-c16a40fb5cbb 32880    10  INFO|Received stop event to watch file system changes
2025-02-18 11:17:47.4170 f117abd2-7898-45a4-8a87-c16a40fb5cbb 32880    10  INFO|Stopped watching file system changes
2025-02-18 11:17:47.4170 f117abd2-7898-45a4-8a87-c16a40fb5cbb 32880    10  INFO|Stopped all file system watcher tasks successfully
2025-02-18 11:17:47.4170 f117abd2-7898-45a4-8a87-c16a40fb5cbb 32880     5  INFO|Unregistering cf callbacks
2025-02-18 11:17:47.4170 f117abd2-7898-45a4-8a87-c16a40fb5cbb 32880     5  WARN|Could not disconnect the sync root callbacks, hr -2147024809. Continuing
2025-02-18 11:17:47.4170 f117abd2-7898-45a4-8a87-c16a40fb5cbb 32880     5  INFO|Skipping unregistration of sync root manager
2025-02-18 11:17:47.4170 00000000-0000-0000-0000-000000000000 32880     5  INFO|Stopping. Is running: False
2025-02-18 11:17:47.4170 00000000-0000-0000-0000-000000000000 32880     1  INFO|Exiting application
2025-02-18 11:17:47.4376 00000000-0000-0000-0000-000000000000 32880     1  INFO|Sync root is not in registered state.
2025-02-18 11:17:47.4376 00000000-0000-0000-0000-000000000000 32880     1  INFO|OneLake file explorer End.

 

 

 

  • Anonymous's avatar
    Anonymous
    1 year ago

    Hi Anonymous,

    Thanks for reaching out to the Microsoft fabric community forum.

     

    It looks like your oneLake explorer is failing to initialize for a specific user because it cannot find the user details in the OneLake service. The error message shows that the user authentication is failing, and the service does not recognize the user’s identity. As the same setup works for other users, it suggests that the issue is specific to this user’s identity or permissions in OneLake. Please check if the user account is properly provided in OneLake. The user may not have been correctly added to the necessary Fabric workspace or OneLake storage permissions. Also check if the user’s Azure AD token may be corrupted, expired, or missing necessary permissions for OneLake.

     

    I would also take a moment to thank nilendraFabric, for actively participating in the community forum and for the solutions you’ve been sharing in the community forum. Your contributions make a real difference.

     

    If I misunderstand your needs or you still have problems on it, please feel free to let us know.  

    Best Regards,
    Hammad.
    Community Support Team

     

    If this post helps then please mark it as a solution, so that other members find it more quickly.

    Thank you.

8 Replies

  • Hello Anonymous 

     

    try

     

    Delete the problematic user’s OneLake profile directory at `%USERPROFILE%\OneLake - Microsoft`.
    • Clear cached credentials via Windows Credential Manager for OneLake-related entries

    • Anonymous's avatar
      Anonymous
      Not applicable

      Hi nilendraFabric 

      Thank you for your answer. Unfortunately that did not help. 
      I deleted the Userprofile multiple times and rebooted the laptop but no success, I get same result. OneLake Explorer crashes immediately after user login.

      On the Windows Credential Managed I did not find any OneLake-related entries.

      • lukaszk_'s avatar
        lukaszk_
        Regular Visitor

        Hi, I have the same problem. Did you manage to fix it?

  • Anonymous's avatar
    Anonymous
    Not applicable

    Hi Anonymous,

    Thanks for reaching out to the Microsoft fabric community forum.

     

    It looks like your oneLake explorer is failing to initialize for a specific user because it cannot find the user details in the OneLake service. The error message shows that the user authentication is failing, and the service does not recognize the user’s identity. As the same setup works for other users, it suggests that the issue is specific to this user’s identity or permissions in OneLake. Please check if the user account is properly provided in OneLake. The user may not have been correctly added to the necessary Fabric workspace or OneLake storage permissions. Also check if the user’s Azure AD token may be corrupted, expired, or missing necessary permissions for OneLake.

     

    I would also take a moment to thank nilendraFabric, for actively participating in the community forum and for the solutions you’ve been sharing in the community forum. Your contributions make a real difference.

     

    If I misunderstand your needs or you still have problems on it, please feel free to let us know.  

    Best Regards,
    Hammad.
    Community Support Team

     

    If this post helps then please mark it as a solution, so that other members find it more quickly.

    Thank you.

    • Anonymous's avatar
      Anonymous
      Not applicable

      Hi Anonymous,

      May I ask if you have resolved this issue? If so, please mark the helpful reply and accept it as the solution. This will be helpful for other community members who have similar problems to solve it faster.

       

      Thank you.

  • Anonymous's avatar
    Anonymous
    Not applicable

    Hi Anonymous,

    As we haven’t heard back from you, so just following up to our previous message. I'd like to confirm if you've successfully resolved this issue or if you need further help.

    If yes, you are welcome to share your workaround and mark it as a solution so that other users can benefit as well. If you find a reply particularly helpful to you, you can also mark it as a solution.


    If you still have any questions or need more support, please feel free to let us know. We are more than happy to continue to help you.
    Thank you for your patience and look forward to hearing from you.

  • Anonymous's avatar
    Anonymous
    Not applicable

    Hi Anonymous,

    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. If my response has addressed your query, please accept it as a solution so that other community members can find it easily.


    Thank you.

  • Same here. I can install it, it asks to log in, and then it's nowhere to be seen. Tried to install it as admin, tried to delete the synced folder, to now avail. Very frustrating. Not good for product image.