none
Broken ECP and Powershell after Failed CU9 RRS feed

  • Question

  • 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??)

    Thursday, June 25, 2015 5:07 PM

Answers

  • Hello,

    This didn't work.

    I re-ran the CU patch and had to monitor the services.

    Every-time the patch completes the step it sets the exchange services to "Disabled" then the patch complains it couldn't start the services....

    So you have to babysit the patch and keep setting the services to manual.

    • Marked as answer by Tularis1 Thursday, July 16, 2015 2:50 PM
    Thursday, July 16, 2015 2:50 PM

All replies

  • Hi,

    Please open IIS manager and check the following settings:

    1. In IIS manager > Default Web Site, make sure Anonymous Authentication is Enabled in Authentication.

    2. Confirm that "Require SSL" is checked on the SSL Settings of the default web site.

    3. If all configurations are correct, please restart IIS service by running IISReset from a command prompt window.

    Regards,


    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Winnie Liang
    TechNet Community Support

    Monday, June 29, 2015 3:25 AM
    Moderator
  • Hello,

    This didn't work.

    I re-ran the CU patch and had to monitor the services.

    Every-time the patch completes the step it sets the exchange services to "Disabled" then the patch complains it couldn't start the services....

    So you have to babysit the patch and keep setting the services to manual.

    • Marked as answer by Tularis1 Thursday, July 16, 2015 2:50 PM
    Thursday, July 16, 2015 2:50 PM
  • Here is the solution:

    Go to Exchange Installed folder

    1)On the affected Exchange 2016 CU5 server go to Installed directory C:\Program Files\Microsoft\Exchange Server\V15\FrontEnd\HttpProxy and rename the file SharedWebConfig.config to SharedWebConfig.config_OLD

    2) Copy the SharedWebConfig.config from a Exchange 2016 CU5 server which do not have the issues to that folder on the affected Server

    3) On the affected Exchange 2016 CU5 server go to Installed directory C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess and rename the file SharedWebConfig.config to SharedWebConfig.config_OLD

    4) Copy the SharedWebConfig.config from a Exchange 2016 CU5 server which do not have the issues to that folder on the affected Server

    5) Open Command Prompt as adminstrator  and run iisreset


    Vishal Bajpai MCP,MCSA,MCTS,CCNA,CCNP


    Saturday, January 20, 2018 3:51 PM