Forum Discussion
SharePoint Caching Problems with Lists
Hi group, I did some digging on this and believe I have found the issue for our tenant.
The OneDrive client appears to be syncing Lists from SharePoint Online (et. al) by default. To verify this is what is happening, you can perform the following steps:
- Open Dev Tools on Chrome (F12)
- Navigate to "Network"
- Select "Fetch/XHR" as type
- Enter "RenderListDataAsStream" as a filter
- Attempt to sort a list that is cached
The results should show "localhost", "::1", or an equivalent loopback address under the "Remote Address" column.
You can then use resmon, netstat or Get-NetTCPConnection/Get-Process to find the IM of the process name and ID of the port being used for these local XHR requests to the RenderListDataAsStream endpoint. In my scenario, it was port 42050 (probably randomized), which was shown in use by the Microsoft.SharePoint.exe application, located under \AppData\Local\Microsoft\OneDrive\<version number>.
If you see this behavior, you can attempt to mitigate the caching by:
- Setting
[HKLM\SOFTWARE\Policies\Microsoft\OneDrive] "DisableNucleusSync" = "dword:1"
(per MS Docs - Use Group Policy to control Lists sync settings ) - Rebooting machine, or force closing the task with IM of "Microsoft.SharePoint.exe".
- Reloading the list page (may need to force-refresh).
This appears to be working on our test machines (all Modern UI queries are forced to use the SPO servers instead of OD), but I'm not entirely sure of the effect this setting could have in regards to SP, OneDrive, Teams, etc - so it should probably be used with caution.
Hopefully this helps your tenants as well. Good luck!
robertchamplin I did just re-report this issue to Microsoft (via ticket #28786964), and the tech informed me that this issue has been reported by others, they are aware of the issue and working toward a resolution. They did tie my tenant to this issue, so I should be seeing updates related to this issue in our Admin Message Center as well (I just got off the phone so it's too early to expect to see anything yet).
They did, however, acknowledge that there was an issue.
- CJohnston71 Thanks for the update and for running this to ground!
- I'm not holding my breath on this; hoping for some successful resolution. The link to THIS thread has also been provided (at the Microsoft tech's request) and attached to my ticket.
- Hi, did they give you a resolution on this? We're experiencing the same issues but lately, MS Support has unable to resolve any of the issues we've reported
- No, MS was quick to say it was something that they'll report to development, and they expect the issue to "go away" with updates. Did you try the suggestion proposed by jnlce on 1/13? I've got just a small handful of users impacted by this, and they've just sort of been quietly dealing with it. I haven't tested out jnlce's suggestions yet, but that did seem like potentially the best find so far.
- Jnlce's suggestion is the best so far - it only addresses the problem for individual machines, and only if your security settings allow it.
