2 comments
.NET 
Operations manager 2007 offers the possibility to monitor your websites from a client perspective through Web Application Monitoring. After setting up the monitoring you point out watcher nodes to perform the actual monitoring for you. These watcher nodes simulate the client perspective. It’s okay if these nodes are in the same network, but even better if it’s possible to perform the monitoring from agents that do not reside in your network.
When the monitors start to alert on errors it’s not always obvious to see what went wrong.
Here’s an example:
The console shows us that Request 1 of an SSL-website https://[website].nl had an error. Preferably we would like the ’alert details’ to provide us with some context on the error that occurred. The alert description shows us nothing however, so we need to dig into the alert:
- Right-click the alert and open up the health explorer (this is also possible from the task menu on the right hand side in the console);
The health explorer now show us that there was an error code failure on the basepage, and when we click the error code failure in the tree we might be able to dig in some more by clicking the ‘state change events (#)’ tab in the details pane. If we click ‘(show/hide details)’ this is what we see:
Since the tree clearly states that there’s an error code failure on the basepage we want to concentrate on the ‘error code’ and the error code is 2147954575. If you would look at list below it now becomes clear that the error code is ERROR_WINHTTP_SECURE_FAILURE. In other words, there’s something wrong with the certificate, and that’s exactly what you see when you go to the website:
|
Error code |
Status or Value |
|
100 |
HTTP_STATUS_CONTINUE |
|
101 |
HTTP_STATUS_SWITCH_PROTOCOLS |
|
200 |
HTTP_STATUS_OK |
|
201 |
HTTP_STATUS_CREATED |
|
202 |
HTTP_STATUS_ACCEPTED |
|
203 |
HTTP_STATUS_PARTIAL |
|
204 |
HTTP_STATUS_NO_CONTENT |
|
205 |
HTTP_STATUS_RESET_CONTENT |
|
206 |
HTTP_STATUS_PARTIAL_CONTENT |
|
207 |
HTTP_STATUS_WEBDAV_MULTI_STATUS |
|
300 |
HTTP_STATUS_AMBIGUOUS |
|
301 |
HTTP_STATUS_MOVED |
|
302 |
HTTP_STATUS_REDIRECT |
|
303 |
HTTP_STATUS_REDIRECT_METHOD |
|
304 |
HTTP_STATUS_NOT_MODIFIED |
|
305 |
HTTP_STATUS_USE_PROXY |
|
307 |
HTTP_STATUS_REDIRECT_KEEP_VERB |
|
400 |
HTTP_STATUS_BAD_REQUEST |
|
401 |
HTTP_STATUS_DENIED |
|
402 |
HTTP_STATUS_PAYMENT_REQ |
|
403 |
HTTP_STATUS_FORBIDDEN |
|
404 |
HTTP_STATUS_NOT_FOUND |
|
405 |
HTTP_STATUS_BAD_METHOD |
|
406 |
HTTP_STATUS_NONE_ACCEPTABLE |
|
407 |
HTTP_STATUS_PROXY_AUTH_REQ |
|
408 |
HTTP_STATUS_REQUEST_TIMEOUT |
|
409 |
HTTP_STATUS_CONFLICT |
|
410 |
HTTP_STATUS_GONE |
|
411 |
HTTP_STATUS_LENGTH_REQUIRED |
|
412 |
HTTP_STATUS_PRECOND_FAILED |
|
413 |
HTTP_STATUS_REQUEST_TOO_LARGE |
|
414 |
HTTP_STATUS_URI_TOO_LONG |
|
415 |
HTTP_STATUS_UNSUPPORTED_MEDIA |
|
449 |
HTTP_STATUS_RETRY_WITH |
|
500 |
HTTP_STATUS_SERVER_ERROR |
|
501 |
HTTP_STATUS_NOT_SUPPORTED |
|
502 |
HTTP_STATUS_BAD_GATEWAY |
|
503 |
HTTP_STATUS_SERVICE_UNAVAIL |
|
504 |
HTTP_STATUS_GATEWAY_TIMEOUT |
|
505 |
HTTP_STATUS_VERSION_NOT_SUP |
|
2147954401 |
ERROR_WINHTTP_OUT_OF_HANDLES |
|
2147954402 |
ERROR_WINHTTP_TIMEOUT |
|
2147954404 |
ERROR_WINHTTP_INTERNAL_ERROR |
|
2147954405 |
ERROR_WINHTTP_INVALID_URL |
|
2147954406 |
ERROR_WINHTTP_UNRECOGNIZED_SCHEME |
|
2147954407 |
ERROR_WINHTTP_NAME_NOT_RESOLVED |
|
2147954409 |
ERROR_WINHTTP_INVALID_OPTION |
|
2147954411 |
ERROR_WINHTTP_OPTION_NOT_SETTABLE |
|
2147954412 |
ERROR_WINHTTP_SHUTDOWN |
|
2147954415 |
ERROR_WINHTTP_LOGIN_FAILURE |
|
2147954417 |
ERROR_WINHTTP_OPERATION_CANCELLED |
|
2147954418 |
ERROR_WINHTTP_INCORRECT_HANDLE_TYPE |
|
2147954419 |
ERROR_WINHTTP_INCORRECT_HANDLE_STATE |
|
2147954429 |
ERROR_WINHTTP_CANNOT_CONNECT |
|
2147954430 |
ERROR_WINHTTP_CONNECTION_ERROR |
|
2147954432 |
ERROR_WINHTTP_RESEND_REQUEST |
|
2147954437 |
ERROR_WINHTTP_SECURE_CERT_DATE_INVALID |
|
2147954438 |
ERROR_WINHTTP_SECURE_CERT_CN_INVALID |
|
2147954444 |
ERROR_WINHTTP_CLIENT_AUTH_CERT_NEEDED |
|
2147954445 |
ERROR_WINHTTP_SECURE_INVALID_CA |
|
2147954457 |
ERROR_WINHTTP_SECURE_CERT_REV_FAILED |
|
2147954500 |
ERROR_WINHTTP_CANNOT_CALL_BEFORE_OPEN |
|
2147954501 |
ERROR_WINHTTP_CANNOT_CALL_BEFORE_SEND |
|
2147954502 |
ERROR_WINHTTP_CANNOT_CALL_AFTER_SEND |
|
2147954503 |
ERROR_WINHTTP_CANNOT_CALL_AFTER_OPEN |
|
2147954550 |
ERROR_WINHTTP_HEADER_NOT_FOUND |
|
2147954552 |
ERROR_WINHTTP_INVALID_SERVER_RESPONSE |
|
2147954553 |
ERROR_WINHTTP_INVALID_HEADER |
|
2147954554 |
ERROR_WINHTTP_INVALID_QUERY_REQUEST |
|
2147954555 |
ERROR_WINHTTP_HEADER_ALREADY_EXISTS |
|
2147954556 |
ERROR_WINHTTP_REDIRECT_FAILED |
|
2147954557 |
ERROR_WINHTTP_SECURE_CHANNEL_ERROR |
|
2147954566 |
ERROR_WINHTTP_BAD_AUTO_PROXY_SCRIPT |
|
2147954567 |
ERROR_WINHTTP_UNABLE_TO_DOWNLOAD_SCRIPT |
|
2147954569 |
ERROR_WINHTTP_SECURE_INVALID_CERT |
|
2147954570 |
ERROR_WINHTTP_SECURE_CERT_REVOKED |
|
2147954572 |
ERROR_WINHTTP_NOT_INITIALIZED |
|
2147954575 |
ERROR_WINHTTP_SECURE_FAILURE |
|
2147954578 |
ERROR_WINHTTP_AUTO_PROXY_SERVICE_ERROR |
|
2147954579 |
ERROR_WINHTTP_SECURE_CERT_WRONG_USAGE |
|
2147954580 |
ERROR_WINHTTP_AUTODETECTION_FAILED |
|
2147954581 |
ERROR_WINHTTP_HEADER_COUNT_EXCEEDED |
|
2147954582 |
ERROR_WINHTTP_HEADER_SIZE_OVERFLOW |
|
2147954583 |
ERROR_WINHTTP_CHUNKED_ENCODING_HEADER_SIZE_OVERFLOW |
|
2147954584 |
ERROR_WINHTTP_RESPONSE_DRAIN_OVERFLOW |
|
2147954585 |
ERROR_WINHTTP_CLIENT_CERT_NO_PRIVATE_KEY |
|
2147954586 |
ERROR_WINHTTP_CLIENT_CERT_NO_ACCESS_PRIVATE_KEY |
|
2147954586 |
WINHTTP_ERROR_LAST |
2 comments
I am getting error code 80072EFE error while configuring web url monitoring in SCOM 2012 checked many solutions but can’t find appropriate solution.
Don’t know whether it is proxy related, or certificate related also modified my advanced setting in IE on watcher node by leaving TLS,SSL all checked.
Cannot install some third party tool.
Muzamil
Hello Muzamil,
The error 0x80072EFE you are getting is “ERROR_INTERNET_CONNECTION_ABORTED The connection with the server has been terminated.”. This termination could take place client- or serverside. Although I do not have an insight in your environment this problem could be proxy- or security related.
The first things I would do is try to log on locally to the watcher node and:
* try to open the website manually under the user context of the account you are using to monitor the website. You should be getting the same error;
* Ping the website and make sure name resolution works as expected;
* If a hosts-file is used instead of DNS then make sure “Automatically detect settings” is turned off under “internet options” > “LAN Settings”;
* If a proxy client is used make sure the user has rights to visit the website;
* Is there a firewall in between that restricts access to or from the specified Watcher node or Website?
* Does the website itself have any ip restrictions?
* If the site uses SSL, does the client support the ciphers that the server supports or is there an incompatibility (could you check serverside)? or
* Is the client unable to verify the certificate (trust issue)?
You could also try to use a network sniffer to check if and why a network connection is being aborted.
Hope this helps.
Cheers,
Mark Wolzak
Mark Wolzak