zoukankan      html  css  js  c++  java
  • OWA or ECP stops working after you install a security update

    Symptoms

    After you install a security update on a server that’s running Microsoft Exchange Server, either Outlook on the web (OWA) or Exchange Control Panel (ECP), or both applications stop working on the server.

    OWA displays the following error message:

    Something went wrong
    Your request couldn’t be completed. HTTP Status code: 500

    Screenshot of the OWA error message.

    ECP displays the following error message:

    Server Error in ‘/ecp’ Application.
    Could not load file or assembly ‘Microsoft.Exchange.Common, Version=15.0.0.0 …Culture=neutral, PublicKeyToken=31bf3856ad364e54’ or one of its dependencies. The system cannot find the file specified.

    Screenshot of the E C P error message.

    Cause

    These errors occur if the security update was manually installed on a server that has User Account Control (UAC) enabled, but without using elevated permissions.

    Resolution

    Use elevated permissions to reinstall the security update on the server.

    1. Select Start, and then type cmd.
    2. Right-click Command Prompt from the search results, and then select Run as administrator.
    3. If the User Account Control window appears, select the option to open an elevated Command Prompt window, and then select Continue. If the UAC window doesn’t appear, continue to the next step.
    4. Type the full path of the .msp file for the security update, and then press Enter.
    5. After the update installs, restart the server.

    Check whether you can now access OWA and ECP on the server without getting an error message.

    If the ECP error message continues to display, do the following:

      1. Start IIS Manager on the server.

      2. Navigate to Exchange Backend website > ECP Virtual directory.

      3. Select Application settings > BinsearchFolder.

      4. Check the paths to the Exchange directories that are listed. You might see directory paths that resemble the following:

        %ExchangeInstallDir%bin;
        %ExchangeInstallDir%bin\CmdletExtensionAgents;
        %ExchangeInstallDir%ClientAccess\Owa\bin

      5. Replace the paths with the following paths:

        C:\Program Files\Microsoft\Exchange Server\V15\bin;
        C:\Program Files\Microsoft\Exchange Server\V15\bin\CmdletExtensionAgents;
        C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\Owa\bin

        Note The paths must point to where Exchange Server is installed. The following examples assume that the program is installed on drive C and that the version is Microsoft Exchange Server 2013. If it is installed on a different drive on your server, or if you’re using a different version such as Microsoft Exchange Server 2010, then use the path and version information that's appropriate for your installation.

      6. Navigate to a folder that includes Exchange Server scripts. By default, scripts are located in the following path for Exchange Server 2013:

        C:\Program Files\Microsoft\Exchange Server\v15\Bin

        Note For Exchange Server 2010, the scripts will be in the V14 folder instead.

      7. Start Exchange Management Shell as an administrator and run the following scripts: .\UpdateCas.ps1 and .\UpdateConfigFiles.ps1.

      8. Exit Exchange Management Shell and open a Command Prompt window as an administrator.

      9. Run iisreset.

      10. Restart the server, and verify that you no longer get an error message when you access ECP.

    *******VICTORY LOVES PREPARATION*******
  • 相关阅读:
    Clojure编写一个阶乘程序 使用递归
    SSH框架学习步骤
    js需要清楚的内存模型
    SeaJS结合javascript面向对象使用笔记(一)
    函数副作用
    linux笔记2
    C#事件与接口编程实例
    C#的接口基础教程之七 覆盖虚接口
    C#的接口基础教程之六 接口转换
    C#的接口基础教程之五 实现接口
  • 原文地址:https://www.cnblogs.com/rusking/p/15743961.html
Copyright © 2011-2022 走看看