There are probably many different reasons why this particular PowerShell error can occur on an Exchange server, but this is what happened in my specific case.
The problem was that when I opened the Exchange management shell on one of my two Exchange 2013 test servers it would fail to connect to the local server, and would instead connect to the other server.
The PowerShell window displayed this error.
VERBOSE: Connecting to E15MB2.exchange2013demo.com.
New-PSSession : [e15mb2.exchange2013demo.com] Processing data from remote server e15mb2.exchange2013demo.com failed
with the following error message: The WinRM Shell client cannot process the request. The shell handle passed to the WSMan Shell function is not valid. The shell handle is valid only when WSManCreateShell function completes successfully. Change the request including a valid shell handle and try again. For more information, see the about_Remote_Troubleshooting Help topic.
At line:1 char:1
+ New-PSSession -ConnectionURI “$connectionUri” -ConfigurationName Microsoft.Excha …
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : OpenError: (System.Manageme….RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotingTransportException
+ FullyQualifiedErrorId : -2144108212,PSSessionOpenFailed
The cause of this error in my specific case was that the SSL certificate was no longer bound to the Exchange Back End website on that Exchange 2013 server.
To fix this, in IIS Manager right-click the Exchange Back End website and click Bindings.
Highlight https and click Edit.
If you see “Not selected” like I did, click on Select.
Choose the certificate you want to bind to the site.
Apply the changes and retry the Exchange management shell. If it connects successfully to the server then you have most likely resolved this issue.
Thanks Paul.
Your solution worked for me. The company Exchange server was back on and running.
Thumbs up.
I getting same error and try the some solution as suggested but its not resolved . any idea how to fix it.
I don’t usually leave comments, but I wanted to thank you for sharing knowledge, I was struggling with this problem and the company’s exchange didn’t work.
You saved my day, thanks!!!!
So here is a curve ball…
I and trying to run the Hybrid config tool on my single Ex2016 CU14 server… and I get the WinRM error 403…
I start looking into this and find nothing is wrong on the server, because I can run remote PSSessions from another machine on my domain. No problem what so ever…
But when I try it locally – no go!
Any ideas as to why this is?
thanks! you made my day (evening!)
VERBOSE: Connecting to HT-HO-Exch16.COM.PK
New-PSSession : [HT-HO-Exch16.com.pk] Connecting to remote server HT-HO-Exch16.COM.PK 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
+ New-PSSession -ConnectionURI “$connectionUri” -ConfigurationName Microsoft.Excha …
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : OpenError: (System.Manageme….RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
gTransportException
+ FullyQualifiedErrorId : -2144108297,PSSessionOpenFailed
I have been working with Exchange since 5.5 and throughout the years, Paul Cunningham has been a great resource in many ways and has helped many, many solutions for a long time. Thank you Paul!!!!
This post helped me in a problem I had!
thanks a lot men , it was a certificate issue
Dear Paul,
Thank you very much your blog help me lot,
This solution solved my problem
Hi all
All of a sudden we had on one of our 2013 test servers this error:
Connecting to remote server 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.
I tested the solutions on this side first, but could not solve it.
But in the end i realized, for what ever reason, on this server the folder C:\inetpub\wwwroot was missing.
So i copied this folder from the other 2013 test server, made a iisrest and tata… this solved our issue 🙂
New-PSSession : [mail.server] Connecting to remote server mail.server 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
+ New-PSSession -ConnectionURI “$connectionUri” -ConfigurationName Microsoft.Excha …
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : OpenError: (System.Manageme….RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
gTransportException
+ FullyQualifiedErrorId : -2144108297,PSSessionOpenFailed
Thanks a lot for the tip!
Can someone help me with this error?
New-PSSession : [fvmail13b.fisc.com] Connecting to remote server fvmail13b.fisc.com failed with the following error
message :
[ClientAccessServer=FVMAIL13B,BackEndServer=,RequestId=bb929d1d-c16f-4103-b790-4bfe34123093,TimeStamp=3/9/2017 8:41:31
PM] [FailureCategory=Cafe-HttpProxyException] The process failed to read the Exchange topology in the allotted time.
For more information, see the about_Remote_Troubleshooting Help topic.
At line:1 char:1
+ New-PSSession -ConnectionURI “$connectionUri” -ConfigurationName Microsoft.Excha …
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : OpenError: (System.Manageme….RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
gTransportException
+ FullyQualifiedErrorId : -2144108477,PSSessionOpenFailed
Thank’s Paul
Your posts on Exchange servers helped me a lot!
Kudos to you and your team 😀 😀
For the benefit of everyone, the issue occurred when I did the following:
1. Changed the certificate to a signed one
2. Disabled SSL v3.0 (This is a vulnerability)
3. Restarted the server (required for SSL v3.0 to be disabled)
This solved my problem!
I cannot tell you how many times I’ve had to reinstall 2 virtual machines and 2 physical servers because I’ve kept getting this issue.
I thought for sure it was because I was setting external and internal URLs and must have changed something that should not have been changed.
I then re-installed everything ALL over again, even my AD server.
Yes, it is only me that uses the email server for my personal emails. I do not work for a company doing this, so I was actually able to reinstall the AD.
Then my trial version of Windows Server 2016 would not activate with my MSDN license key.
So I had to redo everything all over again.
Then ran into this issue. I’ve been searching to fix this issue for days… Thankfully this time of reinstalling, I decided to continue to look up a solution.
I used to work for a company that sells POS machines and software for car washes around the world. The system relied heavily on IIS. So I know a little about it… and I knew it had to do something with bindings, but I was one button away the entire time.
I looked at my virtual environment and yes, the SSL certificate was set.
On my physical working environment, it was not.
I had that moment of knowing that was the issue.
Set it, restart IIS, and now Powershell works and now I’m able to access OWA and ECP via the Internet Browser.
Thank you so much!
I linked this article to my Reddit post.
https://www.reddit.com/r/exchangeserver/comments/57c89y/blank_page_when_accessing_owaecp_after_rebooting/
My setting is same, Microsoft Exchange is already selected. I m doing it in my private lab, using self signed cert. There are three EX servers. All has same issue. kindly help
I am running 2 CAS and 2 Mailbox server for Exchange 2013. Powershell connect on backend mailbox server with no problem but on CAS frontend servers, when I launch Powershell, I get an error saying he WinRM client received an HTTP bad request status (400), but the remote service did not include any other information about the cause of the failure.
Kindly please help me resolve this problem. I have searched everywhere and couldn’t find the fix. Looks like this site has help many folks running into exchange issue. I would really appreciate it if someone can help me out with the issue I am having.
VERBOSE: Connecting to B2K12.sample.com.
New-PSSession : [B2K12.sample.com] Processing data from remote server B2K12.sample.com failed with
the following error message: [ClientAccessServer=B2K12,BackEndServer=B2K12.sample.com,RequestId=a40ed21
d-ba2c-4037-98c4-ab6229433c73,TimeStamp=6/18/2016 4:50:41 PM]
[AuthZRequestId=d17bbff7-9c5d-4cf9-a8d1-80cd40926893][FailureCategory=AuthZ-TypeInitializationException] The type
initializer for ‘Nested’ threw an exception. For more information, see the about_Remote_Troubleshooting Help topic.
At line:1 char:1
+ New-PSSession -ConnectionURI “$connectionUri” -ConfigurationName Microsoft.Excha …
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : OpenError: (System.Manageme….RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
gTransportException
+ FullyQualifiedErrorId : IncorrectProtocolVersion,PSSessionOpenFailed
Failed to connect to an Exchange server in the current site.
Enter the server FQDN where you want to connect.:
Please assist.
do you have solved? I’ve the same issue
This fix does not work, simply because my IIS 8.5 server (on a Windows 2012 R2 server), did NOT contain the “Exchange Back End” site. However, all of the Exchange virtual folders and applications ARE all listed under the “Default Web Site” instead. So I tried to do what you said to do, under the “Default Web Site”, and it was already set to “Microsoft Exchange.” Does not work. I still have massive errors when trying to use the Shell or the Administrative Page. This is a BRAND NEW install. Any help would be greatly appreciated!
The Real Person!
Author Paul Cunningham acts as a real person and passed all tests against spambots. Anti-Spam by CleanTalk.
Which Exchange version and server roles have you installed on the server?
I have a same issue with Paul Scott. I used Exchange 2013 and installed already Mailbox and CAS server role with separate VM Machine.
Please Advise!
Thank you and Best Regards,
Mark
The Real Person!
Author Paul Cunningham acts as a real person and passed all tests against spambots. Anti-Spam by CleanTalk.
How far along are you with the deployment? If you’re just starting, consider redeploying as a multi-role server so you’re aligned with best practices.
Hi Paul,
It’s been 3 days already since I’ve got an error. Anyway regarding the best practice, I read it already but have few things that doubt to my mind that why I need any suggestions/help to broad my knowledge.
It did not solve my problem in my own case. i did all as written in the post, but i could not still connect to exchange via the management shell. Kindly find error message below and assist.
Error VERBOSE: Connecting to GLOBAL-EXCHANGE.(domain name).
New-PSSession : [GLOBAL-EXCHANGE.(domain name)] Processing data from remote server
GLOBAL-EXCHANGE.(domain name) failed with the following error message: The WinRM Shell client
cannot process the request. The shell handle passed to the WSMan Shell function is not valid. The shell handle is
valid only when WSManCreateShell function completes successfully. Change the request including a valid shell handle
and try again. For more information, see the about_Remote_Troubleshooting Help topic.
At line:1 char:1
+ New-PSSession -ConnectionURI “$connectionUri” -ConfigurationName Microsoft.Excha …
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : OpenError: (System.Manageme….RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
gTransportException
+ FullyQualifiedErrorId : -2144108212,PSSessionOpenFailed
Failed to connect to an Exchange server in the current site.
Enter the server FQDN where you want to connect.:
thank you
god bless
in a nutshell, you save my job… thanks a lot!
THANK YOU !!!!
Cheers..!! It worked 🙂
Your such a wonderful man and saved me a lot and you like a God:)
You are a gentleman and a scholar. Fixed my issues perfectly
Thank you, thank you thank you
I love you..
worked for me
Thanks a lot.
Thank you for your answer,
having the same issue but can’t get it to work.
probably the ssl doesn’t contain the ex.domain.lan ?
please advise
Thank you so much for your solution! It saved my life today!
Thanks man
Hi Paul,
Thanks, this saved me.
We experienced this issue when we recently replaced a commercial SSL certificate.
Strange enough it took some time before it occurred. Just after several weeks Exchange suddenly crashed and we could not connect to EMS or ECP and clients we also unsuccesful to connect.
Regards,
Raymond
Worked for me! I get to go to bed tonight! Thanks a ton!
Very thank you guy ^^
Fixed my issue!! thanks for the post 😀
Exchange 2013
Very thanks !!!
This solved my problem !
Thanks a lot.
I am facing same issue on Exchange 2010 SP3. How to solve that?
Thanks in advance!
Paul Cunningham saved me one more time! THANK YOU!
You sir, deserve a medal!
You saved my day.
Thank you!
Thank you!
Thank you!
My problem solved
Thanks a lot!
After 1 day of no-exchange 😀
The error was a HTTP 403 on PS
I faced the same issue with my Exchange 2013 MailBoxCAS role and the reason was “The computer object of exchange server (MailBoxCAS ) was not added in “Exchange server” group in AD” after adding in this group and restarting the server this issue was resolved.
I faced the same issue and reason was “The computer object of exchange server was not added in “Exchange server” group in AD” after adding in this group and restarting the server this issue was resolved
You are my Exchange Hero!
THANKS!!!
Pingback: weblink
Pingback: click through the next website page
Worked for me as well. Thanks for the post.
Hi Paul,
Thanks for this post, worked for me, its still obviously fixing a lot of these issues!
Thanks,
Adrian.
thanks for the blogpost!
Thank you very much, like 30 minutes of panic…
THX! My live was saved too this morning 😉
Thanks. This saved my life this mornig. Also had the Problem that I replaced a cert via powershell but it was not updated in IIS.
Just wanted to add to the conversation, I didn’t have the original problem (the cert was still bound in IIS, wasn’t expired), but I was getting the error connecting in powershell.
An iisreset fixed the issue.
Thanks for the article and other comments steering in the right direction.
Man!! What a lifesaver!! Thakxxx
Hello,
I have another problem.
Can you help?
Welcome to the Exchange Management Shell!
Full list of cmdlets: Get-Command
Only Exchange cmdlets: Get-ExCommand
Cmdlets that match a specific string: Help **
Get general help: Help
Get help for a cmdlet: Help or -?
Exchange team blog: Get-ExBlog
Show full output for a command: | Format-List
Show quick reference guide: QuickRef
Tip of the day #29:
Tab completion reduces the number of keystrokes required to complete a cmdlet. Just press the TAB key to complete the cm
dlet you’re typing. Tab completion kicks in whenever there is a hyphen (-) in the input. For example:
Get-Send
should complete to Get-SendConnector. You can even use wildcards, such as:
Get-U*P*
Pressing the TAB key when you enter this command cycles through all cmdlets that match the expression, such as the Unifi
ed Messaging Mailbox policy cmdlets.
VERBOSE: Connecting to SWINDOWS.colop.local.
New-PSSession : [swindows.colop.local] Connecting to remote server swindows.colop.local failed with the following error
message : The WinRM client received an HTTP server error status (500), but the remote service did not include any othe
r information about the cause of the failure. For more information, see the about_Remote_Troubleshooting Help topic.
At line:1 char:1
+ New-PSSession -ConnectionURI “$connectionUri” -ConfigurationName Microsoft.Excha …
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : OpenError: (System.Manageme….RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
gTransportException
+ FullyQualifiedErrorId : WinRMHttpError,PSSessionOpenFailed
VERBOSE: Connecting to SWINDOWS.colop.local.
New-PSSession : [swindows.colop.local] Connecting to remote server swindows.colop.local failed with the following error
message : The WinRM client received an HTTP server error status (500), but the remote service did not include any othe
r information about the cause of the failure. For more information, see the about_Remote_Troubleshooting Help topic.
At line:1 char:1
+ New-PSSession -ConnectionURI “$connectionUri” -ConfigurationName Microsoft.Excha …
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : OpenError: (System.Manageme….RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
gTransportException
+ FullyQualifiedErrorId : WinRMHttpError,PSSessionOpenFailed
VERBOSE: Connecting to SWINDOWS.colop.local.
New-PSSession : [swindows.colop.local] Connecting to remote server swindows.colop.local failed with the following error
message : The WinRM client received an HTTP server error status (500), but the remote service did not include any othe
r information about the cause of the failure. For more information, see the about_Remote_Troubleshooting Help topic.
At line:1 char:1
+ New-PSSession -ConnectionURI “$connectionUri” -ConfigurationName Microsoft.Excha …
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : OpenError: (System.Manageme….RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
gTransportException
+ FullyQualifiedErrorId : WinRMHttpError,PSSessionOpenFailed
VERBOSE: Connecting to SWINDOWS.colop.local.
New-PSSession : [swindows.colop.local] Connecting to remote server swindows.colop.local failed with the following error
message : The WinRM client received an HTTP server error status (500), but the remote service did not include any othe
r information about the cause of the failure. For more information, see the about_Remote_Troubleshooting Help topic.
At line:1 char:1
+ New-PSSession -ConnectionURI “$connectionUri” -ConfigurationName Microsoft.Excha …
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : OpenError: (System.Manageme….RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
gTransportException
+ FullyQualifiedErrorId : WinRMHttpError,PSSessionOpenFailed
VERBOSE: Connecting to SWINDOWS.colop.local.
New-PSSession : [swindows.colop.local] Connecting to remote server swindows.colop.local failed with the following error
message : The WinRM client received an HTTP server error status (500), but the remote service did not include any othe
r information about the cause of the failure. For more information, see the about_Remote_Troubleshooting Help topic.
At line:1 char:1
+ New-PSSession -ConnectionURI “$connectionUri” -ConfigurationName Microsoft.Excha …
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : OpenError: (System.Manageme….RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
gTransportException
+ FullyQualifiedErrorId : WinRMHttpError,PSSessionOpenFailed
Failed to connect to an Exchange server in the current site.
Enter the server FQDN where you want to connect.:
thanks, really helped me.
Thanks alot for this website…
help me to solve more than 80% of the issues i face.
Hello Paul,
Thank you so much. Resolved my issue. Great.
YOU Saved me !!!! Thank you!!!
Solved my issue on too. Great site. Thank you!
Wow. Awesome, dude! You saved my butt.
how would I fix this error foe Ex2010. We installed SP2 Update Rollup 8 and of our 3 mailbox servers the first one spits out this error.
Thank you.
I had to run iisreset from command prompt afterwards but this resolved the issue for me.
Thanks for you help Paul, this site has helped me more than one.
Wery thank’s!
You are my hero! Thanks a lot!!
Thanks Paul, your suggestion worked like a charm!
You are a bl**dy legend mate! 🙂
MVP definitely is the correct title! :))
Thanks again.
Wil
Thanks gain Paul, this resolved the issue with both exchange servers 2013.
Thank you very much for sharing this and other exeriences.
Your blog is great and very helpful in many situations.
Many thanks!
I am getting below error while opening 2013 exchange through epc
Exchange 2013 has been installed newly but Not able to connect through EPC console.
Please check below error and please let me know the solution.
VERBOSE: Connecting to domain.com
New-PSSession : [domain.com] Processing data from remote server domain.com
failed with the following error message: The user “domain.com/Users/Administrator” isn’t assigned to any
management roles. For more information, see the about_Remote_Troubleshooting Help topic.
At line:1 char:1
+ New-PSSession -ConnectionURI “$connectionUri” -ConfigurationName Microsoft.Excha …
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : OpenError: (System.Manageme….RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
gTransportException
+ FullyQualifiedErrorId : IncorrectProtocolVersion,PSSessionOpenFailed
VERBOSE: Connecting to domain.com
New-PSSession : [domain.com] Connecting to remote server domain.com failed
with the following error message : WinRM cannot complete the operation. Verify that the specified computer name is
valid, that the computer is accessible over the network, and that a firewall exception for the WinRM service is
enabled and allows access from this computer. By default, the WinRM firewall exception for public profiles limits
access to remote computers within the same local subnet. For more information, see the about_Remote_Troubleshooting
Help topic.
At line:1 char:1
+ New-PSSession -ConnectionURI “$connectionUri” -ConfigurationName Microsoft.Excha …
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : OpenError: (System.Manageme….RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
gTransportException
+ FullyQualifiedErrorId : WinRMOperationTimeout,PSSessionOpenFailed
VERBOSE: Connecting to domain.com
New-PSSession : [domain.com] Processing data from remote server domain.com
failed with the following error message: The user “domain.com/Users/Administrator” isn’t assigned to any
management roles. For more information, see the about_Remote_Troubleshooting Help topic.
At line:1 char:1
+ New-PSSession -ConnectionURI “$connectionUri” -ConfigurationName Microsoft.Excha …
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : OpenError: (System.Manageme….RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
gTransportException
+ FullyQualifiedErrorId : IncorrectProtocolVersion,PSSessionOpenFailed
VERBOSE: Connecting to domain.com
New-PSSession : [domain.com] Connecting to remote server domain.com failed
with the following error message : WinRM cannot complete the operation. Verify that the specified computer name is
valid, that the computer is accessible over the network, and that a firewall exception for the WinRM service is
enabled and allows access from this computer. By default, the WinRM firewall exception for public profiles limits
access to remote computers within the same local subnet. For more information, see the about_Remote_Troubleshooting
Help topic.
At line:1 char:1
+ New-PSSession -ConnectionURI “$connectionUri” -ConfigurationName Microsoft.Excha …
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : OpenError: (System.Manageme….RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
gTransportException
+ FullyQualifiedErrorId : WinRMOperationTimeout,PSSessionOpenFailed
VERBOSE: Connecting to domain.com
New-PSSession : [domain.com] Processing data from remote server domain.com
failed with the following error message: The user “domain.com/Users/Administrator” isn’t assigned to any
management roles. For more information, see the about_Remote_Troubleshooting Help topic.
At line:1 char:1
+ New-PSSession -ConnectionURI “$connectionUri” -ConfigurationName Microsoft.Excha …
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : OpenError: (System.Manageme….RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
gTransportException
+ FullyQualifiedErrorId : IncorrectProtocolVersion,PSSessionOpenFailed
WARNING: No Exchange servers are available in the Active Directory site CHE. Connecting to an Exchange server in
another Active Directory site.
VERBOSE: Connecting to domain.com
New-PSSession : [domain.com] Connecting to remote server domain.com failed
with the following error message : WinRM cannot complete the operation. Verify that the specified computer name is
valid, that the computer is accessible over the network, and that a firewall exception for the WinRM service is
enabled and allows access from this computer. By default, the WinRM firewall exception for public profiles limits
access to remote computers within the same local subnet. For more information, see the about_Remote_Troubleshooting
Help topic.
At line:1 char:1
+ New-PSSession -ConnectionURI “$connectionUri” -ConfigurationName Microsoft.Excha …
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : OpenError: (System.Manageme….RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
gTransportException
+ FullyQualifiedErrorId : WinRMOperationTimeout,PSSessionOpenFailed
VERBOSE: Connecting to domain.com
New-PSSession : [domain.com] Processing data from remote server domain.com
failed with the following error message: The user “domain.com/Users/Administrator” isn’t assigned to any
management roles. For more information, see the about_Remote_Troubleshooting Help topic.
At line:1 char:1
+ New-PSSession -ConnectionURI “$connectionUri” -ConfigurationName Microsoft.Excha …
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : OpenError: (System.Manageme….RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
gTransportException
+ FullyQualifiedErrorId : IncorrectProtocolVersion,PSSessionOpenFailed
VERBOSE: Connecting to domain.com
New-PSSession : [domain.com] Connecting to remote server domain.com failed
with the following error message : WinRM cannot complete the operation. Verify that the specified computer name is
valid, that the computer is accessible over the network, and that a firewall exception for the WinRM service is
enabled and allows access from this computer. By default, the WinRM firewall exception for public profiles limits
access to remote computers within the same local subnet. For more information, see the about_Remote_Troubleshooting
Help topic.
At line:1 char:1
+ New-PSSession -ConnectionURI “$connectionUri” -ConfigurationName Microsoft.Excha …
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : OpenError: (System.Manageme….RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
gTransportException
+ FullyQualifiedErrorId : WinRMOperationTimeout,PSSessionOpenFailed
VERBOSE: Connecting to domain.com
New-PSSession : [domain.com] Processing data from remote server domain.com
failed with the following error message: The user “domain.com/Users/Administrator” isn’t assigned to any
management roles. For more information, see the about_Remote_Troubleshooting Help topic.
At line:1 char:1
+ New-PSSession -ConnectionURI “$connectionUri” -ConfigurationName Microsoft.Excha …
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : OpenError: (System.Manageme….RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
gTransportException
+ FullyQualifiedErrorId : IncorrectProtocolVersion,PSSessionOpenFailed
Failed to connect to an Exchange server in the current site.
Enter the server FQDN where you want to connect.:
VERBOSE: Connecting to .
New-PSSession : Cannot bind parameter ‘ConnectionUri’. Cannot convert value
“http:///powershell?serializationLevel=Full;ExchClientVer=15.0.516.32;clientApplication=ManagementShell;TargetServer=”
to type “System.Uri”. Error: “Invalid URI: The hostname could not be parsed.”
At line:1 char:30
+ New-PSSession -ConnectionURI “$connectionUri” -ConfigurationName Microsoft.Excha …
+ ~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidArgument: (:) [New-PSSession], ParameterBindingException
+ FullyQualifiedErrorId : CannotConvertArgumentNoMessage,Microsoft.PowerShell.Commands.NewPSSessionCommand
The Real Person!
Author Paul Cunningham acts as a real person and passed all tests against spambots. Anti-Spam by CleanTalk.
“The user “domain.com/Users/Administrator” isn’t assigned to any management roles.”
Either the account has not been assigned any Exchange management permissions, or there is an AD problem preventing the permissions from being enumerated.
Phew, spent a good 2-3 hours on this. Favorited for future reference!
Saved my day too. Thank you so much. It seemed to happened after my C: drive ran out of space.
Many thanks!
this saved my day. thanks a lot.
Thanks a lot, I already received a load of http errors notifying certificate error on 0.0.0.0:444
using netsh http show sslcert and netsh http del sslcert I removed the certificate and still having the same error.
replacing the certificate in IIS per your instructions I got it working again.
*happy person again*
This is my test environment. I have 3 exchange 2013 server with DAG.
I installed the SSL on my three servers after that i am getting the same error one of my server.
Thanks a lot; this solves my problem on Exchange 2013 CU2 V2.
thanks a lot!!!!!!!!!
Solve my problem!
i love you 😉
I don’t have any certificate to select, all the certificates disappear. I couldn’t access ECP nor Powershelll, so, how can i charge a new certificate?
Tx a lot for this. Solved my issue also. Was testing in accordance to the unvalid SAN certs end of 2015. Couldn’t access ECP nor OWA nor Outlook itself. Now I can again 🙂
Thanks a lot; this solves my problem on Exchange 2013 without CU.
I don’t have any proxy server in my environment.
VERBOSE: Connected to EXCAS.domain.com
[PS] C:Windowssystem32>netsh winhttp show proxy
Current WinHTTP proxy settings:
Direct access (no proxy server).
[PS] C:Windowssystem32>
I have one more EXMBX2, that’s working fine. any other solution?
I faced the smae issue. Please check your proxy settings of the IE explorere.
OR check winhttp settings using netsh.
Reset your winhttp settings and bypass the server and your local domain .
If it was similar problem i faced then it should work after resetting the winhttp settings.
I am getting the same error, but your post didn’t fix my issue.
VERBOSE: Connecting to EXMBX.domain.com
New-PSSession : [exmbx.domain.com Connecting to remote server exmbx.domain.com failed with the
following error message : The client cannot connect to the destination specified in the request. Verify that the
service on the destination is running and is accepting requests. Consult the logs and documentation for the
WS-Management service running on the destination, most commonly IIS or WinRM. If the destination is the WinRM service,
run the following command on the destination to analyze and configure the WinRM service: “winrm quickconfig”. For more
information, see the about_Remote_Troubleshooting Help topic.
At line:1 char:1
+ New-PSSession -ConnectionURI “$connectionUri” -ConfigurationName Microsoft.Excha …
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : OpenError: (System.Manageme….RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
gTransportException
+ FullyQualifiedErrorId : CannotConnect,PSSessionOpenFailed
VERBOSE: Connecting to EXCAS.domain.com.
VERBOSE: Connected to EXCAS.domain.com.
PS] C:Windowssystem32>
[PS] C:Windowssystem32>winrm quickconfig
WinRM service is already running on this machine.
WinRM is already set up for remote management on this computer.
PS] C:Windowssystem32>
Can you suggest anything else?
THANKS YOU! This also solved our problem too!
I am very distraught over this version of Exchange and feel this is going to be a huge problem if anything with IIS screws up….. I’m sure this is just the beginning……
Below is the solution that solved my problem to access the management shel and console to exchange 2010.
Before the change
netsh winhttp show proxy
Current WinHTTP proxy settings:
Proxy Server(s) : http=10.214.17.11:8080
Bypass List : (none)
After the change
C:Windowssystem32>netsh winhttp set proxy proxy-server=”http=10.214.17.11:8080″
bypass-list=”*.xxx.com.xx”
Current WinHTTP proxy settings:
Proxy Server(s) : http=10.214.17.11:8080
Bypass List : *.xxx.com.xx
I remember lately that we set the winhttp proxy and did not put any bypas list there.
thanks.
Thank you, fixed my problem!
This solved my problem! Thanks a million 🙂
Thanks for the tip! This was hard to find, but I’m happy you published it.
After installing two servers Exchange 2013 CAS/MAILBOX roles in the environment Exch 2010, I can’t access eighter the EMS or ECP on both servers. I’ve got these mistakes:
EMS Error:
New-PSSession : [s-mail-nd01] Processing data from remote server s-mail-nd01 failed with the
following error message: [Server=s-mail-nd01,RequestId=***********,TimeStamp=*****].
For more information, see the about_Remote_Troubleshooting Help topic.
At line:1 char:1
+ New-PSSession -ConnectionURI “$connectionUri” -ConfigurationName Microsoft.Excha …
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : OpenError: (System.Manageme….RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
gTransportException
+ FullyQualifiedErrorId : -2144108477,PSSessionOpenFailed
ECP Error:
403 Access is denied.
If I exclude server’s name from AD groups: “Exchange Servers” and “Exchange Trusted Subsysem” ECP and EMS begin to start ! But, if it’s right !? What will happen when I begin to organize DAG and migrate mailboxes, without locating the servers in these groups !? Can’t solve this problem for a week.
Very very very thanks !!!
This solved my problem !
YOU ARE A HERO……..
Thanks a lot for the pointer. however exchange product group should fix it along with mapping of other services.
Thanks; but what the heck? Why did it happen in the first place? Oh well…
Did the trick for me! Thanks much! 🙂
Thank you!! This worked for me too.
Thank you! This solved Event ID 15021 that occured in EX2013 after change to a “real” certificate. This was an easy fix, and you found the right buttons 🙂
This blogpost worked for me!
Perfect!
Thanks Paul the problem Solved with these few steps
BIG BIG Thanks!
Had a Blank owa and ecp screen and the same error.
Following youre guide solved my issue!
Big thanks for this workaround. Good luck!
Thank you so much for this nice article problem solved
This solved my problem as well Cheers.
Hi
I had the same problem and with the help of your post, i solved it.
In my case, i had two exchange servers running as VMs with all roles installed. My second VM was created cloning the first before exchange installed. Without knowing this , i installed my second exchange server in the new VM. it went fine. but i had problems executing shell commands and EAC actions (connecting to ex01 and tried creating MDBs in ex02, got Access denied error) from the first exchange server.
Then i came to know about the cloning, so i ran “sysprep” in the second machine and did other network configs and started the server. All exchange services started fine, but i was unable to connect to ecp, powershell, and owa.
I verified the “binding” setting and it was also correct. then i read somewhere in the internet that the self signed certificate might havebeen corrupted. so i created a new self signed certificate for ex02 server from the first exchange server. Then i installed the certificate in the trusted root of the second server and selected the new certificate in the “Binding” setting. it worked well.
Thought of sharing this.
Thanks
Francis.
i was have the same issue and its fix by following your steps thanks alo 🙂
I am seeing similar issue on one of my Exchange 2010 SP3 on W2K12. I cannot use this solution. Do you have another solution to fix this?
Thanks,
pallavi
Thanks !!!!!
Thanks…had this twice now, both times after replacing the IIS cert in Exchange through PowerShell. Confirmed bug?
Thanks , this helped me 🙂
Very very very thanks !!!
This solved my problem !
Thanks a lot.
Petr Kallen
CZECH REPUBLIC
VERBOSE: Connecting to abc.def.LOCAL.
New-PSSession : [abc.def.local] Processing data from remote server abc.def.local failed with the following
error message:
[AuthZRequestId=1e90bc67-a0c9-4000-bf15-a3da81a0f085][FailureCategory=AuthZ-ADTopologyUnexpectedException] Unexpected
error when calling the Microsoft Exchange Active Directory Topology service on server ‘TopologyClientTcpEndpoint
(localhost)’. Error details: Access is denied.. For more information, see the about_Remote_Troubleshooting Help topic.
At line:1 char:1
+ New-PSSession -ConnectionURI “$connectionUri” -ConfigurationName Microsoft.Excha …
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : OpenError: (System.Manageme….RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
gTransportException
+ FullyQualifiedErrorId : IncorrectProtocolVersion,PSSessionOpenFailed
Failed to connect to an Exchange server in the current site.
Enter the server FQDN where you want to connect.:
Could you please give me the solutions
The Real Person!
Author Paul Cunningham acts as a real person and passed all tests against spambots. Anti-Spam by CleanTalk.
“Access is denied” usually means you’re logged on with an account that doesn’t have permissions to connect. A common mistake is logging in with a local account on the server instead of a domain account.
Thanks Paul
I had this issue. wasted around 2 hours for this, i logged in using local account. Thanks for commenting 🙂
Thanks a lot. I had the same issue. Great.