This article applies to:
Question:
I am getting an exception error in my Watchdog Logs. What does this error mean and how I fix this?
Reply
If you are receiving the following error or another similar exception error in the Watchdog logs, please know that this error is caused by .NET strict validation of the HTTP headers.
It only accepts HTTP responses that are 100% compliant with the HTTP RFC 2616 Specification but in real world the web server responses might not always be in compliance.
This feature was first introduced in .NET 1.1 SP1 and we have had experienced intermittent problems. The Watchdog Software Version 1.0.00.02 fixes this issue by disabling strict validation as suggested in MSDN.
Watchdog 1 1 14:10:22.882 L Testpoint Exceptions : System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a receive. ---> System.IO.IOException: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. ---> System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host.
Since this error is a simple misinterpretation of the HTTP response, it is not FATAL and does not mean that the R3000 is not correctly filtering.
There is no temporary fix available other than upgrading Watchdog to the above stated version when released. To get details on the release date, please contact 8e6 Technical Support.
- This article was previously published as:
- 8e6 KB 276851
