locked
OWA Error after Exchange 2016 CU17 Update RRS feed

  • Вопрос

  • hi community,

    after updating our exchange servers to cu17, owa stops working, after the login an error 500 is displayed in the brower, in eventlog eventid 1309 from source asp.net is written:

    Event code: 3005 
    Event message: An unhandled exception has occurred. 
    Event time: 21.07.2020 16:34:01 
    Event time (UTC): 21.07.2020 14:34:01 
    Event ID: e90849c76df34d8cb67b05ea2c97fbc5 
    Event sequence: 2 
    Event occurrence: 1 
    Event detail code: 0 
     
    Application information: 
        Application domain: /LM/W3SVC/2/ROOT/owa-15-132398156356607838 
        Trust level: Full 
        Application Virtual Path: /owa 
        Application Path: C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\owa\ 
        Machine name: EXC01 
     
    Process information: 
        Process ID: 8864 
        Process name: w3wp.exe 
        Account name: NT AUTHORITY\SYSTEM 
     
    Exception information: 
        Exception type: TargetInvocationException 
        Exception message: Exception has been thrown by the target of an invocation.
       at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
       at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)
       at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
       at Owin.Loader.DefaultLoader.<>c__DisplayClass12.<MakeDelegate>b__b(IAppBuilder builder)
       at Owin.Loader.DefaultLoader.<>c__DisplayClass1.<LoadImplementation>b__0(IAppBuilder builder)
       at Microsoft.Owin.Host.SystemWeb.OwinAppContext.Initialize(Action`1 startup)
       at Microsoft.Owin.Host.SystemWeb.OwinBuilder.Build(Action`1 startup)
       at Microsoft.Owin.Host.SystemWeb.OwinHttpModule.InitializeBlueprint()
       at System.Threading.LazyInitializer.EnsureInitializedCore[T](T& target, Boolean& initialized, Object& syncLock, Func`1 valueFactory)
       at Microsoft.Owin.Host.SystemWeb.OwinHttpModule.Init(HttpApplication context)
       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.Owin, Version=2.1.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
       at Owin.OwinExtensions.MapSignalR(IAppBuilder builder, String path, Type connectionType, ConnectionConfiguration configuration)
       at Microsoft.Exchange.Clients.Owa2.Server.Core.notifications.SignalR.SignalRStartup.Configuration(IAppBuilder app)

     
     
    Request information: 
        Request URL: https://localhost:444/owa/exhealth.check 
        Request path: /owa/exhealth.check 
        User host address: 127.0.0.1 
        User:  
        Is authenticated: False 
        Authentication Type:  
        Thread account name: NT AUTHORITY\SYSTEM 
     
    Thread information: 
        Thread ID: 18 
        Thread account name: NT AUTHORITY\SYSTEM 
        Is impersonating: False 
        Stack trace:    at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
       at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)
       at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
       at Owin.Loader.DefaultLoader.<>c__DisplayClass12.<MakeDelegate>b__b(IAppBuilder builder)
       at Owin.Loader.DefaultLoader.<>c__DisplayClass1.<LoadImplementation>b__0(IAppBuilder builder)
       at Microsoft.Owin.Host.SystemWeb.OwinAppContext.Initialize(Action`1 startup)
       at Microsoft.Owin.Host.SystemWeb.OwinBuilder.Build(Action`1 startup)
       at Microsoft.Owin.Host.SystemWeb.OwinHttpModule.InitializeBlueprint()
       at System.Threading.LazyInitializer.EnsureInitializedCore[T](T& target, Boolean& initialized, Object& syncLock, Func`1 valueFactory)
       at Microsoft.Owin.Host.SystemWeb.OwinHttpModule.Init(HttpApplication context)
       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: 

    steps tried:

    anyone the same issue or can assist to solve this ?!


    • Изменено sp4d0n 21 июля 2020 г. 15:14 spelling mistake
    21 июля 2020 г. 15:12

Ответы

  • Hi,

    Could you please provide the complete error information on the OWA page? Can ECP work properly?

    We could try the below suggestions to resolve your issue

    1. Check the value of BinSearchFolders, go to IIS > open sites > open Exchange back end > open ecp > doubleklick application settings. 

    It should be like: 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

    2. Try recycling the MSExchangeOWAAppPool and MSExchangeECPAppPool

    3. Try running "UpdateCas.ps1" and "UpdateConfigFiles.ps1" under C:\Program Files\Microsoft\Exchange Server\V15\Bin, it will reset OWA and ECP file.

    This Exchange Server 2016 – Administration Forum will be migrating to a new home on Microsoft Q&A, please refer to this sticky post for more details.

    Regards,

    Joyce Shen


    Exchange Server 2016 – Administration 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.

    • Помечено в качестве ответа sp4d0n 22 июля 2020 г. 9:59
    22 июля 2020 г. 2:39

Все ответы

  • Hi,

    Could you please provide the complete error information on the OWA page? Can ECP work properly?

    We could try the below suggestions to resolve your issue

    1. Check the value of BinSearchFolders, go to IIS > open sites > open Exchange back end > open ecp > doubleklick application settings. 

    It should be like: 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

    2. Try recycling the MSExchangeOWAAppPool and MSExchangeECPAppPool

    3. Try running "UpdateCas.ps1" and "UpdateConfigFiles.ps1" under C:\Program Files\Microsoft\Exchange Server\V15\Bin, it will reset OWA and ECP file.

    This Exchange Server 2016 – Administration Forum will be migrating to a new home on Microsoft Q&A, please refer to this sticky post for more details.

    Regards,

    Joyce Shen


    Exchange Server 2016 – Administration 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.

    • Помечено в качестве ответа sp4d0n 22 июля 2020 г. 9:59
    22 июля 2020 г. 2:39
  • Hi

    OWA and ECP site work fine.

    1. Check the value of BinSearchFolders

    BinSearchFolders :

    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

    But on thirdparty application which want to connect to e-mail server using SMTP: TLS:587 I get error:

    Odpowiedź serwera SMTP: 250-mail.domain123.com Hello [x.x.x.x] 250-SIZE 37748736 250-PIPELINING 250-DSN 250-ENHANCEDSTATUSCODES 250-AUTH GSSAPI NTLM 250-8BITMIME 250-BINARYMIME 250 CHUNKING


    Kind Regards Tomasz

    22 июля 2020 г. 8:04
  • hi joyce,

    the error was only with owa, ecp was working, screenshot:

    1. was correct
    2. does not help
    3. solved my problem !

    thanks for support !

    22 июля 2020 г. 9:59
  • Hi Discovered what could be the problem.

    Problem started when I installed new certificate for IIS, IMAP, SMTP. POP and remove the old. When I again import the old certificate (it will expire in 5 days) everything start work!!!

    I if remove this old certificate and enable the new - problem start again.

    I use ECP console to mark tne new certificate to services and use PowerSell - but the same situation.

    So I've got some question. If we have two Internet e-mail domain :
    domain1.com
    domain2.com

    and internal domain
    corp.domain1.com

    So Ca I add exchange sever exch1.corp.domain1.com to request for DIGICERT (thirdparty certificate issuer)? 

    What option is ok:

    Version 1: SAN ceritificate from Digicert

    mail.domain1.com
    mail.domain2.com
    autodiscovery.domain1.com
    autodiscovery.domain2.com

    or Version 2:

    mail.domain1.com
    mail.domain2.com
    autodiscovery.domain1.com
    autodiscovery.domain2.com
    exch1.corp.domain1.com

    He have internal PKI for domain corp.domain1.com and exchange server has certificate of this PKI.

    So perhaps that is the reason of problem? External (from Internet) certificate issuer cannot be responsible for  exch1.corp.domain1.com?






    Kind Regards Tomasz



    • Изменено Yukio Seki 22 июля 2020 г. 18:11 more data
    22 июля 2020 г. 13:28
  • Hi Discovered what could be the problem.

    Problem started when I installed new certificate for IIS, IMAP, SMTP. POP and remove the old. When I again import the old certificate (it will expire in 5 days) everything start work!!!

    I if remove this old certificate and enable the new - problem start again.

    I use ECP console to mark tne new certificate to services and use PowerSell - but the same situation.

    So I've got some question. If we have two Internet e-mail domain :
    domain1.com
    domain2.com

    and internal domain
    corp.domain1.com

    So Ca I add exchange sever exch1.corp.domain1.com to request for DIGICERT (thirdparty certificate issuer)? 

    What option is ok:

    Version 1: SAN ceritificate from Digicert

    mail.domain1.com
    mail.domain2.com
    autodiscovery.domain1.com
    autodiscovery.domain2.com

    or Version 2:

    mail.domain1.com
    mail.domain2.com
    autodiscovery.domain1.com
    autodiscovery.domain2.com
    exch1.corp.domain1.com

    He have internal PKI for domain corp.domain1.com and exchange server has certificate of this PKI.

    So perhaps that is the reason of problem? External (from Internet) certificate issuer cannot be responsible for  exch1.corp.domain1.com?






    Kind Regards Tomasz



    What's the type of the expired certificate? You could try renewing it.

    If Auth Certificate, referring to this link: https://byronwright.blogspot.com/2018/05/expired-microsoft-exchange-server-auth.html

    If a certificate issued by CA, https://docs.microsoft.com/en-us/exchange/architecture/client-access/renew-certificates?view=exchserver-2016#renew-a-certificate-that-was-issued-by-a-certification-authority

    And the SAN should be like autodiscover.contoso.com, the official document here for your reference as well: https://docs.microsoft.com/en-us/exchange/architecture/client-access/create-ca-certificate-requests?view=exchserver-2016#use-the-exchange-management-shell-to-create-a-new-certificate-request

    [Note] This forum will be locked down, you can continue to post in here before 8/10/2020. It is highly recommended to register the Microsoft Q&A Platform and create new thread in Microsoft Q&A Platform to continue the discussion.

    This Exchange Server 2016 – Administration Forum will be migrating to a new home on Microsoft Q&A, please refer to this sticky post for more details.

    Regards,

    Joyce Shen


    Exchange Server 2016 – Administration 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.

    5 августа 2020 г. 6:47