Teams renderer error

Hello Opeyemi,

My name is EngineTyme, an Independent Advisor and a Microsoft user like you and I would be glad to help you.

I apologize for the inconvenience you are experiencing with Teams and your class notebooks. The error message teamsNotebookView.notebookRendererError indicates an issue with rendering the notebook within Teams. Let’s troubleshoot this together:

1. Clear Browser Cache and Cookies: If you’re using Teams on the web, try clearing your browser cache and cookies. This often resolves rendering errors. Additionally, clear the cache in the Teams desktop app. You can find detailed steps in this support article.

If you using the Classic Teams, you can follow the steps below to clear Teams cache:

1. If Teams is still running, right-click the Teams icon on the taskbar, and then select Quit.
2. Open the Run dialog box by pressing the Windows logo key +R.
3. In the Run dialog box, enter the following path, and then select OK: %appdata%\Microsoft\Teams
4. Delete all files and folders in the directory. 5.Restart Teams.

Clear the Teams client cache: https://learn.microsoft.com/microsoftteams/troubleshoot/teams-administration/clear-teams-cache

“Give back to the Community. Help the next person who has this issue by indicating if this reply solved your problem. Click Yes or No below. “

Please let me know if you have any questions or concern.

Best regards, EngineTyme.

Hello EngineTyme,

Thank you for assisting me on this issue. I appreciate you.

I have tried these steps but the issue persists.

Other suggestions are appreciated.

Hello, i experience this issue also on Android and my Teachers and Classmates on Ipads too. Do you have Solution for that too?

Best regards
Chris

Hello Opeyemi,

Please, can you state the device on which you experience this and what Office 365 license do you have?

Best regards,

Hi!

We have a similar problem.

In a web-browser we can se that Onenote(Sharepoint) is getting the authentication error. Seems like the authentication request is coming from Microsoft own IP.

We have succeeded to solve this, by bypassing MFA from Microsoft own IP scope.

This has to be a bug, but we haven't seen any information around this....