Forum Discussion
Syncing SharePoint Libraries Repair Question
We have a SharePoint Library that will not stop syncing. We have paused and stopped syncing other librarires succesfully but this one library does not want to go away. I follow the same steps to remove it but it stays where it is at. I assume it could be a cache issue, but my question is if I repair the library won't all of my other libraries need to be rescynced as well? Are there any other thoughts on the potential problem?
No error messages are received either.
11 Replies
- JOSEPH OWINOCopper Contributor
After doing extensive research and trying to figure out why this issue wouldnt go away for my client. I think I know why.
1. Microsoft says you can only sync 20000 items in total across all synchronized libraries (this includes files and folders) Read here https://support.microsoft.com/en-us/kb/2933738
2. The issue I have with this is because its a very small number. I have a client who has 4 sharepoint sites and each has about 3 document libraries just to avoid the issue of the 5000 items/document library. Aaargghhh
3. Try reducing the amount of libraries you are syncing and it might stop.
- AnonymousIn my experience, recent versions of the OD4B sync client (still groove.exe), will only repair "broken" libraries, so any libraries that have sync'ed OK, shouldn't be touched.
Just today I hit a library that wouldn't stop syncing, nor could I disconnect it or two other libraries from the same SPO site... Had to uninstall the client, flush out the cache and credentials and re-install the client. Still waiting to hear back if that's resolved it...- JOSEPH OWINOCopper Contributor
Read this link, I think its an issue with the limit to the number of items you are allowed to sync
https://support.microsoft.com/en-us/kb/2933738
- AnonymousHi Joseph,
no, that's the first thing I checked. This particular user had 7 libraries being synced, none were near the 5000 per library limit and the total was well under 20K.
Even after stopping the sync of the four "OK" libraries, I was still unable to successfully sync the "broken" library, nor was I able to stop syncing the three remaining libraries. Even after reboots.
What's a pain, is that you end up with the OD4B (groove.exe) credential/data cache and the Office Upload Center credential/data cache. MS really need to finish unifying all these bits.
Thanks
Craig
- DeletedUser_6884Copper ContributorYes that also has been my experience, having to flush the cache and credentials and re-install. Which this causes all of the libraries to stop syncing in my experience. This is a pain as some of my users have 10s and 20s of libraries from different sites/projects that they are actively using and syncing.
My hope is that this all goes away when the NGSC gets the document library functionality.
P.S Sorry for the double post, for some reason I am still experiencing a "Double Account Syndrome"
- My guess is that if you repair that specific document library, you should not have to resync the other libraries again. By the way: is this SPO? If so, open a support ticket.
- DeletedUser_6884Copper Contributor
Not really a support question (yet), I was asking in regards to how the sync client is supposed to behave, I was just giving some context to what was happening when I saw this behaviour.
Previously when I ran a repair it unsynced all of my libraries. If that is the behaviour that I am supposed to see then there is no problem. If that isn't the behaviour then a support ticket is definitely in need :)
Yes it is SPO
- JOSEPH OWINOCopper Contributor
I would really love an answer to this issue. We are having the same challenge.