<

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x

Exchange 2010 EMC/EMS not working after applying to Exchange 2010 SP3.

Published on
5,026 Points
1,826 Views
2 Endorsements
Last Modified:
Recently, I was updating the Rollup 7 update on our Exchange 2010 SP3 server. When I opened the Exchange Management Console (EMC) on the on-premise server, I got the following error message:

[Server FQDN] Processing data from remote server failed with the following error message: Could not load type 'Microsoft.Exchange.Data.AutoDiscoverSmtpDomain' from assembly 'Microsoft.Exchange.Data, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'. For more information, see the about_Remote_Troubleshooting Help topic. It was running the command 'Discover-ExchangeServer -UseWIA $true -SuppressError $true -CurrentVersion 'Version 14.3 (Build 123.4)''.

This article shows how I applied some troubleshooting to get to the final solution.
 
  1. I tried to open the EMC but it failed with the error
  2. I then tried using the Exchange management shell, but it failed to open with above error.
  3. Verified that wsman and kerbauth modules are showing up in native mode on PowerShell virtual directory.

    WSMan provides methods and properties used to create a session. Kerberos is used to authenticate the user connecting using remote PowerShell. If either was absent, the server would fail to process data from remote sources.
  4. I verified that wsman and kerbauth module were not loaded on Default Web site level.
  5. I verified that wsman and kerbauth module were present in the global modules section of the C:\Windows\System32\Inetsrv\config\ApplicationHost.config file
  6. I checked event viewer and did not find any events related to the issue.
  7. I executed WinRM quickconfig in Windows PowerShell. WinRM quickconfig is a PowerShell command that analyzes and configures the WinRM service; WinRM allows you to then start remote computers and servers.
  8. I installed the WinRM IIS Extension. This allowed me to verify that my issue was the server itself and not something with the connection to it.
  9. I made a backup of AdminTools from registry path HKEY_CURRENT_USER\SOFTWARE\Microsoft\ExchangeServer\v14 and removed "NodeStructureSetting" value from AdminTools key.
  10. I then relaunched EMC but still the received the same error.
  11. Reverted the changes by importing the AdminTools again in registry.
  12. I then reinstalled Exchange 2010 SP3 Update Rollup 7 and rebooted the server.
After that, both the EMC and EMS started working.
 
2
Author:R--R
1 Comment
LVL 19

Author Comment

by:R--R
It was necessary to come to the conclusion. I mentioned what i did on the case.
0

Featured Post

Big Business Goals? Which KPIs Will Help You

The most successful MSPs rely on metrics – known as key performance indicators (KPIs) – for making informed decisions that help their businesses thrive, rather than just survive. This eBook provides an overview of the most important KPIs used by top MSPs.

how to add IIS SMTP to handle application/Scanner relays into office 365.
Whether it be Exchange Server Crash Issues, Dirty Shutdown Errors or Failed to mount error, Stellar Phoenix Mailbox Exchange Recovery has always got your back. With the help of its easy to understand user interface and 3 simple steps recovery proced…

Keep in touch with Experts Exchange

Tech news and trends delivered to your inbox every month