Exchange 2016 ошибка сервера в приложении ecp

  • Remove From My Forums

  • Вопрос

  • Здравствуйте! После автоматической установки обновления  Security Update For Exchange Server 2016 CU12 (KB4487563) начались проблемы с отправкой/получением писем. Было принято решение откатить состояние системы на
    дату, предшествующую установке обновления. В результате проблема с отправкой/получением писем была решена, но появилась новая проблема — невозможность войти в Exchange admin center. При попытке авторизоваться в EAC,
    появляется окно с ошибкой «Не удалось загрузить файл или сборку «Microsoft.Exchange.Common, Version=15.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35″ либо одну из их зависимостей. Не удается найти указанный файл.» (на скриншоте),
    при этом OWA работает. Подскажите, пожалуйста, куда копать и что можно сделать в данной ситуации?

Ответы

  • После отката была перезагрузка сервера. Похоже, удалось решить проблему, в чём помогла данная тема:

    https://social.technet.microsoft.com/Forums/en-US/7c36836c-0223-4bfe-8a36-24db8a021507/error-in-ecp-and-owa-after-update?forum=exchangesvrdeploy

    Опишу, что конкретно помогло: 

    Диспетчер служб IIS -> сайты -> Exchange Back End -> ecp -> Параметры приложения -> BinSearchFolders

    Пути были заданы через переменные: «%ExchangeInstallDir%bin;%ExchangeInstallDir%binCmdletExtensionAgents;%ExchangeInstallDir%ClientAccessOwabin»

    Я задал в явном виде:

    «C:Program FilesMicrosoftExchange ServerV15bin;C:Program FilesMicrosoftExchange ServerV15binCmdletExtensionAgents;C:Program FilesMicrosoftExchange ServerV15ClientAccessOwabin»

    Ну и, соответственно, после этого перезапуск сайта. После этого ECP стала открываться, пока полёт нормальный.

    • Помечено в качестве ответа

      5 июня 2019 г. 12:34

Источник

5 Replies

  • Author Matt

    Your specific error here in the screenshot indicates 80004005 which is Access Denied.

    There is another error at the end of this «SSLCertificateProblem»

    Try Get-ExchangeCertificate | fl and see if that illuminates the issue.


    Was this post helpful?
    thumb_up
    thumb_down

  • Author Shaw Lu

    Hi,

    According the
    screenshot, it seems an issue on server1.

    Please check
    the application pools and certificate binding in IIS. You could compare them with
    server2.

    Image: post content

    Image: post content


    2 found this helpful
    thumb_up
    thumb_down

  • Author C Peters

    Thank you.  The local host (127.0.0.1) HTTPS binding was missing the certificate on Server1.   Thank you again for pointing me in the right direction.  That fixed the issue.


    1 found this helpful
    thumb_up
    thumb_down

  • Author Shaw Lu

    Glad to see it helps.


    Was this post helpful?
    thumb_up
    thumb_down

  • Author Daniel Beato

    dbeato


    This person is a Verified Professional

    This person is a verified professional.

    Verify your account
    to enable IT peers to see that you are a professional.

    pure capsaicin

    cpeters wrote:

    Thank you.  The local host (127.0.0.1) HTTPS binding was missing the certificate on Server1.   Thank you again for pointing me in the right direction.  That fixed the issue.

    Please make sure to mark the best answer then.


    Was this post helpful?
    thumb_up
    thumb_down

Источник

RRS feed

  • Remove From My Forums

  • Question

  • I’ve just installed Exchange 2016 and after the first initial reboot, I am getting the error below when trying to access ECP. 

    Any fixes?

All replies

    • Edited by

      Tuesday, October 3, 2017 1:14 PM

  • Hi,

    To fix your issue, please ensure:
    1. All Exchange services running well.
    2. Check the status of server component by
    Get-ServerComponentState.

    If this issue remain exists, try to reset ECP by UpdateCas.ps1:
    1. Open Windows PowerShell by administrator.
    2. Locate to C:Program FilesMicrosoftExchange ServerV15Bin, then run this .ps1 file.

    Figure as below:

    Regards,

    Allen Wang

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

    • Proposed as answer by
      Allen_WangJF
      Thursday, October 12, 2017 2:29 AM

  • @MTrieu,
    does this issue fix after run UpdateCas.ps1?
    If so, please be free to mark the useful reply as answer. Thanks.

    Regards,

    Allen Wang

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

  • Hi,

    Is there any further help with this issue?
    If it helps, please be free to mark the useful reply as answer. Thanks.

    Regards,

    Allen Wang

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

  • Dear Allen,

    I have similar issue. OWA no issue but the ECP unable to access.

    When drill into the application, event log show the following.

    Event code: 3008
    Event message: A configuration error has occurred.
    Event time: 12/3/2019 10:09:57 AM
    Event time (UTC): 12/3/2019 2:09:57 AM
    Event ID: e98294cda3ce4744a0302c5f261e4cce
    Event sequence: 1
    Event occurrence: 1
    Event detail code: 0

     
    Application information:
        Application domain: /LM/W3SVC/2/ROOT/ecp-363-132198125971665173

        Trust level: Full
        Application Virtual Path: /ecp
        Application Path: C:Program FilesMicrosoftExchange ServerV15ClientAccessecp

        Machine name: XXXXXXXX

     
    Process information:
        Process ID: 6440
        Process name: w3wp.exe
        Account name: NT AUTHORITYSYSTEM

     
    Exception information:
        Exception type: ConfigurationErrorsException
        Exception message: Could not load file or assembly ‘Microsoft.Exchange.Common, Version=15.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35’ or one of its dependencies. The system cannot find the file specified.
       at System.Web.Configuration.ConfigUtil.GetType(String typeName, String propertyName, ConfigurationElement configElement, XmlNode node, Boolean checkAptcaBit, Boolean ignoreCase)
       at System.Web.Configuration.ConfigUtil.GetType(String typeName, String propertyName, ConfigurationElement configElement, Boolean checkAptcaBit)
       at System.Web.Configuration.Common.ModulesEntry.SecureGetType(String typeName, String propertyName, ConfigurationElement configElement)
       at System.Web.Configuration.Common.ModulesEntry..ctor(String name, String typeName, String propertyName, ConfigurationElement configElement)
       at System.Web.HttpApplication.BuildIntegratedModuleCollection(List`1 moduleList)
       at System.Web.HttpApplication.GetModuleCollection(IntPtr appContext)
       at System.Web.HttpApplication.RegisterEventSubscriptionsWithIIS(IntPtr appContext, HttpContext context, MethodInfo[] handlers)
       at System.Web.HttpApplication.InitSpecial(HttpApplicationState state, MethodInfo[] handlers, IntPtr appContext, HttpContext context)
       at System.Web.HttpApplicationFactory.GetSpecialApplicationInstance(IntPtr appContext, HttpContext context)
       at System.Web.Hosting.PipelineRuntime.InitializeApplication(IntPtr appContext)

    Could not load file or assembly ‘Microsoft.Exchange.Common, Version=15.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35’ or one of its dependencies. The system cannot find the file specified.
       at System.RuntimeTypeHandle.GetTypeByName(String name, Boolean throwOnError, Boolean ignoreCase, Boolean reflectionOnly, StackCrawlMarkHandle stackMark, IntPtr pPrivHostBinder, Boolean loadTypeFromPartialName, ObjectHandleOnStack type)
       at System.RuntimeTypeHandle.GetTypeByName(String name, Boolean throwOnError, Boolean ignoreCase, Boolean reflectionOnly, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean loadTypeFromPartialName)
       at System.Type.GetType(String typeName, Boolean throwOnError, Boolean ignoreCase)
       at System.Web.Compilation.BuildManager.GetType(String typeName, Boolean throwOnError, Boolean ignoreCase)
       at System.Web.Configuration.ConfigUtil.GetType(String typeName, String propertyName, ConfigurationElement configElement, XmlNode node, Boolean checkAptcaBit, Boolean ignoreCase)

     
     
    Request information:
        Request URL: https://localhost:444/ecp/About.aspx
        Request path: /ecp/About.aspx
        User host address: 127.0.0.1
        User:  
        Is authenticated: False
        Authentication Type:  
        Thread account name: NT AUTHORITYSYSTEM

     
    Thread information:
        Thread ID: 124
        Thread account name: NT AUTHORITYSYSTEM
        Is impersonating: False
        Stack trace:    at System.Web.Configuration.ConfigUtil.GetType(String typeName, String propertyName, ConfigurationElement configElement, XmlNode node, Boolean checkAptcaBit, Boolean ignoreCase)
       at System.Web.Configuration.ConfigUtil.GetType(String typeName, String propertyName, ConfigurationElement configElement, Boolean checkAptcaBit)
       at System.Web.Configuration.Common.ModulesEntry.SecureGetType(String typeName, String propertyName, ConfigurationElement configElement)
       at System.Web.Configuration.Common.ModulesEntry..ctor(String name, String typeName, String propertyName, ConfigurationElement configElement)
       at System.Web.HttpApplication.BuildIntegratedModuleCollection(List`1 moduleList)
       at System.Web.HttpApplication.GetModuleCollection(IntPtr appContext)
       at System.Web.HttpApplication.RegisterEventSubscriptionsWithIIS(IntPtr appContext, HttpContext context, MethodInfo[] handlers)
       at System.Web.HttpApplication.InitSpecial(HttpApplicationState state, MethodInfo[] handlers, IntPtr appContext, HttpContext context)
       at System.Web.HttpApplicationFactory.GetSpecialApplicationInstance(IntPtr appContext, HttpContext context)
       at System.Web.Hosting.PipelineRuntime.InitializeApplication(IntPtr appContext)

     
     
    Custom event details:

    Can you advise?

Источник

Скрипт написан по следам вот этой статьи.

После обновления MS Exchange 2016 потерялся доступ к серверу как по owa, так и по ecp. Что характерно – страница с формой входа исправно работает, а после авторизации сервер сообщает об ошибке доступа с кодом 500.

Поиск по форумам сначала привёл на вот это обсуждение и только потом нашлась вышеуказанная статья. Все команды указанные там, я объединил в скрипт и автоматизировал получение отпечатка скрипта. По сути, запустил и забыл.

Вот код:

## Заголовок окна ##
[System.Console]::Title = "Исправление ошибки доступа к OWA и ECP"

## Добавление командлетов Exchange в сессию ##
Add-PSSnapin Microsoft.Exchange.Management.PowerShell.SnapIn

## Установка переменных ##
$thumbprint = (Get-AuthConfig).CurrentCertificateThumbprint
$domain = (Get-ADDomain).DNSRoot

## Генерация сертификата ##
New-ExchangeCertificate -KeySize 2048 -PrivateKeyExportable $true -SubjectName "cn=Microsoft Exchange Server Auth Certificate" -FriendlyName "Microsoft Exchange Server Auth Certificate" -DomainName $domain #@()

## Настройка параметров авторизации ##
Set-AuthConfig -NewCertificateThumbprint $thumbprint -NewCertificateEffectiveDate (Get-Date)
Set-AuthConfig -PublishCertificate
Set-AuthConfig -ClearPreviousCertificate

## Перезапуск служб ##
Restart-WebAppPool MSExchangeOWAAppPool
Restart-WebAppPool MSExchangeECPAppPool

Источник

При открытии Exchange Managment Shell (EMS) или Центра администрирования (ECP) появляется следующая ошибка:

ОДРОБНО: Подключение к SREX01.
New-PSSession : [srex01] Сбой подключения к удаленному серверу srex01. Сообщение об оши
бке:  Подробности см. в разделе справки "about_Remote_Troubleshooting".
строка:1 знак:1
+ New-PSSession -ConnectionURI "$connectionUri" -ConfigurationName Micr ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
   gTransportException
    + FullyQualifiedErrorId : -2144108477,PSSessionOpenFailed
ПОДРОБНО: Подключение к SREX01.
New-PSSession : [srex01] Сбой подключения к удаленному серверу srex01.sibpromstroy.ru. Сообщение об ошибке:  Подробности см. в разделе справки "about_Remot
e_Troubleshooting".
строка:1 знак:1
+ New-PSSession -ConnectionURI "$connectionUri" -ConfigurationName Micr ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotingTransportException
    + FullyQualifiedErrorId : -2144108477,PSSessionOpenFailed

New-PSSession: server: Не удалось подключиться к удаленному серверу «сервер» со следующим сообщением об ошибке: ClientAccessServer=Server BackEndServer=Server, RequestId=….[FailureCategory=Cafe-SendFailure]… FullyQualifiedErrorId: –2144108477,PSSessionOpenFailed

После ввода пароля страница открывается пустой:

Системный журнал ошибка 15021 HttpEvent

Произошла ошибка при использовании конфигурации SSL для конечной точки 0.0.0.0:444. Код состояния ошибки содержится в возвращенных данных

Решение

Для этого я открываю консоль IIS и проверяю,   действительно ли запущен   серверный сайт Exchange , поэтому я щелкаю правой кнопкой мыши — «Редактировать привязки»  , чтобы увидеть конфигурацию. Я нахожу следующее:

Правой кнопкой мыши в IIS на Exchange Backend – Edit Bindings:

Выбираем https порт 444 – Edit

Выбираем сертификат “Microsoft Exchange” – Ok

Перезапускаем IIS, отправляем “спасибо” автору.

Источник

Я получаю сообщение об ошибке в ECP Exchange Server 2016, пока OWA работает нормально. Откроется страница входа в ECP, но после входа мы получим следующую ошибку. Эта проблема существует около недели, и мы не достигли прогресса. Пожалуйста, помогите, если кто-то столкнулся с подобной ошибкой и решил проблему.

      Server Error in '/ecp' Application.
Object reference not set to an instance of an object.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.NullReferenceException: Object reference not set to an instance of an object.

Source Error:

The source code that generated this unhandled exception can only be shown when compiled in debug mode. To enable this, please follow one of the below steps, then request the URL:

1. Add a "Debug=true" directive at the top of the file that generated the error. Example:

  <%@ Page Language="C#" Debug="true" %>

or:

2) Add the following section to the configuration file of your application:

<configuration>
   <system.web>
       <compilation debug="true"/>
   </system.web>
</configuration>

Note that this second technique will cause all files within a given application to be compiled in debug mode. The first technique will cause only that particular file to be compiled in debug mode.

Important: Running applications in debug mode does incur a memory/performance overhead. You should make sure that an application has debugging disabled before deploying into production scenario.

Stack Trace:


[NullReferenceException: Object reference not set to an instance of an object.]
   Microsoft.Exchange.Management.ControlPanel.Global..cctor() +119

[TypeInitializationException: The type initializer for 'Microsoft.Exchange.Management.ControlPanel.Global' threw an exception.]
   ASP.global_asax..ctor() +28

[TargetInvocationException: Exception has been thrown by the target of an invocation.]
   System.RuntimeTypeHandle.CreateInstance(RuntimeType type, Boolean publicOnly, Boolean noCheck, Boolean& canBeCached, RuntimeMethodHandleInternal& ctor, Boolean& bNeedSecurityCheck) +0
   System.RuntimeType.CreateInstanceSlow(Boolean publicOnly, Boolean skipCheckThis, Boolean fillCache, StackCrawlMark& stackMark) +139
   System.Activator.CreateInstance(Type type, Boolean nonPublic) +105
   System.RuntimeType.CreateInstanceImpl(BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes, StackCrawlMark& stackMark) +1431
   System.Activator.CreateInstance(Type type, BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes) +184
   System.Activator.CreateInstance(Type type, BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture) +27
   System.Web.HttpRuntime.CreateNonPublicInstance(Type type, Object[] args) +79
   System.Web.HttpApplicationFactory.GetSpecialApplicationInstance(IntPtr appContext, HttpContext context) +178
   System.Web.Hosting.PipelineRuntime.InitializeApplication(IntPtr appContext) +341

[HttpException (0x80004005): Exception has been thrown by the target of an invocation.]
   System.Web.HttpRuntime.FirstRequestInit(HttpContext context) +523
   System.Web.HttpRuntime.EnsureFirstRequestInit(HttpContext context) +107
   System.Web.HttpRuntime.ProcessRequestNotificationPrivate(IIS7WorkerRequest wr, HttpContext context) +688


Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.7.3770.0
Источник

Ever reboot your servers and when you login, all looks good on the surface but when you try and do stuff well it doesn’t actually work? In this scenario exactly that.

Running coexistence with Exchange 2016 and 2019 and after a reboot, all seemed good. Exchange Management Shell launched fine but the Exchange Admin Center came up with the login page and then immediately after that HTTP 500 Error:

Right, let’s not go into panic mode. Step by step to get this working:

  1. Check that all Exchange services are started.
  2. Check that all stores are mounted.
  3. Check which database the user account is on.

As you can see, services where still starting, others had not started and a few were running. Start each service and wait for it to enter running mode.

In our case, the Exchange 2016 store was not mounted because the service was not started, after starting the service, the store mounted.

Right, after a few minutes and refreshing the ECP Page we were finally able to login and things back to normal.

Now launching that user account, we could see it is located on the Exchange 2016 server hence the login error as well:

So a few basic checks and everything is fine.

Hope it helps.

Источник

Понравилась статья? Поделить с друзьями:
  • Explorer exe ошибка при запуске виндовс
  • Explorer exe ошибка при запуске windows 10
  • Explorer exe ошибка при выполнении приложения сервера windows 10
  • Explorer exe ошибка при выполнении приложения сервер
  • Explorer exe ошибка ввода вывода