Microsoft KB Archive/246214
Article ID: 246214
Article Last Modified on 10/26/2006
- Microsoft Exchange Server 5.5 Standard Edition
This article was previously published under Q246214
Servers incorrectly log the following event in the event log:
Event ID: 1349 Source: MSExchangeDS
The GUID on server (Server Name) has changed from a86a49730326d3118fb80000f806a267 (Server Name) to 0a964fd8e0d7d2118faf0000f806a267 (Server Name). This causes all replicas to be resynced from scratch.
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.
To resolve this problem, obtain the latest service pack for Exchange Server 5.5. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
191014 XGEN: How to Obtain the latest Exchange Server 5.5 Service Pack
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.
Not all 1349 errors in the event log are a issue. If the server is re-installed, it gets a new GUID and this should be expected behavior. There is a way to make sure that a server has the exact symptom described in the "Symptoms" section. In the 1349 event ID, the GUIDs are logged. With this information, you can check to see if the first GUID is the same as the invocation-id attribute on the directory object. If the first GUID is the same as the invocation-id of the server reporting the 1349 error, contact Microsoft Support for the fix that resolves this issue.
Keywords: kbbug kbexchange550presp4fix kbexchange550sp4fix kbfix kbqfe KB246214