none
Exchange 2010 can't find GC?

    Question

  • We have one 2003 Domain Controller and a Server 2008 R2 Exchange 2010 Server.  The Exchange System Attendant service will not start.  When I open up Active Directory Users & Computers on the Exchange Server (not a DC) - go to Domain Controllers, select properties of the DC and select the "Member of" tab - it tells me that the GC is not available.

    I added a 2nd DC - this time a 2008 R2 Server and GC.  When this Server is on, the Exchange Server can find the GC and the Exchange System Attendant service can start.  When this Server is off - it can't.

    The GC seems to replicate fine from the 2003 Server to the 2008.

    How do I troubleshoot the 2003 Global Catalog problem?

    Tuesday, September 11, 2012 2:59 PM

Answers

  • Do you have other DCs than those two? I ask because neither of them is
    a PDC FSMO role holder according to that information.Yes, that is weird that it doesn't show up as a PDC.  FILESERVER is the 2003 DC and holds all roles.  CPIDC is the 2008 R2 Server I created to troubleshoot.

    I ended up calling Microsoft on this issue and we found that the 2003 Server was not set to register it's connection's address in DNS.  As soon as we turned this on, everything worked correctly.

    • Marked as answer by CTS-Tech Wednesday, September 12, 2012 2:57 PM
    Wednesday, September 12, 2012 2:57 PM

All replies

  • I have checked to see if any DCs are excluded in Exchange - no exclusions:

    http://support.microsoft.com/kb/298879

    We don't want to keep the 2008 R2 DC (for now).  We want the 2003 DC Global Catalog working correctly with Exchange 2010.

    Tuesday, September 11, 2012 3:08 PM
  • On Tue, 11 Sep 2012 15:08:51 +0000, CTS-Tech wrote:
     
    >I have checked to see if any DCs are excluded in Exchange - no exclusions:
    >
    >http://support.microsoft.com/kb/298879
    >
    >We don't want to keep the 2008 R2 DC (for now). We want the 2003 DC Global Catalog working correctly with Exchange 2010.
     
    Check your Application event log for event id 2080. What DCs show up
    in the list? What's different with the 2003 DC?
     
    Log Name: Application
    Source: MSExchange ADAccess
    Date: 9/11/2012 5:28:15 PM
    Event ID: 2080
    Task Category: Topology
    Level: Information
    Keywords: Classic
    User: N/A
    Computer: XXXX.XXXX.com
    Description:
    Process STORE.EXE (PID=4460). Exchange Active Directory Provider has
    discovered the following servers with the following characteristics:
    (Server name | Roles | Enabled | Reachability | Synchronized | GC
    capable | PDC | SACL right | Critical Data | Netlogon | OS Version)
    In-site:
    XXXX.XXXX.com CDG 1 7 7 1 0 1 1 7 1
    XXXX.XXXX.com CDG 1 7 7 1 0 1 1 7 1
    Out-of-site:
    XXXX.XXXX.com CDG 1 7 7 1 0 1 1 7 1
     
    ---
    Rich Matheisen
    MCSE+I, Exchange MVP
     

    --- Rich Matheisen MCSE+I, Exchange MVP
    Tuesday, September 11, 2012 9:41 PM
  • Check your Application event log for event id 2080. What DCs show up
    in the list? What's different with the 2003 DC?

    When 2nd DC is off:

    FILESERVER.CPI CDG 1 7 7 1 0 1 1 7 1
    CPIDC.CPI          CDG 1 0 0 1 0 0 0 0 0

    When 2nd DC is on:

    FILESERVER.CPI CDG 1 7 7 1 0 1 1 7 1
    CPIDC.CPI          CDG 1 7 7 1 0 1 1 7 1

    Tuesday, September 11, 2012 10:52 PM
  • On Tue, 11 Sep 2012 22:52:59 +0000, CTS-Tech wrote:
     
    >Check your Application event log for event id 2080. What DCs show up in the list? What's different with the 2003 DC?
    >
    >When 2nd DC is off:
    >
    >FILESERVER.CPI CDG 1 7 7 1 0 1 1 7 1 CPIDC.CPI CDG 1 0 0 1 0 0 0 0 0
    >
    >When 2nd DC is on:
    >
    >FILESERVER.CPI CDG 1 7 7 1 0 1 1 7 1 CPIDC.CPI CDG 1 7 7 1 0 1 1 7 1
     
    Do you have other DCs than those two? I ask because neither of them is
    a PDC FSMO role holder according to that information.
     
    Both of the DC's appear to be GCs, but that doesn't necessarily mean
    they're both functional.
     
    If CPIDC.PCI is the 2003 DC you might want to remove it as a GC and
    reboot it. After a few minutes promote it back to a GC and let it
    replicate, then reboot it again.
     
    If you still have problems after that try running ExBPA and see what
    it has to say. DCDIAG and NETDIAG may also shed some light on your
    problem, but i don't think it's an Exchange problem.
     
    ---
    Rich Matheisen
    MCSE+I, Exchange MVP
     

    --- Rich Matheisen MCSE+I, Exchange MVP
    Wednesday, September 12, 2012 2:02 AM
  • Do you have other DCs than those two? I ask because neither of them is
    a PDC FSMO role holder according to that information.Yes, that is weird that it doesn't show up as a PDC.  FILESERVER is the 2003 DC and holds all roles.  CPIDC is the 2008 R2 Server I created to troubleshoot.

    I ended up calling Microsoft on this issue and we found that the 2003 Server was not set to register it's connection's address in DNS.  As soon as we turned this on, everything worked correctly.

    • Marked as answer by CTS-Tech Wednesday, September 12, 2012 2:57 PM
    Wednesday, September 12, 2012 2:57 PM