Solved

Exchange 2010 Services not starting after replacing/upgrading Domain Controllers

Posted on 2013-02-06
4
959 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
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
  • 2
4 Comments
 
LVL 52

Expert Comment

by:Manpreet SIngh Khatra
ID: 38859545
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
ID: 38859815
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
ID: 38859871
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
ID: 38875420
To help others!
0

Featured Post

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article will help to fix the below errors for MS Exchange Server 2013 I. Certificate error "name on the security certificate is invalid or does not match the name of the site" II. Out of Office not working III. Make Internal URLs and Externa…
Group policies can be applied selectively to specific devices with the help of groups. Utilising this, it is possible to phase-in group policies, over a period of time, by randomly adding non-members user or computers at a set interval, to a group f…
In this Micro Video tutorial you will learn the basics about Database Availability Groups and How to configure one using a live Exchange Server Environment. The video tutorial explains the basics of the Exchange server Database Availability grou…
Microsoft Active Directory, the widely used IT infrastructure, is known for its high risk of credential theft. The best way to test your Active Directory’s vulnerabilities to pass-the-ticket, pass-the-hash, privilege escalation, and malware attacks …

724 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