ECP and OWA shows 500 error after patch update

%3CLINGO-SUB%20id%3D%22lingo-sub-3187689%22%20slang%3D%22en-US%22%3EECP%20and%20OWA%20shows%20500%20error%20after%20patch%20update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3187689%22%20slang%3D%22en-US%22%3E%3CP%20class%3D%22%22%3EHi.%20Today%20in%20an%20exchange%20environment%20with%20DAG%20configured%20with%202%20servers%2C%20EmailA%20and%20EmailB%20we%20have%20installed%20some%20patches%20on%20the%20two%20servers%3A%3C%2FP%3E%3CP%20class%3D%22%22%3EUpdate%20for%20Microsoft%20Windows%20(KB5010462)%3C%2FP%3E%3CP%20class%3D%22%22%3ESecurity%20Update%20for%20Microsoft%20Windows%20(KB5010419)%3C%2FP%3E%3CP%20class%3D%22%22%3EUpdate%20for%20Microsoft%20Windows%20(KB5008868)%3C%2FP%3E%3CP%20class%3D%22%22%3EAfter%20installing%20the%20patches%2C%20we%20have%20found%20that%20we%20cannot%20access%20ECP%20and%20OWA%20on%20EmailA%20(it%20shows%20error%20500).%20One%20weird%20thing%20is%2C%20the%20CU22%20(KB5007409)%20that%20we%20have%20installed%20on%2011%20Nov%202021%20shows%20that%20it%20was%20installed%20on%20today%20as%20well%20in%20control%20panel.%3C%2FP%3E%3CP%20class%3D%22%22%3EWe%20have%20followed%20the%20steps%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fexchange%2Ftroubleshoot%2Fclient-connectivity%2Fowa-stops-working-after-update%22%20target%3D%22_blank%22%20rel%3D%22noopener%20ugc%20noreferrer%22%3Ehere%3C%2FA%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3Ebut%20it%20didn't%20work.%20Everything%20works%20fine%20on%20EmailB%20so%20the%20impact%20was%20not%20that%20big.%3C%2FP%3E%3CP%20class%3D%22%22%3EWe%20can%20re-install%20EmailA%20but%20we%20need%20some%20logs%20to%20show%20that%20the%20server%20has%20some%20errors%20through%20some%20logs.%20Can%20anyone%20help%20with%20the%20issue%2For%20knows%20where%20can%20I%20find%20some%20related%20log%20files%3F%20Thanks.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-3187689%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EExchange%20Server%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3197485%22%20slang%3D%22en-US%22%3ERe%3A%20ECP%20and%20OWA%20shows%20500%20error%20after%20patch%20update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3197485%22%20slang%3D%22en-US%22%3EDid%20you%20try%20to%20run%20updateconfigfiles.ps1%20and%20updatecas.ps1%20%3F%3CBR%20%2F%3ESometimes%20after%20upgrade%20or%20update%20this%20script%20are%20not%20executed%20corretly%20and%20can%20also%20render%20EAC%20or%20ECP%20inaccessible%2C%20causing%20HTTP%20ERROR%20500%20after%20login.%3CBR%20%2F%3E%3CBR%20%2F%3ETheses%20PowerShell%20scripts%20located%20in%20the%20Exchange%20Server%20%E2%80%98Bin%E2%80%99%20directory%20(C%3A%5CProgram%20Files%5CMicrosoft%5CExchange%20Server%5CV15%5CBin%5C)%20to%20resolve%20the%20error.%20You%20can%20run%20from%20PS%20command%20line.%3C%2FLINGO-BODY%3E
Occasional Contributor

Hi. Today in an exchange environment with DAG configured with 2 servers, EmailA and EmailB we have installed some patches on the two servers:

Update for Microsoft Windows (KB5010462)

Security Update for Microsoft Windows (KB5010419)

Update for Microsoft Windows (KB5008868)

After installing the patches, we have found that we cannot access ECP and OWA on EmailA (it shows error 500). One weird thing is, the CU22 (KB5007409) that we have installed on 11 Nov 2021 shows that it was installed on today as well in control panel.

We have followed the steps here but it didn't work. Everything works fine on EmailB so the impact was not that big.

We can re-install EmailA but we need some logs to show that the server has some errors through some logs. Can anyone help with the issue/or knows where can I find some related log files? Thanks.

1 Reply

Did you try to run updateconfigfiles.ps1 and updatecas.ps1 ?
Sometimes after upgrade or update these scripts are not executed corretly and can also render EAC or ECP inaccessible, causing HTTP ERROR 500 after login.

These PowerShell scripts located in the Exchange Server ‘Bin’ directory (C:\Program Files\Microsoft\Exchange Server\V15\Bin\) to resolve the error. You can run from PS command line.