question

GeertvanderHeijden-5855 avatar image
0 Votes"
GeertvanderHeijden-5855 asked KevinClawson-7381 commented

Exchange 2019 HTTP error 500 After CU10 and KB5004780

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.

office-exchange-server-connectivity
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

ZhengqiLou-MSFT avatar image
0 Votes"
ZhengqiLou-MSFT answered

Hi @GeertvanderHeijden-5855 ,

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:
123826-image.png
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.


image.png (30.2 KiB)
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

GeertvanderHeijden-5855 avatar image
0 Votes"
GeertvanderHeijden-5855 answered ZhengqiLou-MSFT commented

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


· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Hi @GeertvanderHeijden-5855 ,

Then please check if the certificate binding in IIS, the https service should have a certificate on it.
Your business certificate or Microsoft Exchange(by default) for the Default Web Site, and Microsoft Exchange for Exchange Back End.
123921-image.png

Best regards,
Lou

0 Votes 0 ·
image.png (55.9 KiB)
GeertvanderHeijden-5855 avatar image
0 Votes"
GeertvanderHeijden-5855 answered KevinClawson-7381 commented

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.

· 4
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Hi @GeertvanderHeijden-5855 ,

Thank you for sharing these information.

Can you login OWA? And have you tried using the localhost to login ECP or OWA?
Do you have multiple servers or load balancers? I've seen the same errors if the not all of the servers installed the SU patch.

And in addition, could you uninstall the SU and see if this could recover the server?

Best regards,
Lou

0 Votes 0 ·

Nope I get on ECP and OWA HTTP 500 error pageI;'ve one server and Exchange is installed local. The install path is D:\Exchange instead of C:\Program Files........
I have already removed the KB5004780 without any result.
Is there a way that I create a log file where you can see more information?

0 Votes 0 ·
ZhengqiLou-MSFT avatar image ZhengqiLou-MSFT GeertvanderHeijden-5855 ·

The ExchangeSetupLog may show something special but I will not suggest you to upload it to a public forum here.
As your install path is D drive, please check the IIS again, it should be D:/.......

And can you login with https://localhost/ecp or owa?

Best regards,
Lou

0 Votes 0 ·

Do you happen to remember what you fixed in your updated? It says StaticFilter but I only have StaticFile. Could that be what you removed?

0 Votes 0 ·
GeertvanderHeijden-5855 avatar image
0 Votes"
GeertvanderHeijden-5855 answered ZhengqiLou-MSFT commented

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://docs.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

· 3
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Hi @GeertvanderHeijden-5855 ,

Do you mean the mail flow stopped working after installed the security update? And still be disabled even uninstall the SU?
Sorry I'm not sure if I properly described the procress, I mean could you use Https://127.0.0.1/ecp to login? And if not, are there any useful error messages?

You could recover this server to another server that joined the same domain.
The recovery steps you could refer to this article: https://practical365.com/recovering-a-failed-exchange-server-2016-server/

In addition, please check if your certificate has been expired.

Best regards,
Lou

0 Votes 0 ·

Dear Lou,

The e-mail does get to the server. We have a spam filter for it and there is no mail inside. When I go to: Https://127.0.0.1/ecp or /owa I get an HTTP 500 error. I have looked at the certificate and it is valid until 2022. Recovery to another server is going to be difficult as I don't have another server.

Where could I possibly see a log why I am getting the HTTP 500 error?

0 Votes 0 ·
ZhengqiLou-MSFT avatar image ZhengqiLou-MSFT GeertvanderHeijden-5855 ·

Hi @GeertvanderHeijden-5855 ,

Thank you for the tests.

So for now the mail flow is correctly working right? Could you login Outlook clients on this server or on some external computers?

The main errors are now the ECP & OWA Error 500, and EMS disabled.

For the EMS error, please try the following methods:

  1. Open Control Panel > System > Advanced system settings > Advanced > Environment Variables > System variables > Check the Value of ExchangeInstallPath, it should be D:......

  2. Open Server Manager > Add roles and features > Go to Features > Check if the WinRM IIS Extension was installed, if so, uninstall and re-install it, if not, install it.

  3. Use the PowerShell of your DC to remote connect to the EMS on your server, see:https://docs.microsoft.com/en-us/powershell/exchange/connect-to-exchange-servers-using-remote-powershell?view=exchange-ps

If this could fix the EMS error, then try repair the ECP & OWA virtual directory with remove- and new- commands.

Best regards,
Lou

0 Votes 0 ·
GeertvanderHeijden-5855 avatar image
0 Votes"
GeertvanderHeijden-5855 answered ZhengqiLou-MSFT commented

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.

· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Hi @GeertvanderHeijden-5855 ,

Can you use the default Microsoft Exchange self-signed certificate instead of your own third-party one? This is to see if the certificate has any mistakes.

And see if this thread has anything helpful for your issue: https://social.technet.microsoft.com/Forums/lync/en-US/5b82f131-b469-4661-9d6c-1c1c7939b73a/the-winrm-client-received-an-http-server-error-status-500?forum=exchange2010

Sorry but I think we have to do some checks for this issue step by step.

And the final option is to uninstall and re-install the Exchange server, hope we don't need to.

Best regards,
Lou

0 Votes 0 ·