Home > Event Id > Cdg 1 7 7 1 0 1 1 7 1

Cdg 1 7 7 1 0 1 1 7 1

Contents

This lets you keep Exchange from using domain controllers dedicated to other applications. Connect with top rated Experts 11 Experts available now in Live! Please check the settings I have suggested and let me know. DC-B passed test ObjectsReplicated Test omitted by user request: OutboundSecureChannels Starting test: Replications * Replications Check *

DSAccess identifies the full topology and compiles a list of working domain controllers and a list of working GCs. Topology discovery failed due to LDAP_SERVER_DOWN error". EventID: 0xC0001390 Time Generated: 03/07/2012 10:32:37 Event String: The DFS Replication service CENTRAL-AD2 passed test VerifyReferences Running partition tests on : ForestDnsZones Starting test: CrossRefValidation ......................... http://www.microsoft.com/technet/support/ee/transform.aspx?ProdName=Exchange&ProdVer=8.0&EvtID=2080&EvtSrc=MSExchangeADAccess

Cdg 1 7 7 1 0 1 1 7 1

Exchange Active Directory Provider has discovered the following servers with the following characteristics: (Server name | Roles | Enabled | Reachability | Synchronized | GC capable | PDC | SACL right Disable 3rd party firewall products on GC make sure there is a GC in the AD site your exchange server is in Sites and service not configured - Need to configure CENTRAL-AD1 passed test MachineAccount Starting test: Services ......................... EventID: 0x00009018 Time Generated: 03/07/2012 18:17:50 Event String: The following fatal alert

Additional Information: Error: 1722 (The RPC server is unavailable.) Connection ID: 720F1DB0-6D6C-40EF-904F-0107ECC98E9F Replication Additional Information: Error: 1722 (The RPC server is unavailable.) Connection ID: 8853FFF0-21A5-4510-B638-751D9C696AB6 Replication Information about the 2080 event starts on page 53. Msexchange Adaccess 2114 EventID: 0xC0001390 Time Generated: 03/07/2012 09:09:32 Event String: The DFS Replication service

CENTRAL-AD2 passed test NetLogons Starting test: Advertising ......................... DomainDnsZones passed test CheckSDRefDom Running partition tests on : Schema Starting test: CrossRefValidation ......................... DC-B passed test Connectivity Doing primary tests Testing server: LondonOffice\DC-B Starting test: Advertising The DC DC-B is advertising itself as a here Exchange Active Directory Provider has discovered the following servers with the following characteristics: (Server name | Roles | Enabled | Reachability | Synchronized | GC capable | PDC | SACL right

CENTRAL-AD1 passed test systemlog Starting test: VerifyReferences ......................... Event Id 2142 Exchange 2013 We had to manually add in the servers to the policy on the domain controllers (DC1, DC2, old_DC1) To manually add the servers to the policy: Start > Administrative Tools > Partner DNS Address: DC-A.company.local Optional data if available: Partner WINS Address: DC-A The system object reference (msDFSR-ComputerReferenceBL) CN=426aae45-50fc-48d7-b1a5-951eb6e821cc,CN=Topology,CN=mena replication group 2,CN=DFSR-GlobalSettings,CN=System,DC=company,DC=local and backlink on CN=DC-B,OU=Domain Controllers,DC=company,DC=local are correct.

Msexchange Adaccess 4127

Join 234 other followers CategoriesCategories Select Category .net 2003 2003 2007 2008 2008 R2 2010 Active Directory ActiveSync ADFS BPOS Certification Eseutil Exchange Exchange 2010 Exchange 2013 Exchange 2016 Hyper-v IIS However, be aware that re-running PrepareAD may only resolve the issue temporarily as any bad Group Policies may find themselves being re-applied in about 15min so fixing the actual source of Cdg 1 7 7 1 0 1 1 7 1 CENTRAL-AD2 passed test NCSecDesc Starting test: NetLogons ......................... Exchange 2010 Sacl Right Missing The Exchange 2007 and 2010 servers, with the exception of one Exchange 2007 mailbox server, were throwing errors such as these: Event Type: Error Event Source: MSExchange ADAccess Event Category: Topology

To Isolate such scenarios below are the steps that have to checked. 1: Check the network or DNS issues. 2: Obviously they must all be pointing to an internal DNS server, Join Now For immediate help use Live now! Or possibly a configuration issue on the network stack (IP/DNS/etc); maybe someone even powered your GC off much to your dismay. We have 3 AD sites in CA (LAX, SFO, and IRV) and none of those DC's show up in my event 2080 as being out of site DC's. Topology Discovery Failed, Error 0x80040a02

An additional note here is if you're utilizing AD Split permissions with Exchange, there may be additional precautions to be taken before running PrepareAD  again. CENTRAL-AD1 passed test KnowsOfRoleHolders Starting test: RidManager ......................... DC-B passed test NetLogons Starting test: ObjectsReplicated DC-B is in domain DC=company,DC=local Checking for CN=DC-B,OU=Domain Controllers,DC=company,DC=local in domain DC=company,DC=local on Any ideas on what to troubleshoot here? 0 Comment Question by:mkllpit Facebook Twitter LinkedIn https://www.experts-exchange.com/questions/28368058/Exchange-2010-Event-ID-2080-Topology-issue.htmlcopy LVL 6 Best Solution byaschaef217 This article has a good description of how Exchange DA Discovery

Checked everything as stated and all was correct. Dcdiag If the topology is hard coded, the discovery process stops. What is the role of the Netlogon share?

Schema passed test CheckSDRefDom Starting test: CrossRefValidation .........................

By default, the Exchange Servers (Exchange 2007 and 2010) group and Exchange Enterprise Servers (Exchange 2003) group are added to this right in the Default Domain Controllers Policy. ForestDnsZones passed test CrossRefValidation Running partition tests on : DomainDnsZones Starting test: CheckSDRefDom ......................... The service will retry the connection periodically. ForestDnsZones passed test CheckSDRefDom Running partition tests on : DomainDnsZones Starting test: CrossRefValidation .........................

I forced it off, booted to Safe Mode, and saw the above errors in the Event Log - which were preventing the server from booting up. We also found that his one working Exchange 2007 server had been added to the Exchange Domain Servers group (again, Exchange 2003 group) which is then part of the EES group. CENTRAL-AD2 passed test Advertising Starting test: KnowsOfRoleHolders ......................... Then everything was fine, we could apply updates & reboot the DCs with no problem.

It will only use local site DC/GC. cancersa.local passed test FsmoCheck C:\Documents and Settings\Administrator.CANCERSA> (in reply to Mad_deamon) Post #: 3 RE: Event ID 2080 Domain Controller used - 21.Oct.2007 8:36:18 AM Mad_deamon Posts: 19