Solved

Error while opening exchange powershell in exchange 2010 Sp3

Posted on 2014-03-21
6
572 Views
Last Modified: 2014-03-26
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
Comment
Question by:Krishna Patil
  • 4
  • 2
6 Comments
 
LVL 9

Expert Comment

by:Mahesh Sharma
ID: 39944730
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
 
LVL 3

Author Comment

by:Krishna Patil
ID: 39944797
Also tried EMTSHOOTER.PS1 scripts. BUT no luck
0
 
LVL 9

Expert Comment

by:Mahesh Sharma
ID: 39944814
What's the output of EMTSHOOTER.ps1 script?
0
PRTG Network Monitor: Intuitive Network Monitoring

Network Monitoring is essential to ensure that computer systems and network devices are running. Use PRTG to monitor LANs, servers, websites, applications and devices, bandwidth, virtual environments, remote systems, IoT, and many more. PRTG is easy to set up & use.

 
LVL 3

Author Comment

by:Krishna Patil
ID: 39944833
[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
 
LVL 3

Accepted Solution

by:
Krishna Patil earned 0 total points
ID: 39944863
Issue got autoresolved after correcting host file entries for IPs
0
 
LVL 3

Author Closing Comment

by:Krishna Patil
ID: 39955480
Issue got autoresolved after correcting host file entries for IPs
0

Featured Post

Does Powershell have you tied up in knots?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

How to resolve IMCEAEX NDRs in Exchange or Exchange Online related to invalid X500 addresses.
In-place Upgrading Dirsync to Azure AD Connect
In this video we show how to create a User Mailbox in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Recipients >> Mailb…
This video shows how to quickly and easily add an email signature for all users on Exchange 2016. The resulting signature is applied on a server level by Exchange Online. The email signature template has been downloaded from: www.mail-signatures…

808 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question