locked
Issue after upgrade to exchange 2010 sp3 RRS feed

  • Question

  • Hellou 

    After exchange 2010 sp3 update. Exchange is installed on Windows 2008 R2

    When I try to start exchange console or shell I receive the following error: 

    The attempt to connect to http://....local/PowerShell using "Kerberos" authentication failed: Connecting to remote server 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. 

    In Application log I have the following error:

    Log Name:      Application
    Source:        Microsoft-Windows-IIS-W3SVC-WP
    Date:          7/14/2020 8:10:47 PM
    Event ID:      2214
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      
    Description:
    The HTTP Filter DLL E:\Exchange\ClientAccess\owa\auth\owaauth.dll failed to load.  The data is the error.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Microsoft-Windows-IIS-W3SVC-WP" Guid="{670080D9-742A-4187-8D16-41143D1290BD}" EventSourceName="W3SVC-WP" />
        <EventID Qualifiers="49152">2214</EventID>
        <Version>0</Version>
        <Level>2</Level>
        <Task>0</Task>
        <Opcode>0</Opcode>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2020-07-14T17:10:47.000000000Z" />
        <EventRecordID>1130221</EventRecordID>
        <Correlation />
        <Execution ProcessID="0" ThreadID="0" />
        <Channel>Application</Channel>
        <Computer>ZP.gb.local</Computer>
        <Security />
      </System>
      <EventData>
        <Data Name="IsapiFilter">E:\Exchange\ClientAccess\owa\auth\owaauth.dll</Data>
        <Binary>05000000</Binary>
      </EventData>
    </Event>

    Log Name:      Application
    Source:        Microsoft-Windows-IIS-W3SVC-WP
    Date:          7/14/2020 8:10:47 PM
    Event ID:      2268
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:     
    Description:
    Could not load all ISAPI filters for site 'DEFAULT WEB SITE'.  Therefore site startup aborted.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Microsoft-Windows-IIS-W3SVC-WP" Guid="{670080D9-742A-4187-8D16-41143D1290BD}" EventSourceName="W3SVC-WP" />
        <EventID Qualifiers="49152">2268</EventID>
        <Version>0</Version>
        <Level>2</Level>
        <Task>0</Task>
        <Opcode>0</Opcode>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2020-07-14T17:10:47.000000000Z" />
        <EventRecordID>1130220</EventRecordID>
        <Correlation />
        <Execution ProcessID="0" ThreadID="0" />
        <Channel>Application</Channel>
        <Computer>ZP.gb.local</Computer>
        <Security />
      </System>
      <EventData>
        <Data Name="SiteName">DEFAULT WEB SITE</Data>
        <Binary>05000000</Binary>
      </EventData>
    </Event>

    Tuesday, July 14, 2020 5:13 PM

All replies

  • Hi,Cornel.

    According to the Microsoft KB 2028305,these are the possible cause of the problem:

    1. The Kerbauth module is configured incorrectly in Internet Information Services (IIS) in one of the following ways:

    • The Kerbauth module is displayed as a Managed module instead of as a Native module.
    • The Kerbauth module has been loaded on the Default website level (instead of, or in addition to, the PowerShell virtual directory).

    2.The user does not have Remote PowerShell Enabled status.

    3.The WSMan module entry is missing from the Global modules section of the ApplicationHost.config file that is in the following location:

    C:\Windows\System32\Inetsrv\config\ApplicationHost.config

    This causes the WSMan module to be displayed as a Managed module in the PowerShell virtual directory.

    Note:The WSMan Module entry may also be missing from the ApplicationHost.config file if the WinRM IIS Extension feature is installed on the server.


    And here are the resolutions:

    1. Make sure that the Kerbauth module is not enabled on the default website but is, instead, enabled only for the PowerShell virtual directory.

    2. Make sure that the user who is trying to connect has a Remote PowerShell Enabled status.

    3. Make sure that the WSMan module is registered but not enabled at the Server level. Also make sure that the WSMan module is enabled for the PowerShell virtual directory.

    Then, verify that the following WSMan module entry is included in the "Global modules" section of the C:\Windows\System32\Inetsrv\config\ApplicationHost.config file as follows:

    <globalModules> 
    <add name="WSMan" image="C:\Windows\system32\wsmsvc.dll" />
    Note:You must follow these steps even if the WinRM IIS Extension feature has been removed. This is because the uninstall procedure does not automatically fix the ApplicationHost.config file.

    For more information, please see KB2028305 and Troubleshooting the Exchange Management Shell


    This Exchange Server 2013 - Administration, Monitoring, and Performance Forum will be migrating to a new home on Microsoft Q&A, please refer to this sticky post for more details.

    Regards,

    Kael Yao


    Microsoft Online: Migration and Coexistence forum will be migrating to a new home on Microsoft Q&A! We invite you to post new questions in the new forum.

    For more information, please refer to the sticky post.

    • Edited by Kael Yao Wednesday, July 15, 2020 9:02 AM
    • Proposed as answer by Kael Yao Thursday, July 16, 2020 3:11 AM
    Wednesday, July 15, 2020 9:02 AM
  • Hi,

    Do suggestions above help?

    If you have any questions or need further help on this issue,please feel free to post back.

    If the issue has been resolved,please mark the helpful replies as answers,this will make answer searching in the forum easier and be beneficial to other community members as well.


    This Exchange Server 2013 - Administration, Monitoring, and Performance Forum will be migrating to a new home on Microsoft Q&A, please refer to this sticky post for more details.

    Regards,

    Kael Yao


    Microsoft Online: Migration and Coexistence forum will be migrating to a new home on Microsoft Q&A! We invite you to post new questions in the new forum.

    For more information, please refer to the sticky post.


    • Edited by Kael Yao Monday, July 20, 2020 8:28 AM
    Monday, July 20, 2020 8:26 AM