Appinsight for Exchange configuration error "The operation failed because of an HTTP error. The HTTP error (12175) is: A security error occurred"

When clicking on configure server for appinsight for exchange get the following error when it gets to the testing connection part.

Remote Configuration Failed

Remote configuration was unsuccessful due to the following: "WinRM test was successful. PowerShell Exchange web site testing failed with the following error:Connecting to remote server failed with the following error message : WS-Management cannot process the request. The operation failed because of an HTTP error. The HTTP error (12175) is: A security error occurred . For more information, see the about_Remote_Troubleshooting Help topic."

Any help appreciated on where to look to figure out what is causing the error.

Find more posts tagged with

appinsight_for_exchange

Accepted answers

aLTeReGo

This error has only once been reported by another user, but fortunately they were kind enough to share with us the steps they followed to ultimately resolved it.

It turns out to have been a non-standard IIS setting. The PowerShell virtual directory had two settings that were not expected:

1. The PowerShell virtual directory SSL Settings | Client certificates was set to Accept instead of Ignore
2. The Default Web Site had SSL Settings | Require SSL

Item #1 was probably requesting a SSL client certificate from SolarWinds, and was the source of the problem. Once removed, AppInsight for Exchange lit up. I went ahead and completed the “Configure Server” successfully.
Item #2 implicitly set PowerShell virtual directory to require SSL, which is known to break remote PowerShell. Oddly enough, when I removed the setting from the Default Web Site, SolarWinds AppInsight for Exchange continued to report in, so I don’t believe this setting was the root cause.

I have since then configured the "Require SSL" back to their best practices setting. I believe a prior Exchange administrator was attempting to redirect HTTP to HTTPS for OWA access, and did so incorrectly. That has been corrected. Since the solution was so non-standard, it was difficult googling our symptoms and finding solution from other administrators that had the same issue.
These explain the correct procedure to redirect HTTP to HTTPS:
http://www.techrepublic.com/blog/the-enterprise-cloud/exchange-2010-how-to-redirect-non-ssl-outlook-web-app-traffic-to-ssl/
http://briandesmond.com/blog/redirecting-owa-urls-in-exchange-2010

All comments

aLTeReGo

This error has only once been reported by another user, but fortunately they were kind enough to share with us the steps they followed to ultimately resolved it.

It turns out to have been a non-standard IIS setting. The PowerShell virtual directory had two settings that were not expected:

1. The PowerShell virtual directory SSL Settings | Client certificates was set to Accept instead of Ignore
2. The Default Web Site had SSL Settings | Require SSL

Item #1 was probably requesting a SSL client certificate from SolarWinds, and was the source of the problem. Once removed, AppInsight for Exchange lit up. I went ahead and completed the “Configure Server” successfully.
Item #2 implicitly set PowerShell virtual directory to require SSL, which is known to break remote PowerShell. Oddly enough, when I removed the setting from the Default Web Site, SolarWinds AppInsight for Exchange continued to report in, so I don’t believe this setting was the root cause.

I have since then configured the "Require SSL" back to their best practices setting. I believe a prior Exchange administrator was attempting to redirect HTTP to HTTPS for OWA access, and did so incorrectly. That has been corrected. Since the solution was so non-standard, it was difficult googling our symptoms and finding solution from other administrators that had the same issue.
These explain the correct procedure to redirect HTTP to HTTPS:
http://www.techrepublic.com/blog/the-enterprise-cloud/exchange-2010-how-to-redirect-non-ssl-outlook-web-app-traffic-to-ssl/
http://briandesmond.com/blog/redirecting-owa-urls-in-exchange-2010

gyoung

That was it, it's working now.

Thanks