Answered by:
URL Genie Management Pack

Question
-
Hi,
We have configured URL monitoring in our environment by importing URL Genie management pack . We are receiving critical alerts for few URLS continuously on URL Genie error code monitor but DNS resolution,rechablity, response and status code monitors are healthy for these URL's.
URL Genie Error code -2147954552
Kindly help us in resolving this issue.
Regards,
Venkat
Venkat R
Wednesday, September 5, 2018 6:47 AM
Answers
-
Hi Venkat,
your response (HTP Status Code) is indeed OK - 200. Your SSL certificate seems also fine. I searched a bit and found another post, describing the same error. The error code actually translates to an invalid server response:
ERROR_WINHTTP_INVALID_SERVER_RESPONSE.
So the guy, which solved this has described it in a perfect way here:
Web Application Availability Test: The URL probe returned error code 80072F78. Reason: 0x80072f78
You will have to modify the header and test again. Please keep us updated.
(Please take a moment to "Vote as Helpful" and/or "Mark as Answer" where applicable. This helps the community, keeps the forums tidy, and recognizes useful contributions. Thanks!) Blog: https://blog.pohn.ch/ Twitter: @StoyanChalakov
- Proposed as answer by AlexZhu_775Microsoft contingent staff Thursday, September 6, 2018 2:38 AM
- Marked as answer by Stoyan ChalakovMVP Wednesday, October 31, 2018 3:06 PM
Wednesday, September 5, 2018 9:33 AM
All replies
-
Hi Venkat,
can you please paste the whole error message you see or a screenshot of it?
Thanks in advance!
Regards,
(Please take a moment to "Vote as Helpful" and/or "Mark as Answer" where applicable. This helps the community, keeps the forums tidy, and recognizes useful contributions. Thanks!) Blog: https://blog.pohn.ch/ Twitter: @StoyanChalakov
Wednesday, September 5, 2018 7:44 AM -
Hi
Please find below for the error code in detail
Base Page (show/hide details)
HTTP Status Code
200
Unreachable
false
Error Code
2147954552
DNS Resolution Failure
false
DNS Resolution Time (seconds)
0
TCP Connect Time (seconds)
0
Time To First Byte (seconds)
0
Time To Last Byte (seconds)
0
Redirect Time (seconds)
0
Download Time (seconds)
0
Total Response Time (seconds)
0
Content Size (bytes)
0
Secure Failure Code
0
Certificate will expire in (days)
4294967295
Verb
GET
Version
HTTP/1.1
Certificate Expired
false
Certificate Authority Untrusted
false
Certificate CN Invalid
false
Response Headers
Response Url
internal URL
Request Headers
GET /masters/ HTTP/1.1 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; Trident/7.0; rv:11.0) Content-Type: text/html;charset=ISO-8859-1 Accept-Language: en-US Accept-Charset: ISO-8859-1 From: email(SCOM id) Connection: Keep-Alive
Response Body
See end of page for full Response Body
Venkat R
Wednesday, September 5, 2018 8:46 AM -
Hi Venkat,
your response (HTP Status Code) is indeed OK - 200. Your SSL certificate seems also fine. I searched a bit and found another post, describing the same error. The error code actually translates to an invalid server response:
ERROR_WINHTTP_INVALID_SERVER_RESPONSE.
So the guy, which solved this has described it in a perfect way here:
Web Application Availability Test: The URL probe returned error code 80072F78. Reason: 0x80072f78
You will have to modify the header and test again. Please keep us updated.
(Please take a moment to "Vote as Helpful" and/or "Mark as Answer" where applicable. This helps the community, keeps the forums tidy, and recognizes useful contributions. Thanks!) Blog: https://blog.pohn.ch/ Twitter: @StoyanChalakov
- Proposed as answer by AlexZhu_775Microsoft contingent staff Thursday, September 6, 2018 2:38 AM
- Marked as answer by Stoyan ChalakovMVP Wednesday, October 31, 2018 3:06 PM
Wednesday, September 5, 2018 9:33 AM -
Hi Venkat,
were you able to solve this challenge with the information provided? Appreciate the feedback and thanks in advance!
Regards,
(Please take a moment to "Vote as Helpful" and/or "Mark as Answer" where applicable. This helps the community, keeps the forums tidy, and recognizes useful contributions. Thanks!) Blog: https://blog.pohn.ch/ Twitter: @StoyanChalakov
Monday, October 22, 2018 9:58 AM