Getting error connecting to EMS in a recently deployed server: "WinRM cannot process the request because the input XML contains a syntax error"
Getting this error when trying to connect to exchange managment shell in exchange 2013: "WinRM cannot process the request because the input XML contains a syntax error".
What has been done so far:
Exchange server and DC both are on ESXI VM hence checked the time sync and re-sync the time again between DC and exchange VM and host.
Checked the certificates and default websites in IIS manager and getting blank page when browsing the powershell Vdir.
Updated the exchange to latest CU and also the windows server to latest patch.
Ran updatecas.ps1.
replaced the web.config file with that of the working exchange server.
there are two exchange servers in the environment.
Checked the WinRM service and it is running fine.
Any help in this will be appreciated.
What has been done so far:
Exchange server and DC both are on ESXI VM hence checked the time sync and re-sync the time again between DC and exchange VM and host.
Checked the certificates and default websites in IIS manager and getting blank page when browsing the powershell Vdir.
Updated the exchange to latest CU and also the windows server to latest patch.
Ran updatecas.ps1.
replaced the web.config file with that of the working exchange server.
there are two exchange servers in the environment.
Checked the WinRM service and it is running fine.
Any help in this will be appreciated.
You may need to delete and recreate the powershell virtual directory on the server.
ASKER
Will this cause any problem to the server or other functionalities.
can you tell me the best ways to delete and recreate the powershell virtual directory
can you tell me the best ways to delete and recreate the powershell virtual directory
the below link shows you how to remove and recreate the EMS virtual directory. Be sure that you have at least 2 exchange servers because powershell will not work on the one you delete the virtual directory, you will have to recreate from the second server.
https://social.technet.microsoft.com/wiki/contents/articles/51374.exchange-2016-troubleshooting-event-id-4127.aspx
https://social.technet.microsoft.com/wiki/contents/articles/51374.exchange-2016-troubleshooting-event-id-4127.aspx
This question needs an answer!
Become an EE member today
7 DAY FREE TRIALMembers can start a 7-Day Free trial then enjoy unlimited access to the platform.
View membership options
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.