• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 629
  • Last Modified:

Error while opening exchange powershell in exchange 2010 Sp3

Getting following error, while opening exchange powershell.

Connecting to remote server 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 return
ed by a HTTP server that does not support the WS-Management protocol. For more information, see the about_Remote_Troubl
eshooting Help topic.
    + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [], PSRemotingTransportExc
   eption
    + FullyQualifiedErrorId : PSSessionOpenFailed


Tried stuff
1. Re-install WinRM add-in
2. Ran WinRM QuickConfig
3. Restarted IIS
4. Rebooted machine.


But no luck, all other exchange tasks are working fine.
0
Krishna Patil
Asked:
Krishna Patil
  • 4
  • 2
1 Solution
 
Mahesh SharmaCommented:
Try below steps:

1.Open IIS Manager, and then navigate to Default Web Site.
2.Right-click Default Web Site, and then click Edit Bindings.
3.If a binding exists for HTTP, clear the host name value.
4.If no binding exists for HTTP, create a new binding that has no host name and a value of All Unassigned for the IP address.
5.Restart IIS.
0
 
Krishna PatilAuthor Commented:
Also tried EMTSHOOTER.PS1 scripts. BUT no luck
0
 
Mahesh SharmaCommented:
What's the output of EMTSHOOTER.ps1 script?
0
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

 
Krishna PatilAuthor Commented:
[Servername.domain.com] Connecting to remote server failed with the following error message : The WinRM client sent
    + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [], PSRemotingTransportExcep
    + FullyQualifiedErrorId : PSSessionOpenFailed
The Exchange Management Troubleshooter successfully completed connecting to:

Servername.domain.com

Failed to connect to any Exchange Server in the current site.

Problem found:

Looking for error...

These are the possible causes for this error:

1. The default http binding has been removed from the Default Web Site. Exchange Powershell needs http to be configured
so that the IP Address is "All Unassigned", the Port is "80", and the Host Name is "".  A common scenario for changing t
his is if you are running multiple web sites, and attempting to set up a redirect to https://mail.company.com/owa by req
uiring SSL on the Default Web Site, and creating another web site to do the redirect back to the SSL-enabled website. Re
mote PowerShell requires port 80 to be available on the Default Web Site for all Internet Addresses. If you want to set
up an automatic redirect to /owa and redirect http requests to https, you should follow the instructions located at:

http://technet.microsoft.com/en-us/library/aa998359(EXCHG.80).aspx

and follow the directions under the section:
"For a Configuration in Which SSL is required on the Default Web Site or on the OWA Virtual Directory in IIS 7.0."

2. The http binding on the Default Web Site has been modified, and the Hostname field configured. To correct this issue,
 you need to clear out the Hostname field under the port 80 bindings on the Default Web Site.

After each error is resolved, close this window and re-run the tool to check for additional problems.
0
 
Krishna PatilAuthor Commented:
Issue got autoresolved after correcting host file entries for IPs
0
 
Krishna PatilAuthor Commented:
Issue got autoresolved after correcting host file entries for IPs
0

Featured Post

Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

  • 4
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now