| Event Id | 1349 |
| Source | MSExchangeDS |
| Description | The GUID on server ServerD has changed from 8ab25beb042fd311af6c00c04f68de18 ServerD to 54242885302fd311af6e00c04f68de18. This will cause all replicas to be resynced from scratch. |
| Event Information | According to Microsoft: CAUSE: When there are a lot of changes to be replicated, it may take multiple calls to transfer the data between the servers. If during the multiple calls there is a remote procedure call (RPC) error, the global universal identification (GUID) on the REPS-FROM for the calling server is reset to the invocation ID of the local server. The next replication cycle detects the GUID change and logs the 1349 error. This logic error causes unnecessary naming context resynchronizations. Naming context resynchronizations in a large Exchange Server environment can cause performance degradation. RESOLUTION: To resolve this problem, obtain the latest service pack for Exchange Server 5.5.Microsoft has confirmed that this is a problem in Microsoft Exchange Server version 5.5. This problem was first corrected in Exchange Server 5.5 Service Pack 4. |
| Reference Links | XADM: Directory Logging 1349 GUID Changed Events When RPC Errors Occur XADM: Two Sites with the Same Organization and Site Name May Join Together |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.