Hello,
I am installing Exchange 2013 as part of a 2007 Upgrade / Migration.
Everything has installed OK but halfway through the installation for CU9 it failed (I didn't note down the error :()
Now after a reboot all of the exchange services were set to "disabled", after bringing them all up if I try to access the ECP I get;
Server Error in '/ecp' Application. Configuration Error Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately. Parser Error Message: Could not load file or assembly 'Microsoft.Exchange.Clients.Strings, Version=15.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified. Source Error: Line 42: the compiler. All assemblies in the GAC and owa\bin are referenced automatically. Line 43: --> Line 44: <add assembly="Microsoft.Exchange.Clients.Strings, Version=15.0.0.0, Culture=neutral, publicKeyToken=31bf3856ad364e35" /> Line 45: <add assembly="Microsoft.Exchange.Data.Directory, Version=15.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" /> Line 46: <add assembly="Microsoft.Exchange.Clients.Common, Version=15.0.0.0,Culture=neutral, publicKeyToken=31bf3856ad364e35" /> Source File: C:\Program Files\Microsoft\Exchange Server\V15\FrontEnd\HttpProxy\ecp\web.config Line: 44 Assembly Load Trace: The following information can be helpful to determine why the assembly 'Microsoft.Exchange.Clients.Strings, Version=15.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' could not be loaded. WRN: Assembly binding logging is turned OFF. To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1. Note: There is some performance penalty associated with assembly bind failure logging. To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog]. Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.0.30319.34248
And If I try to open an exchange power shell I get.
VERBOSE: Connecting to Mail-2012.Domain.local. New-PSSession : [mail-2012.Domain.local] Connecting to remote server mail-2012.Domain.local failed with the following error message : The WinRM client cannot process the request. It cannot determine the content type of the HTTP response from the destination computer. The content type is absent or invalid. For more information, see the about_Remote_Troubleshooting Help topic. At line:1 char:1+ New-PSSession -ConnectionURI "$connectionUri" -ConfigurationName Microsoft.Excha ...+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~+ CategoryInfo : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin gTransportException+ FullyQualifiedErrorId : -2144108297,PSSessionOpenFailed VERBOSE: Connecting to Mail-2012.Domain.local. New-PSSession : [mail-2012.Domain.local] Connecting to remote server mail-2012.Domain.local failed with the following error message : The WinRM client cannot process the request. It cannot determine the content type of the HTTP response from the destination computer. The content type is absent or invalid. For more information, see the about_Remote_Troubleshooting Help topic. At line:1 char:1+ New-PSSession -ConnectionURI "$connectionUri" -ConfigurationName Microsoft.Excha ...+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~+ CategoryInfo : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin gTransportException+ FullyQualifiedErrorId : -2144108297,PSSessionOpenFailed VERBOSE: Connecting to Mail-2012.Domain.local. New-PSSession : [mail-2012.Domain.local] Connecting to remote server mail-2012.Domain.local failed with the following error message : The WinRM client cannot process the request. It cannot determine the content type of the HTTP response from the destination computer. The content type is absent or invalid. For more information, see the about_Remote_Troubleshooting Help topic. At line:1 char:1+ New-PSSession -ConnectionURI "$connectionUri" -ConfigurationName Microsoft.Excha ...+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~+ CategoryInfo : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin gTransportException+ FullyQualifiedErrorId : -2144108297,PSSessionOpenFailed VERBOSE: Connecting to Mail-2012.Domain.local. New-PSSession : [mail-2012.Domain.local] Connecting to remote server mail-2012.Domain.local failed with the following error message : The WinRM client cannot process the request. It cannot determine the content type of the HTTP response from the destination computer. The content type is absent or invalid. For more information, see the about_Remote_Troubleshooting Help topic. At line:1 char:1+ New-PSSession -ConnectionURI "$connectionUri" -ConfigurationName Microsoft.Excha ...+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~+ CategoryInfo : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin gTransportException+ FullyQualifiedErrorId : -2144108297,PSSessionOpenFailed VERBOSE: Connecting to Mail-2012.Domain.local. New-PSSession : [mail-2012.Domain.local] Connecting to remote server mail-2012.Domain.local failed with the following error message : The WinRM client cannot process the request. It cannot determine the content type of the HTTP response from the destination computer. The content type is absent or invalid. For more information, see the about_Remote_Troubleshooting Help topic. At line:1 char:1+ New-PSSession -ConnectionURI "$connectionUri" -ConfigurationName Microsoft.Excha ...+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~+ CategoryInfo : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin gTransportException+ FullyQualifiedErrorId : -2144108297,PSSessionOpenFailed Failed to connect to an Exchange server in the current site.
As the ECP and PowerShell have both broken I'm at a bit of a loss..
Has anyone see this before? does anyone know how to fix this?
(Who Knew powershell uses HTTP??)