XtremeOwnage

This issue popped up for me over the weekend. Again, my code has not been changed in years. And nothing would have been changed at 1:30am Sat/Sun.

X-AnchorMailbox did resolve most of my issues a few days ago. Now, If I can get this error (also new) ironed out, I will be doing good again. The specified...

The issues "magically" self-resolved for me... for this issue "because the ExchangePrincipal object contains outdated information. The mailbox may have been moved recently."

As an update on my end, The issues "magically" came back over the weekend. I am reopening my ticket with Microsoft support. Edit- Issue is also affected a few other...

For the other error, the resolution is pretty simple. This is from Microsoft: if (attendee.Id != null) { attendee.Id = null; } Here is the explanation from the Microsoft support...

To summarize this entire issue (And provide resolutions for both exceptions) Occasionally in office 365, mailboxes move between forests. This causes a lot of issues. For the first exception "ExchangeImpersonation...

Here is a partial config from mine. I did get temp sensing working. Not a clue if it is accurate or not, however, the provided value matches what I would...

I managed to grab a stack trace for this issue. Essentially a fresh installation. Added a single channel subscription... and... ``` [37:0x4fd7800] 450983 ms: Mark-sweep 4046.7 (4136.7) -> 4044.1 (4143.4)...

Well..... Issues for this problem were originally opened in 2017. Its now close to Q2 2022, and this is still an issue on the latest .net 6.0 release. https://github.com/dotnet/project-system/issues/1409 https://github.com/dotnet/project-system/issues/2934...

That was actually pretty easy. I would still recommend eventually updating the documentation to have a few additional pointers to that page. As well, perhaps a tad more documentation around...