User Profile
Megasware128
Copper Contributor
Joined 3 years ago
User Widgets
Recent Discussions
Re: OneDrive Client Sync Issues: Unable to Retrieve DefaultDocumentLibrary ID
Deleted which entry should be OneDrive? It seems to be in alphabetical order but as you can see there is no OneDrive at O: Also, I must mention I've tried these steps before and my issue is consistent across Windows devices.Re: OneDrive Client Sync Issues: Unable to Retrieve DefaultDocumentLibrary ID
Hi Deleted, Thank you for responding. 1. Yes, I'm able to use the web interface and also the Android app normally. 2. I don't think so, although it is part of a couple of Microsoft Entra Tenants. 3. I don't visually get an error. It will be stuck in a sign in loop like shown in the screenshot. I noticed in fiddler this login loop is basically OneDrive trying to retrieve my DefaultDocumentLibrary ID but failing to do so. The error response is also in one of the screenshots:OneDrive Client Sync Issues: Unable to Retrieve DefaultDocumentLibrary ID
Hello everyone, I've been facing issues with my personal OneDrive account for the past two months, where the OneDrive client gets stuck during the initial synchronization. After linking my account to the client, the client restarts at some point and appears to be stuck in a visual login loop. This issue persists across different devices, which leads me to believe it's likely a server-side issue. The problem started around two months ago, and after attempting several standard troubleshooting steps (such as resetting, re-linking, reinstalling, and checking for updates), I opened a support ticket. However, due to a lengthy response time on the support ticket which eventually escalated without resolution, I decided to do some debugging on my end. Through this process, I discovered that the issue occurs during the initialization of the MS-FILESYNC protocol, where a series of HTTP, GET, and POST communications known as the first run are made to sync the client with the protocol server and authenticate the user among other steps. Specifically, the issue arises at the step where a GET request is made to retrieve the DefaultDocumentLibrary ID, as documented https://learn.microsoft.com/en-us/openspecs/sharepoint_protocols/ms-filesync/c8ce8b37-f197-401c-8f9b-ae53dfdddd55. The specific problem seems to lie in step 3 of the protocol, where the DefaultDocumentLibrary ID is being retrieved. The error message I receive is: {"error":{"code":"-2146232832, Microsoft.SharePoint.SPException","message":{"lang":"en-US","value":"A default document library could not be found in this site."}}}. I attempted to bypass this issue by writing a YARP-based proxy that returns a fabricated DefaultDocumentLibrary ID. I also tried using some GUIDs retrieved from Microsoft Graph, which I thought could be substitutes for the DocumentLibrary ID, but none of these attempts were successful. Eventually, I hit a roadblock at step 5, retrieving the user's personal site global client policy, likely because the document library doesn't actually exist. I also looked into a friend's OneDrive account (which dates back to 2006) and found that they have a DefaultDocumentLibrary, and interestingly, the API indicates that it was created on the 28th of September this year. On the other hand, my girlfriend, who has a fairly new Microsoft account, doesn't appear to have a my.microsoftpersonalcontent.com environment. I am unsure how to interpret these findings, but they might indicate some server-side changes or inconsistencies. I have a substantial history with my current account and I also subscribe to Microsoft 365, utilizing around 30% of the 1 TB data allocation. Creating a new account is not a viable option as it would be highly inconvenient. Hence, I am keen on finding a solution that will resolve the syncing issue with my existing account. I'm looking for advice on how to resolve this issue. Is there a way to create a DefaultDocumentLibrary for my personal OneDrive account, or is there another way to approach this problem? Any help would be greatly appreciated. Thank you!
