Event ID/Source search
Keyword searchExample: Windows cannot unload your registry file
Event ID: 8027 Source: MSADC
The LDAP Bind to the global catalog on <server name> for distinguished name '<recipient name>' was unsuccessful. The Directory returned error:[0x<value>] <value> The Active Directory Server that the ADC binds to must be a global catalog. Please, correct the configuration, or promote the Active Directory Server to be a global catalog.
|English: Request a translation of the event description in plain English.|
|Concepts to understand:|
What is the role of the Global Catalog?
What is LDAP?
What is the role of the Microsoft Active Directory Connector (MSADC) ?
The ADC (Active Directory Connector) is logging this error because it cannot locate a global catalog server in its own domain. The ADC tries to locate another global catalog server in another domain, so this event may give the wrong impression that the actual global catalog server is down. See ME251468, ME264145 and MSEX2K3DB for additional information about this event.
We were getting this on the domain controller that we installed the ADC on. Apparently the ADC automatically creates a connection agreement when it is installed. The connection agreement that it created was trying to replicate using port 3268 (the global catalog port) to our Infrastructure Master. This server was not a Global Catalog because you don't want to have a GC on your Infrastructure Master. We manually updated the connection agreement to point to a DC that was also a GC and then stopped/restarted the ADC to fix the problem."
Either promote the Active Directory Server that the Connection Agreement points to, to a global catalog, or modify the Connection Agreement to point to a global catalog.
|Private comment: Subscribers only. See example of private comment|
|Links: ME251468, ME264145, MSEX2K3DB, MSADC Events|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
Send comments or solutions
- Notify me when updated