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.
Could not import the entry '<entry name>' into the directory server '<directory name>' in the second attempt. (Connection Agreement '<connection agreement>' #1536)
|English: Request a translation of the event description in plain English.|
|Concepts to understand:|
What is the role of the Microsoft Active Directory Connector (MSADC) ?
See ME291385 for information about this event.
As per Microsoft: "This event indicates that the Active Directory Connector (ADC) was unable to import the entry (specified in the Description section of the event) on the second attempt. There may be other related events (8270, 8109, 8021, etc.) preceding or succeeding this event that indicate what the underlying cause for this failure is". See MSEX2K3DB and ME893608 for information on this event.
Elliott Fields Jr
To resolve this issue, use the Exchange Server 5.5 Administrator program to check the permissions on the site object, and then look to see if the account that is listed on the Exchange 5.5 tab of the recipient Connection Agreement has Admin privileges for the site object. See ME329047 for further details.
|Private comment: Subscribers only. See example of private comment|
|Links: ME291385, ME329047, ME893608, MSEX2K3DB|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
Send comments or solutions
- Notify me when updated