MS Exchange 2010 management tools - EMC (Exchange Management Console) and EMS (Exchange Management Shell) no longer working

Hi guys,

This issue has baffled me for ages, all of the sudden my MS Exchange 2010 management tools - EMC (Exchange Management Console)  and EMS (Exchange Management Shell) - have stopped working, both fail when I try to access them - below is the error. Also worth noting no changes had been made to the server prior to the issue occurring.
I have also noticed when I go to Control Panel - Programs & Features - and click on Change I also get an error, I am not sure if and how maybe the whole installation has corrupted.
My emails are still working.

We are running via the following setup:
- Exchange 2010 SP3 UR18 is running on Windows Server 2008 R2 SP1
- We are also running in hybrid mode - majority of our mailboxes have been migrated to Office 365 however there are around 10 mailboxes left.

Thank you all in advance!
Mike




ERROR:

TryLoadExchangeTypes : Exception calling "TryLoadExchangeTypes" with "2" argument(s): "Could not load file or assembly
'file:///C:\Program Files\Microsoft\Exchange Server\V14\Bin\Microsoft.Exchange.Data.Providers.dll' or one of its depend
encies. The module was expected to contain an assembly manifest."
At C:\Program Files\Microsoft\Exchange Server\V14\bin\RemoteExchange.ps1:75 char:92
+ $typeLoadResult = [Microsoft.Exchange.Configuration.Tasks.TaskHelper]::TryLoadExchangeTypes <<<< ($ManagementPath, $t
ypeListToCheck)
    + CategoryInfo          : NotSpecified: (:) [], MethodInvocationException
    + FullyQualifiedErrorId : DotNetMethodException

The Exchange types file wasn't loaded because not all of the required files could be found.


VERBOSE: Connecting to OUR SERVER.OUR DOMAIN.local
[OUR SERVER.OUR DOMAIN.local] Processing data from remote server failed with the following error message: The type
initializer for 'Microsoft.Exchange.Configuration.Authorization.InitialSessionStateBuilder' threw an exception. For mor
e information, see the about_Remote_Troubleshooting Help topic.
    + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [], PSRemotingTransportExc
   eption
    + FullyQualifiedErrorId : PSSessionOpenFailed
VERBOSE: Connecting to OUR SERVER.local
[OUR SERVER.OUR DOMAIN.local] Processing data from remote server failed with the following error message: The type
initializer for 'Microsoft.Exchange.Configuration.Authorization.InitialSessionStateBuilder' threw an exception. For mor
e information, see the about_Remote_Troubleshooting Help topic.
    + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [], PSRemotingTransportExc
   eption
    + FullyQualifiedErrorId : PSSessionOpenFailed
VERBOSE: Connecting to OUR SERVER.local
[OUR SERVER.OUR DOMAIN.local] Processing data from remote server failed with the following error message: The type
initializer for 'Microsoft.Exchange.Configuration.Authorization.InitialSessionStateBuilder' threw an exception. For mor
e information, see the about_Remote_Troubleshooting Help topic.
    + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [], PSRemotingTransportExc
   eption
    + FullyQualifiedErrorId : PSSessionOpenFailed
Failed to connect to an Exchange server in the current site.
Enter the server FQDN where you want to connect.: OUR SERVER.OUR DOMAIN.local
Mirza BegicAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

MASEE Solution Guide - Technical Dept HeadCommented:
Mirza BegicAuthor Commented:
@ MAS

Thanks for your prompt reply however I did try the EMTshooter before with no success, it did not report on what the exact problem is nor did it recommend any solutions.

I have executed EMTshooter 1 more time to see if it will provide more information on the error or solution but unfortunately the outcome was the same as before, see below:


EMTshooter RESULT:
'Welcome to the Exchange Management Troubleshooter!

We recommend that you run the troubleshooter after making changes to
IIS to ensure that connectivity to Exchange Powershell is unaffected.

Checking IIS Service...

Checking the Exchange Install Path variable...

Checking the Powershell Virtual Directory...

Checking the Powershell vdir SSL setting...

Checking the Powershell vdir path setting...

Checking HTTP Port 80...

Checking HTTP Port 80 Host Name...

Testing for errors...

VERBOSE: Connecting to OUR_SERVER.OUR_DOMAIN.local


new-pssession : [OUR_SERVER.OUR_DOMAIN.local] Processing data from remote server OUR_SERVER.OUR_DOMAIN.local fai
At C:\Users\MY_USERNAME\Documents\EMTshooter\EMTConnectFunctions.ps1:177 char:15
+ ...  $session = new-pssession -connectionURI "http://$fqdn/powershell?ser ...
+                 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotingT
    + FullyQualifiedErrorId : IncorrectProtocolVersion,PSSessionOpenFailed
The Exchange Management Troubleshooter successfully completed connecting to:

OUR_SERVER.OUR_DOMAIN.local

Failed to connect to any Exchange Server in the current site.

Problem found:

Looking for error...

Unknown Error

After each error is resolved, close this window and re-run the tool to check for additional problems.'
Mirza BegicAuthor Commented:
If I click on CHANGE while Microsoft Exchange Server 2010 is highlighted in Programs and Features I get the error attached
Capture.PNG
Maximize Customer Retention with Superior Service

The IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy for valuable how-to assets including sample agreements, checklists, flowcharts, and more to help build customer satisfaction and retention.

Mirza BegicAuthor Commented:
When I try to uninstall Exchange 2010 management tools via Command Prompt I get the error attached
MASEE Solution Guide - Technical Dept HeadCommented:
You can use this command in Powershell to get access to Exchange Shell
Add-PSSnapin Microsoft.Exchange.Management.PowerShell.SnapIn;

Open in new window

Mirza BegicAuthor Commented:
Thx, tried already with no luck:
PS C:\Windows\system32> Add-PSSnapin Microsoft.Exchange.Management.PowerShell.SnapIn;
Add-PSSnapin : The Windows PowerShell snap-in 'Microsoft.Exchange.Management.PowerShell.SnapIn' is not installed on this computer.
At line:1 char:1
+ Add-PSSnapin Microsoft.Exchange.Management.PowerShell.SnapIn;
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidArgument: (Microsoft.Excha...werShell.SnapIn:String) [Add-PSSnapin], PSArgumentException
    + FullyQualifiedErrorId : AddPSSnapInRead,Microsoft.PowerShell.Commands.AddPSSnapinCommand


I've also tried Add-PSSnapIn Microsoft.Exchange.Management.PowerShell.E2010 - also got an error:
PS C:\Windows\system32> Add-PSSnapin Microsoft.Exchange.Management.PowerShell.E2010
Add-PSSnapin : The type initializer for 'Microsoft.Exchange.Management.PowerShell.CmdletConfigurationEntries' threw an exception.
At line:1 char:1
+ Add-PSSnapin Microsoft.Exchange.Management.PowerShell.E2010
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [Add-PSSnapin], TypeInitializationException
    + FullyQualifiedErrorId : System.TypeInitializationException,Microsoft.PowerShell.Commands.AddPSSnapinCommand
Radhakrishnan RSenior Technical LeadCommented:
Hi,

By looking this error, i could think of some powershel path in IIS virtual directory may be wrong . Could you this path?

Open IIS and locate the powershll virtual directory, make sure the path is correct . I.e - C:\Program Files\Microsoft\Exchange Server\Vxx\ClientAccess\PowerShell.

Also, what's the output you are getting for 'Get-ExchangeServer' ?
Sudeep SharmaTechnical DesignerCommented:
Have you tried restarting the World Wide Web Publishing Service and check if that has any effect on the issue?

Thanks,
Sudeep
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.