SOLVED

Exchange 2013 EMS error upon open

%3CLINGO-SUB%20id%3D%22lingo-sub-3071739%22%20slang%3D%22en-US%22%3EExchange%202013%20EMS%20error%20upon%20open%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3071739%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%3CP%3EI%20get%20the%20following%20error%20when%20opening%20EMS%20on%20my%20local%202013%20server%20(or%20remotely).%20EMS%20has%20worked%20fine%20up%20until%20recently%20and%20I'm%20not%20sure%20what%20caused%20the%20issue.%20I've%20read%20many%20articles%20and%20forum%20posts%20and%20none%20of%20the%20suggestions%20have%20worked.%3C%2FP%3E%3CP%3EThanks%2C%3C%2FP%3E%3CP%3ETravis%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EError%3A%3C%2FP%3E%3CP%3E%26nbsp%3BNew-PSSession%20%3A%20%5Bservername%5D%20Connecting%20to%20remote%20server%20servername%20failed%20with%20the%3CBR%20%2F%3Efollowing%20error%20message%20%3A%20The%20WinRM%20client%20sent%20a%20request%20to%20an%20HTTP%20server%20and%20got%20a%20response%20saying%20the%20requested%3CBR%20%2F%3EHTTP%20URL%20was%20not%20available.%20This%20is%20usually%20returned%20by%20a%20HTTP%20server%20that%20does%20not%20support%20the%20WS-Management%3CBR%20%2F%3Eprotocol.%20For%20more%20information%2C%20see%20the%20about_Remote_Troubleshooting%20Help%20topic.%3CBR%20%2F%3EAt%20line%3A1%20char%3A1%3CBR%20%2F%3E%2B%20New-PSSession%20-ConnectionURI%20%22%24connectionUri%22%20-ConfigurationName%20Microsoft.Excha%20...%3CBR%20%2F%3E%2B%20~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~%3CBR%20%2F%3E%2B%20CategoryInfo%20%3A%20OpenError%3A%20(System.Manageme....RemoteRunspace%3ARemoteRunspace)%20%5BNew-PSSession%5D%2C%20PSRemotin%3CBR%20%2F%3EgTransportException%3CBR%20%2F%3E%2B%20FullyQualifiedErrorId%20%3A%20URLNotAvailable%2CPSSessionOpenFailed%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-3071739%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EExchange%20Server%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
New Contributor

Hi,

I get the following error when opening EMS on my local 2013 server (or remotely). EMS has worked fine up until recently and I'm not sure what caused the issue. I've read many articles and forum posts and none of the suggestions have worked.

Thanks,

Travis

 

Error:

 New-PSSession : [servername] Connecting to remote server servername failed with the
following error message : The WinRM client sent a request to an HTTP server and got a response saying the requested
HTTP URL was not available. This is usually returned by a HTTP server that does not support the WS-Management
protocol. 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 : URLNotAvailable,PSSessionOpenFailed

1 Reply
best response confirmed by tmacie (New Contributor)
Solution

@tmacie I have figured this out. A binding got wiped out on IIS. I don't know why it didn't occur to me, but our internal DNS scheme is different than our external. I had to re-add the binding for the internal servername.