Exchange management Powershell Error Message: The WSMan client cannot process the request. Proxy is not supported under HTTP transport.


Exchange management Powershell Error Message:  

 New-PSSession : Connecting to remote server failed with the following error message : The WSMan client cannot process the request. Proxy is not supported under HTTP transport. Change the transport to HTTPS and specify valid proxy information and try again. For more information, see the

about_Remote_Troubleshooting Help topic. 

+                 & $script:NewPSSession `

    + CategoryInfo          : OpenError: (System.Manageme….RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin

   gTransportException

    + FullyQualifiedErrorId : AccessDenied,PSSessionOpenFailed

Exception calling “GetSteppablePipeline” with “1” argument(s): “No session has been associated with this implicit

remoting module”

+             $steppablePipeline = $scriptCmd.GetSteppablePipeline($myInvocation.C …

+     + CategoryInfo          : NotSpecified: (:) [], ParentContainsErrorRecordException

    + FullyQualifiedErrorId : RuntimeException

  Solution:

  •  Verify the session state using the powershell command  – Get-Pssession | fl The value are  All, Opened, Disconnected, Closed, and Broken.
  • Remove the broken powershell session using the command – remove-pssession -id 1
  • Check the internet proxy setting – Go to internet Explorer – Tools – Internet Options – Connections – Lan Settings
  • Verify the netsh winhttp show proxy
  • Export the registry and then delete the WinHttpSettings key from the registry location HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings\Connections\WinHttpSettings

 

Ref: http://blogs.technet.com/b/exchange/archive/2010/02/04/3409289.aspx

        http://exchangeserverpro.com/exchange-2010-certificate-revocation-checks-and-proxy-settings/

Advertisements

About Raji Subramanian

Nothing great to say about me...Just want to share my knowledge for others that will be useful at any moment of time when they stuck in critical issue....
This entry was posted in Commands, Exchange Server, OWA 2013, Uncategorized and tagged , , , , , , . Bookmark the permalink.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s