Exchange 2019 HTTP error 500 After CU10 and KB5004780

Question

Hey,

I have a problem with my Exchange 2019 server. After Friday I installed CU10 and immediately afterwards (run in cmd as admin) KB5004779. After the reboot, the Exchange services do not start automatically. Set it to auto-delayed and rebooted and it worked fine. When I start Exchange Administrative Center I get HTTP 500 error. When I start the Management Shell I also get an HTTP500 error (+ FullyQualifiedErrorId : WinRMHttpError,PSSessionOpenFailed) and it cannot connect. ExchangeInstallPath checked and in IIS PowerShell virtual directory. I can't find anything in the windows log that can help me. I've tried everything but can't get it to work. Can someone help me with this.

Answer 1

Hi @Geert van der Heijden ,

Basically after you installed a new Exchange server, you need to restart once to apply some changes.

Better check your server status with the script: HealthChecker
Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.

And for your issue, please first check all Exchange services are running, run this in powershell:

Get-Service | Where {$_.DisplayName -Like "*Exchange*"} | Where {$_.DisplayName -NotLike "*Hyper-V*"} | Format-Table DisplayName, Name, Status  

And please check the ECP Application settings in IIS below:

If it's something like "%ExchangeInstallDir%bin;", please replace them all with(the path should be the Exchange installed path):
C:\Program Files\Microsoft\Exchange Server\V15\bin;
C:\Program Files\Microsoft\ExchangeServer\V15\bin\CmdletExtensionAgents;
C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\Owa\bin

Best regards,
Lou

---

If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 2

Thank you for your Answer.
The path in IIS I already checked and it's correct.
All services are running in services.msc
When I run the Healtchecker he can't connect and get the same message as the Exchange Power Shell try's to connect (replaced domain wiht OUR DOMAIN NAME):

     Welcome to the Exchange Management Shell!

Full list of cmdlets: Get-Command
Only Exchange cmdlets: Get-ExCommand
Cmdlets that match a specific string: Help <string>
Get general help: Help
Get help for a cmdlet: Help <cmdlet name> or <cmdlet name> -?
Exchange team blog: Get-ExBlog
Show full output for a command: <command> | Format-List

Show quick reference guide: QuickRef
VERBOSE: Connecting to SERVER01.(OUR DOMAIN NAME).LOCAL.
New-PSSession : [server01.OUR DOMAIN NAME.local] Connecting to remote server server01.OUR DOMAIN NAME.local failed with the following error
message : De WinRM-client heeft de HTTP-status Server Error (500) ontvangen, maar er is van de externe service geen na
dere informatie ontvangen over de oorzaak van de fout. For more information, see the about_Remote_Troubleshooting Help
topic.
At line:1 char:1

• New-PSSession -ConnectionURI "$connectionUri" -ConfigurationName Micr ...
• ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
• CategoryInfo : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
  gTransportException
• FullyQualifiedErrorId : WinRMHttpError,PSSessionOpenFailed

Answer 3

Thank you for the quick response. Yes I've checked the bindings on the default website and Back end and our SSL certifcate is selected.
It's strange that I get the HTTP 500 error and that was the first thing I checked.

Best regards,
Geert

Update: We found the problem in IIS Modules StaticFilter. When I removed it and reset IIS everything works fine! Thanks for the help.

Answer 4

Yes I've checked serveral path's but i can't find something stange.
When i go to https://server01/owa or ecp I get the http 500 error.

I tried to run the CU10 update in recovery mode with no luck (https://learn.microsoft.com/en-us/exchange/high-availability/disaster-recovery/recover-exchange-servers?view=exchserver-2019) I think it only works when Exchange is not installed.

I run the Setup in upgrade mode and that was completed good but It's still not working.

Do I have other option? Mail is not working since friday and it's beginning to be a problem here.

Kind regards

Answer 5

Hi Lou,

It looks like the mail flow is working good. If I open Outlook on a external computer than it can't connect to the Exchange server so the users can't check the mail.

1. The system variables i had already checked and the value is good D:\Exchange Server\V15\
2. WinRM IIS extension was not installed and I installed it but without any luck.
3. Connecting from a remote pc doesn't work I get error 0x80090311
   On the local server the Exchange Toolbox can't even connect.

When I use the old Internet Exporer then I get this message when I go to https://server01/owa :

DLG_FLAGS_SEC_CERT_CN_INVALID
and then I get a blank page

I Also run the UpdateCas.ps1 and UpdateConfigfiles.ps1 from the Exchange bin folder but it's still not working.