Replies: 3 comments 3 replies
-
I first started getting new and unexpected entries in the log file at 2025-02-23 01:48 UTC+1. A huge amount (6514, to be exact) of these:
Then, it terminated and restarted, after which a very high amount of changes were received:
All of the following "Downloading: " log entries were related to Microsoft OneNote notebooks (and ".one" file name specs), which are weird beasts. Many of them failed verification, as is quite normal for these weird entities. I haven't had them mentioned in the logs for a long time, as I don't really use them much (therefore, no changes). Starting approximately 2025-02-23 02:17 UTC+1, I started getting this error:
The application was running as a user service unit via systemd, and kept restarting every 30 seconds or so. When I noticed the problem many hours later, I shallowly read the description of issue #3115 and suspected it was relevant. The drive ID was not 15 chars, however. After pulling the latest master revision and compiling from source, I started getting the message
So far, the discussions I've seen mentioning this root ID issue, have been related to problems with downloading shared items. The question on my mind right now is whether the initial symptoms and the non-unique account root ID situation, are potentially related in any way, or if they are more likely two separate incidents. I don't really have any shared items added to my own OneDrive root, and I cannot say for sure whether the root ID issue is new or not. I only observed this when using a new build with this check added. Side note: I spun up a Windows VM this evening, running the official Windows OneDrive client, and that too got >100k changes and used half an eternity processing them. I found no abnormal or unexpected changes, and my (shallow) impression is that this must have been caused by a change or bug in the service or in the API. EDIT: By the way, I did try reauthenticating, after getting the root ID error. Unfortunately, no change. |
Beta Was this translation helpful? Give feedback.
-
@vikingtiger |
Beta Was this translation helpful? Give feedback.
-
@nathan-gs There are 2 issues relating to this Microsoft change:
Please can you help get some traction here! |
Beta Was this translation helpful? Give feedback.
-
If your client will not operate due to this message, please seek support from Microsoft. You can do this in the following ways:
More details of the impact can be found in this GitHub Bug Report: OneDrive/onedrive-api-docs#1891
UNVERIFIED
Additionally, re-authentication of your client may work, attempt aThis does not fix the situation.--reauth
to return to a working operational state.Important
Please note, this is not a bug with this client. This is not an issue that this project can solve.
Beta Was this translation helpful? Give feedback.
All reactions