Forum Discussion
Onelake Explorer Not Syncing to Fabric
Good morning, Fabric Community,
I'm currently utilizing OneLake File Explorer across multiple lab PCs, all configured identically. Each PC runs scripts that generate JSON files, which are then stored in various locations, including a Lakehouse via OneLake Explorer, to integrate results into Fabric.
While this setup functions seamlessly on most machines, a few PCs exhibit persistent issues. Specifically, OneLake Explorer ceases to sync new files to Fabric unless I uninstall and reinstall the application. Post-reinstallation, synchronization resumes temporarily—typically for two to three cycles—before the problem recurs.
Notably, the scripts execute correctly, and the JSON files are saved in the appropriate local directories. However, these files fail to appear within the Fabric environment. Given the uniform configuration across all PCs, this inconsistency is perplexing.
Troubleshooting Steps Undertaken:
Verified that all PCs are running the same version of OneLake Explorer.
Ensured that file and folder names do not contain Windows reserved characters or other restricted naming conventions.
Confirmed that files are not being written to locations lacking appropriate write permissions, such as the root of a workspace.
Despite these efforts, the issue persists on certain machines. I would greatly appreciate any insights or suggestions from the community to resolve this synchronization challenge.
Thank you in advance for your assistance!
Anonymous
OneLake File Explorer sync problems
Hi aeelissa,
We regret the inconvenience caused and acknowledge your requirements. Please consider raising a Microsoft support ticket for further investigation. You can explain all the troubleshooting steps you have taken to help them better understand the issue.You can create a Microsoft support ticket with the help of the link below:
https://learn.microsoft.com/en-us/power-bi/support/create-support-ticketIf this helps, please accept it as a solution and drop a "Kudos" so other members can find it more easily.
Thank you.
15 Replies
v-ssriganeshCommunity Support
Hi aeelissa,
Thank you for reaching out to the Microsoft Fabric Community Forum.
Based on your description, the issue seems related to OneLake File Explorer’s sync process failing on specific machines after a few cycles, potentially due to local cache corruption, network issues, or authentication problems. Here are some steps to try:- Review OneLake File Explorer logs on affected PCs for sync errors like network timeouts or authentication issues and share specific errors for targeted advice.
- Exit OneLake File Explorer, back up and delete its cache folder, restart the app, and test if syncing resumes consistently.
- Ensure a stable network connection on affected PCs and confirm OneLake’s server is accessible, manually triggering sync if needed.
- Sign out of OneLake File Explorer, sign back in with your Microsoft Entra ID account, and verify Contributor or higher permissions to the workspace and Lakehouse.
If this information is helpful, please “Accept as solution” and give a "kudos" to assist other community members in resolving similar issues more efficiently.
Thank you.
- burakkaragoz
Super User
Hi aeelissa ,
Hello, the synchronization problem you are experiencing seems really annoying. Especially if all machines are configured in the same way, it makes it even more difficult to find the source of the problem. I would like to make some additional suggestions below:
OneLake Explorer Logs: It may be useful to examine the OneLake Explorer log files on the problem machines to see if there are any error messages or warnings during synchronization. Logs are usually located in the application folder or under %AppData%.
Services running in the background: Check that OneLake Explorer's services running in the background are working properly. In particular, the status of the relevant services can be reviewed via Windows Services (Services.msc).
Antivirus / Security Software: Some security software can block write operations to the file system or synchronization services. It may be useful to temporarily disable and test antivirus software on the problem machines.
User Authorizations: Although the configurations are the same, user accounts may have different permissions. Make sure that the necessary permissions are complete, especially for write/sync operations.
File Watcher: The system APIs that OneLake Explorer uses to detect file changes may not work properly on some machines. In this case, it may be necessary to test whether changes to the file system are actually detected.
Updates and Known Bugs: It is worth taking a look at Microsoft's list of known issues with Fabric and OneLake Explorer. Perhaps this is a known bug in a specific release.
- v-ssriganesh
Hi aeelissa,
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 and give a 'Kudos' so other members can easily find it.
Thank you.Hi v-ssriganesh , I will have the chance to test it next week, I will keep you posted 😉
Thanks a lot!!Hello v-ssriganesh burakkaragoz just tested your suggestions, it's still the same 😕
- v-ssriganesh
Hi aeelissa,
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.
Hi v-ssriganesh , unfortunatly, it is still working 😕
- v-ssriganesh
Hi aeelissa,
We regret the inconvenience caused and acknowledge your requirements. Please consider raising a Microsoft support ticket for further investigation. You can explain all the troubleshooting steps you have taken to help them better understand the issue.You can create a Microsoft support ticket with the help of the link below:
https://learn.microsoft.com/en-us/power-bi/support/create-support-ticketIf this helps, please accept it as a solution and drop a "Kudos" so other members can find it more easily.
Thank you.
