url monitor errors out with results of error code -2147012852 Reason: 0x80072f0c

Question

I'm trying to add a Web Application Availability Monitor in SCOM 2016 to monitor a few URLs but I cannot because I get an error code of 80072F0C - SEE SCREEN SHOTS for more details. I'm plain out of ideas. please help!

GET /v1/sys/health HTTP/1.1
Accept: /
Accept-Language: en-us
Accept-Encoding: GZIP
User-Agent: Microsoft Monitoring Agent 10.19.10014.0
Connection: Keep-Alive

RAW DATA

<DataItem type="Microsoft.SystemCenter.WebApplicationTest.WebTestData" time="2020-09-02T14:59:51.9305365-04:00" sourceHealthServiceId="20F6CC9C-7640-0833-3F24-69F9EA4EBF60"><TransactionResponseTime>0.0843624</TransactionResponseTime><TransactionErrorCode>0</TransactionErrorCode><CollectPerformanceData Type="Boolean">true</CollectPerformanceData><TestTimeout Type="Boolean">false</TestTimeout><TransactionEvalResult>3</TransactionEvalResult><TransactionResponseTimeEvalResult>0</TransactionResponseTimeEvalResult><TransactionErrorCodeEvalResult>1</TransactionErrorCodeEvalResult><RequestResults><RequestResult Id="1"><State>1</State><CollectPerformanceData Type="Boolean">false</CollectPerformanceData><RequestEvalResult>3</RequestEvalResult><BasePageData><ResponseUrl>https://v000000valt1001.tamcentral.asp:8200/v1/sys/health</ResponseUrl><DNSResolutionTime>0</DNSResolutionTime><TCPConnectTime>0</TCPConnectTime><TimeToFirstByte>0</TimeToFirstByte><TimeToLastByte>0</TimeToLastByte><RedirectTime>0</RedirectTime><ContentTime>0</ContentTime><ResponseTime>0</ResponseTime><DownloadTime>0.0843624</DownloadTime><ContentSize>0</ContentSize><StatusCode>0</StatusCode><ErrorCode>2147954444</ErrorCode><Redirected Type="Boolean">false</Redirected><ResponseHeaders></ResponseHeaders><ResponseBody></ResponseBody><SecureFailureCode>0</SecureFailureCode><DaysToExpiry>4294967295</DaysToExpiry><RequestUrl>https://v000000valt1001.tamcentral.asp:8200/v1/sys/health</RequestUrl><RequestHeaders><![CDATA[GET /v1/sys/health HTTP/1.1
Accept: /
Accept-Language: en-us
Accept-Encoding: GZIP
User-Agent: Microsoft Monitoring Agent 10.19.10014.0
Connection: Keep-Alive

]]></RequestHeaders><Verb>GET</Verb><Version>HTTP/1.1</Version><CertificateExpired Type="Boolean">false</CertificateExpired><CertificateAuthorityUntrusted Type="Boolean">false</CertificateAuthorityUntrusted><CertificateCNInvalid Type="Boolean">false</CertificateCNInvalid><DNSResolutionFailure Type="Boolean">false</DNSResolutionFailure><Unreachable Type="Boolean">false</Unreachable><ResponseBodyEvalResult>0</ResponseBodyEvalResult><StatusCodeEvalResult>0</StatusCodeEvalResult><ErrorCodeEvalResult>3</ErrorCodeEvalResult><CheckRedirectsEvalResult>0</CheckRedirectsEvalResult><MonitorSSLEvalResult>0</MonitorSSLEvalResult></BasePageData><ResourceData><AggregateDNSResolutionTime>0</AggregateDNSResolutionTime><AggregateTCPConnectTime>0</AggregateTCPConnectTime><AggregateTimeToFirstByte>0</AggregateTimeToFirstByte><AggregateTimeToLastByte>0</AggregateTimeToLastByte><AggregateRedirectTime>0</AggregateRedirectTime><AggregateContentTime>0</AggregateContentTime><AggregateResponseTime>0</AggregateResponseTime><AggregateContentSize>0</AggregateContentSize><StatusCodeEvalResult>0</StatusCodeEvalResult><ErrorCodeEvalResult>0</ErrorCodeEvalResult></ResourceData></RequestResult></RequestResults></DataItem>

B. Wright

Answer 1

Hello.... I am having the exact same problem; mine just started over the weekend. All of our web servers are behaving as expected.

I think I know the problem, I just don't know how to fix it. (To be clear, we have been doing the following for about 10 years now, it just stopped working...)

This works: (where I always include the HOST NAME in the URL)
Request to: https://myserver.somewhere.com/mypage.html

This no longer works (but used to), when I make the request via IP Address and included the HTTP Header:
Request to: https://{IPAddress}/mypage.html using HTTP Header: myserver.somewhere.com (Hostname matches Binding on IIS server)

I am using another monitoring program as well, and it has NO PROBLEMS accessing the web server using IP address with the HTTP Header.

Yes, I get the correct IP address when I do an nslookup for myserver.somewhere.com. There are no network issues, the problem is isolated to SCOM 2019 doing a test.

Same results as Brian:

Any ideas?

It simply looks like SCOM is not sending the host header tag anymore. (The header tag is of course, quite important, as it tells IIS which web application to bind to.)

Answer 2

Here some more testing results:

I first changed the test to use port 80 only. (No SSL). The SCOM tests all work when it isn't using 443.

I put it back to port 443 (SSL), and the same problem occurred.

I then made this IIS change: For the site binding I added the IP address (so now the binding is showing hostname and IP address) and the SCOM test works! It then stops working if I remove the IP address from the binding. (Very odd, no? The web server only has one IP address. All of the site bindings are based on hostname, and I don't want to start hardcoding IP addresses for deployment sake.)

Again, the web sites are running as expected, it is the SCOM test that isn't working; but now I'm not sure if the issue is from IIS for SCOM.

More details to follow... if anyone has any suggestions it would be appreciated.