Forum Discussion
Suspicious events
RrrrowsdowerThis also appears to have started in less than 24 hours after installing the Exchange zero day patch for me as well.
Jason284 - Did you get any update from Microsoft on your case?
DhruvaKudvaUnfortunately no, not a word yet. Although I have noticed that there are a lot of people getting these exact errors and it seems to correlate with installing the Exchange zero day patch last week from what I can tell. It's frustrating there hasn't been any response from Microsoft on this.
From what I understand, this could be due to Mailbox Anchoring. When an External connection is made (OWA) Exchange looks for the users mailbox on the same node as the Transport node.
If the users mailbox is not the same node as the transport node, it throws this error.
We get this error as well and each time it occurs, the users mailbox is NOT on the same node as the transport. Doesnt impact anything as the DAG handles this but it does seem to throw this error each time.
