“An Error Caused A Change In The Current Set Of Domain Controllers” Error While Launching Exchange 2010 Management Console…

MS Exchange

While working with Exchange 2010 at a customer site, I came across the error message below while launching the Exchange 2010 Management Console (EMC) and navigating to Recipient Configuration –> Mailbox.

An error caused a change in the current set of domain controllers. It was running the command “Get-Recipient –PropertySet ConsoleLargeSet –ResultSize ‘1000’ –SortBy DisplayName –RecipientType “UserMailbox”

Error in EMC 2010

AD guys confirmed that one or more domain controllers were decommissioned before I tried launching the EMC. Few GCs were online while I received the error as well. After searching on the internet and finding number of “fixes”, the one that worked for me was to delete the “Exchange Management Console” file from my profile.

The file is located in C:UsersUserAppDataRoamingMicrosoftMMC

EMC Path

After deleting the file, I was able to work with the EMC without any errors!

Other Popular Articles


MS Exchange

Scripting Agent Initialization Failed: “File is not found” Error During Exchange 2016 Setup

MS Exchange

EAC Access While Co-Existing Exchange 2013 With 2010

MS Exchange

Delete All Calendar Entries In An Exchange 2010 Mailbox

18 thoughts on ““An Error Caused A Change In The Current Set Of Domain Controllers” Error While Launching Exchange 2010 Management Console…”

  1. This has been bugging me for a while… with me thinking I had a serious problem w/ my Exchange server not reading information from AD correctly. This article was 100% accurate and solved my (non)issue.
    Thanks.

    Reply
  2. this totally worked for me. I was in the middle of a Blackberry Enterprise Server migration, while issuing the "Get-MailboxDatabase | Add-ADPermission…" which had already been issued, when the command returned a warning and EMC>Recipient Configuration>Mailbox stopped working.

    Reply
  3. I have faced this problem before but with Exchange 2007 Management console . some Googling I found the solutions – the same as yours – but unfortunately I still didn't know the cause !! . Do you ?

    Reply

Leave a Comment