Apr 19 2020 10:29 PM
Hello,
I'm having an issue in Teams and OneNote. Specifically, I have a OneNote that's shared as a tab within a Team. Changes have been made from within OneNote App on a Team Member's computer. Some, but not all, of those changes are displayed when accessing the OneNote via Teams. This issue persists even after a force refresh is triggered. What's more odd, OneNote in the cloud is consistent with OneNote found in Teams Tab. Nothing suggests that the sync isn't working from the user's OneNote client app, yet only some of the changes make it to the cloud and Teams. No errors or unsynchronized notes messages come up.
Can anyone help!?
Apr 27 2020 11:35 PM
sort of same issue here.
- OneNote app and OneNote web is showing the correct (synced) content
- OneNote teams app for other team members is showing the correct (synced) content
- But my own onenote teams tab is showing old (not synced) content.
How can I force a resync of the OneNote teams tab?
Apr 28 2020 08:06 PM
@Roel Teeuwen - That's my EXACT situation. We can't be the only ones.
Apr 28 2020 11:30 PM
@ParagonRob I thought I fixed it by manually deleting the OneNote tab from the teams channel and adding it again. That did the trick, but only one time, new changes after that are again not showing in the onenote tab (but are indeed showing in the onenote web and onenote 2016 desktop app)...
Apr 28 2020 11:42 PM - edited Apr 28 2020 11:46 PM
@ParagonRob @Roel Teeuwen We're also experiencing different issues with OneNote that can't really be explained. And it's frustrating, both from an end-user perspective and as an administrator. I'm afraid that raising a ticket with Microsoft Premier support isn't the solution either. But when reading about your specific problem I believe it's due to the extensive increase in use of cloud services with the following 'temporary feature adjustments' that's been made to select capabilities within Microsoft 365. These where published a month ago and for the OneNote part it said:
Nov 12 2020 02:42 AM
Solution@ParagonRob probably too late (I hope you got it resolved), but I noticed the same problem this morning. To get it working again:
not sure if it will do the trick for you, but it did for me, as well as for a colleague of mine, who had the exact same problem. I don't know WHY it was broken, and I don't know if my fix will be permanent. I hope so
Nov 18 2020 09:36 AM
@Koen Daems I've run into the same issue. I did some playing around with the particular page open in multiple formats (Web-based, Desktop, and Teams) and while the Desktop would update without issue, I found the Web-based to be slow, and Teams to be unresponsive until I tried to make an update, whether it was adding a new row to a table or adding text, suddenly all of the updates from the other locations would refresh. FYI, your fix/workaround did work for me as well, albeit not ideal due to needing the workbook open in multiple windows.
Dec 01 2020 05:13 AM
Worked for me too, thanks. Unfortunate we have to do this.
Dec 02 2020 07:41 AM
@DPasiechnyk thanks for the feedback. The reason I opened explicitly so many windows, is that I use many different accounts in parallel (several customer and partner contexts). To make sure I was actually looking/working in the proper books, with the proper accounts, I opened it that way. If less manipulations is possible and works for you - top! :thumbs_up:
Dec 02 2020 07:44 AM
Dec 08 2020 02:44 PM
@Koen Daems I tried this method for our user in the hopes that it would work for us (seeing as it seemed to work for others), but we weren't as lucky. Some more tinkering around led me to see a new sync status error message in the OneNote 2016 app.
I checked the library and found that the 'Require Check Out' setting (under Versioning settings) was indeed enabled (I was a bit gobsmacked here, tbh. Perhaps someone other administrator went in to enable this).
Anyway, long story short, disabling the checkout requirement fixed the issue for us. On occasion, the OneNote tab in Teams may need to be "reloaded" to force display new changes, but other than that, there hasn't syncing hasn't been a problem anymore. I hope this can help others who still have this issue.