Solved

Exchange 2010 Services not starting after replacing/upgrading Domain Controllers

Posted on 2013-02-06
4
934 Views
Last Modified: 2013-02-11
After upgrading our domain controllers to Windows Server 2012 our Exchange 2010 server was not allowing connections.  After a reboot it would not allow services to start and would not login completely, it would hang during login process.  After investigation we found Exchnage services trying were start and stopping.  Below are the erros and I'll post what we did to fix in an answer after this post.

Log Name:      Application
Source:        MSExchange ADAccess
Date:          2/5/2013 10:35:41 PM
Event ID:      2114
Task Category: Topology
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      EXCHANGE2010.domain.com
Description:
Process MSEXCHANGEADTOPOLOGYSERVICE.EXE (PID=3164). Topology discovery failed, error 0x80040a02 (DSC_E_NO_SUITABLE_CDC). Look up the Lightweight Directory Access Protocol (LDAP) error code specified in the event description. To do this, use Microsoft Knowledge Base article 218185, "Microsoft LDAP Error Codes." Use the information in that article to learn more about the cause and resolution to this error. Use the Ping or PathPing command-line tools to test network connectivity to local domain controllers.

Log Name:      Application
Source:        MSExchange ADAccess
Date:          2/5/2013 10:35:41 PM
Event ID:      2080
Task Category: Topology
Level:         Information
Keywords:      Classic
User:          N/A
Computer:      EXCHANGE2010.domain.com
Description:
Process MSEXCHANGEADTOPOLOGYSERVICE.EXE (PID=3164). 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:
old-dc1.domain.com      CDG 1 0 0 1 0 0 0 0 0
old-dc2.domain.com      CDG 1 0 0 1 0 0 0 0 0
 Out-of-site:


Log Name:      Application
Source:        MSExchange ADAccess
Date:          2/5/2013 10:35:41 PM
Event ID:      2102
Task Category: Topology
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      EXCHANGE2010.domain.com
Description:
Process MSEXCHANGEADTOPOLOGYSERVICE.EXE (PID=3164). All Domain Controller Servers in use are not responding:
old-dc1.domain.com
old-dc2.domain.com
0
Comment
Question by:NMGISupport
  • 2
  • 2
4 Comments
 
LVL 52

Expert Comment

by:Manpreet SIngh Khatra
Comment Utility
Was some changes done to DC's ?
Is Exchange able to communicate with DC on port 389a dn GC on 3268

- Rancy
0
 

Accepted Solution

by:
NMGISupport earned 0 total points
Comment Utility
To solve this we rebooted into safe mode and edited the registry keys for the domain controllers Exchange was trying to use.  To do this search the registry for the FQDN of the old Domain Controllers (picture with example attached).  This will be under HKLM\SYSTEM\ControlSet001\services\MSExchange ADAccess\Profiles\Default\UserDC1, UserDC2, UserGC1, and UserGC2.  We modified these entries with the correct Dcomain Controllers FQDN and rebooted.  Everything worked at that point.

Hope this helps someone!
0
 
LVL 52

Expert Comment

by:Manpreet SIngh Khatra
Comment Utility
Dont mind but you shouldnt be hardcoding Exchnage to use some specific DC as this will arise whenever this new server added will have issues or will be restarted

- Rancy
0
 

Author Closing Comment

by:NMGISupport
Comment Utility
To help others!
0

Featured Post

Windows Server 2016: All you need to know

Learn about Hyper-V features that increase functionality and usability of Microsoft Windows Server 2016. Also, throughout this eBook, you’ll find some basic PowerShell examples that will help you leverage the scripts in your environments!

Join & Write a Comment

Resolve DNS query failed errors for Exchange
Easy CSR creation in Exchange 2007,2010 and 2013
In this video we show how to create a Resource Mailbox in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: Navigate to the Recipients >> Resources tab.: "Recipients" is our default selection …
In this video we show how to create an email address policy in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.:  First we need to log into the Exchange Admin Center. Navigate to the Mail Flow…

762 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

7 Experts available now in Live!

Get 1:1 Help Now