Exchange 2010: Unable to open Exchange Management Console - Initialization Failed

Exchange 2010: Unable to open Exchange Management Console - Initialization Failed

  • Comments 34
  • Likes

Problem:  Exchange Management Console in Exchange 2010 will not open and references a server that is down or has been removed from the environment.

Error Verbiage: Initialization Failed

The following error occurred while attempting to connect to the specified Exchange server 'exchange.contoso.com':

The attempt to connect to http://exchange.contoso.com'/powershell using 'Kerberos' authentication failed: Connecting to the remote server failed with the following error message : WinRM cannot process the request. The following error occurred while using Kerberos  authentication: The network path was not found.

 

Resolutions:

Method 1:

  1. Close all MMC/EMC instances before proceeding.
  2. Open Registry Editor (regedit) as the user you run the EMC under.
  3. Go to
    HKEY_CURRENT_USER\SOFTWARE\Microsoft\ExchangeServer\v14\AdminTools
  4. Look for value NodeStructureSetting.
  5. If it is there, back it up and then remove it.

Method 2:

  1. Close all MMC/EMC Instances before proceeding.
  2. Open Powershell or Powershell IDE as the user you run the EMC under and execute the following command:.
  1. Remove-ItemProperty -Path HKCU:\Software\Microsoft\ExchangeServer\v14\AdminTools\ -Name NodeStructureSettings
  • Close Powershell

After performing either of the methods above to remove the registry entry you should be able to open the Exchange Management Console and it will discover another Exchange server and connect.

 

Comments
  • Perfect solution, spent more that 2 hours and finally found your post

    thanks

  • Thank you!! #1

  • You the man.. appreciate it

  • This steps I followed but did not resolved the problem, I have the Exchange server 2010 installed on the same server running active directory on server 2008 r2 standard edition.

    It is really frustrating and why can't Microsoft give us a hint , i have lost my 2nd job interview just to this problem

  • Sometimes cache credentials also gave the same error.

  • Worked perfect for me!

  • You are a god among men! Worked perfectly.

  • Worked ! :) thanks

  • Worked for me too. Many thanks.

    Any idea how it got broken?

  • @John Healy

    You either have removed a server from the environment, have a server offline, or a server is inaccessible due to stopped services or.local firewall.

  • Worked Great :)

  • Thanks a lot... :)

  • Quick and Eazy.  The way I like it!!!  Thanks

  • Such a Great Post !

  • Had the same issue on a fresh install. After I started to replicate Free & Busy and OAB sys files from my 2003 exchange.  I could no longer connect from 2010 exchange to the 2003 exchange.  Tried deleting the mentioned reg key it did not work for me>> Any ideas??

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment