Build a great reporting interface using Splunk, one of the leaders in the Security Information and Event Management (SIEM) field, linking the collected Windows events to www.eventid.net. The EventId.Net for Splunk Add-on assumes that Splunk is collecting information from Windows servers and workstation via the Splunk Universal Forwarder.
The target object "<object>" was modified after the source object "<object>". Consequently the following set of updates will not be applied to the target object. If this warning persists make sure that the time is correctly set on both the source and target servers.
|English: Request a translation of the event description in plain English.|
As per Microsoft: "This issue can occur if there is a time-skew between the servers from which the ADC is reading the information. The ADC reads information from a domain controller (or global catalog) and an Exchange Server. If these servers have a time skew between them, this issue can occur. Also, if a target object is modified manually between replication cycles, this issue might occur". See MSEX2K3DB for additional information about this event.
This problem was occurring during my testing phase of an Exchange 2003 deployment. The fix was to verify the ADC connections are pointing to a domain controller that is a Global Catalog. After manually setting this DC as a GC, the ADC.EXE error stopped and replication worked fine. Using the Wizard to create the ADC connection agreements did not alert me that I was pointing to a DC that was not a Global Catalog server.
|Private comment: Subscribers only. See example of private comment|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
Send comments or solutions
- Notify me when updated