This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(12.8, 71%, 11%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EGY%3C/text%3E%3C/svg%3E)
Hi,
I have Exchange 2016. I failed to open Exchange Management Shell. The issue happened after I patched CU23. The error message is below.
New-PSSession : [Exchange.mycompany.com] Connecting to remote server Exchange.mycompany.com failed with
the following error message : The WinRM client cannot process the request. It cannot determine the content type of the
HTTP response from the destination computer. The content type is absent or invalid. For more information, see the
about_Remote_Troubleshooting Help topic.
At line:1 char:1
gTransportException
Please help!
Thanks,
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(198.4, 62%, 29%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJZ%3C/text%3E%3C/svg%3E)
Hi @Grace Yin ,
According to error messages, here are some troubleshooting steps for your reference and hope these help you:
Above solution is mentioned in the blog you could refer to it: How to fix problems related to remote PowerShell connections
Detailed information: The WinRM Shell Client Cannot Process the Request
A similar thread for your reference as well: Exch 2016 Management Shell Broken - TheWinRM client cannot process the request
Please Note: Since the web sites are not hosted by Microsoft, the links may change without notice. Microsoft does not guarantee the accuracy of this information.
If an Answer is helpful, please click "Accept Answer" and upvote it. If you have extra questions about this answer, please click "Comment".
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.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(118.4, 81%, 21%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMV%3C/text%3E%3C/svg%3E)
Thank you. New binding of Certificate for Exchange Back End works great.
Thank you for your reply. I have verified all above and confirmed all are configured correctly.
By the way, I have another Exchange server which is configured as failover with this Exchange server. I am able to launch EMS on that one with the same login account.
It seems CU23 broke something on this server, but I failed to run CU23 setup.exe to repair it.
Any idea?
Please help!
Hi @Joy Zhang-MSFT ,
Could you please check if there is any error message in the exchange setup logs?
Comparing the web.config files between these 2 exchange servers and see if there is any difference, especially path.
If all of above still cannot help you to resolve the issue, you maybe need recover a Failed Exchange 2016 CU Installation.
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.
Hi @Joy Zhang-MSFT ,
Thank you very much for your reply. The issue has been resolved by following the link below.
I am able to launch EMS now, however I still can't open ECP. The error is below
Parser Error Message: Could not load file or assembly 'Microsoft.Exchange.Clients.Strings, Version=15.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified.
Source Error:
Line 61: the compiler. All assemblies in the GAC and owa\bin are referenced automatically.
Line 62: -->
Line 63: <add assembly="Microsoft.Exchange.Clients.Strings, Version=15.0.0.0, Culture=neutral, publicKeyToken=31bf3856ad364e35" />
Line 64: <add assembly="Microsoft.Exchange.Data.Directory, Version=15.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" />
Line 65: <add assembly="Microsoft.Exchange.Clients.Common, Version=15.0.0.0,Culture=neutral, publicKeyToken=31bf3856ad364e35" />
Source File: C:\Program Files\Microsoft\Exchange Server\V15\FrontEnd\HttpProxy\ecp\web.config Line: 63
Assembly Load Trace: The following information can be helpful to determine why the assembly 'Microsoft.Exchange.Clients.Strings, Version=15.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' could not be loaded.
I checked the exchange setup logs and there are a few errors, not sure if it is related.
[ERROR-REFERENCE] Id=AllRolesPreFileCopyComponent___2f7e3804a2b340c69e930798211fb8fd Component=EXCHANGE14:\Current\Release\Shared\Datacenter\Setup
[ERROR] The term 'C:\Program Files\Microsoft\Exchange Server\V15\Bin\ManageScheduledTask.ps1' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
[ERROR] The following error was generated when "$error.Clear();
& $RoleBinPath\ServiceControl.ps1 -Operation:DisableServices -Roles:($RoleRoles.Replace('Role','').Split(',')) -SetupScriptsDirectory:$RoleBinPath;
& $RoleBinPath\ServiceControl.ps1 -Operation:Stop -Roles:($RoleRoles.Replace('Role','').Split(',')) -IsDatacenter:([bool]$RoleIsDatacenter)
Hi @Joy Zhang-MSFT ,
Thank you very much for your reply. I followed your instructions. I ran Enable-PSRemoting on the Exchange server. I verified the SSL cert which is installed and valid. I changed the physical path and restarted IIS.
Now I got the error below when I launched EMS.
New-PSSession : [Exchange.mycompany.com] Processing data from remote server Exchange.mycompany.com failed
with the following error message: The EndpointConfiguration with the
http://schemas.microsoft.com/powershell/Microsoft.Exchange identifier is not in a valid initial session state on the
remote computer. Contact your Windows PowerShell administrator, or the owner or creator of the endpoint configuration.
For more information, see the about_Remote_Troubleshooting Help topic.
At line:1 char:1
Please advise!
Thank you!
Hi @Joy Zhang-MSFT ,
I have done research on the error message, here's a solution mentioned in the blog to fix the error. Hope it help your issue.
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.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(268.8, 4%, 36%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESC%3C/text%3E%3C/svg%3E)
Good day
I just wanted to thank you for this thread, we rebooted our core switches and it caused a bunch of errors on our primary Exchange server, thankfully we have a DAG and the secondary server was performing customer request. My first issue was I could not open the ECP or get PowerShell to connect on the primary. I checked the Binding on our HTTPS port and it was no longer bound to our certificate. I remedied that and it came up and Exchange PS connected. I still have a "BAD COPY COUNT" on my primary but at least now I can utilize PS. Thank you again for all the help.