|
@@ -45,6 +45,12 @@ start another send after completing the send of the previous request. While
|
|
|
possible, this is highly unlikely and is probably a programmatic error. The
|
|
|
application should recover on its own.
|
|
|
|
|
|
+% DHCP_DDNS_NCR_UDP_CLEAR_READY_ERROR NCR UDP watch socket failed to clear: %1
|
|
|
+This is an error message that indicates the application was unable to reset the
|
|
|
+UDP NCR sender ready status after completing a send. This is programmatic error
|
|
|
+that should be reported. The application may or may not continue to operate
|
|
|
+correctly.
|
|
|
+
|
|
|
% DHCP_DDNS_NCR_UDP_RECV_CANCELED UDP socket receive was canceled while listening for DNS Update requests: %1
|
|
|
This is an informational message indicating that the listening over a UDP socket for DNS update requests has been canceled. This is a normal part of suspending listening operations.
|
|
|
|
|
@@ -75,20 +81,14 @@ caught in the application's send completion handler. This is a programmatic
|
|
|
error that needs to be reported. Dependent upon the nature of the error the
|
|
|
client may or may not continue operating normally.
|
|
|
|
|
|
-% DHCP_DDNS_WATCH_SOURCE_CLOSE_ERROR Source-side watch socket failed to close: %1
|
|
|
+% DHCP_DDNS_WATCH_SINK_CLOSE_ERROR Sink-side watch socket failed to close: %1
|
|
|
This is an error message that indicates the application was unable to close
|
|
|
-the outbound side of a NCR sender's watch socket. While technically possible
|
|
|
+the inbound side of a NCR sender's watch socket. While technically possible
|
|
|
this error is highly unlikely to occur and should not impair the application's
|
|
|
ability to process requests.
|
|
|
|
|
|
-% DHCP_DDNS_WATCH_SINK_CLOSE_ERROR Sink-side watch socket failed to close: %1
|
|
|
+% DHCP_DDNS_WATCH_SOURCE_CLOSE_ERROR Source-side watch socket failed to close: %1
|
|
|
This is an error message that indicates the application was unable to close
|
|
|
-the inbound side of a NCR sender's watch socket. While technically possible
|
|
|
+the outbound side of a NCR sender's watch socket. While technically possible
|
|
|
this error is highly unlikely to occur and should not impair the application's
|
|
|
ability to process requests.
|
|
|
-
|
|
|
-% DHCP_DDNS_NCR_UDP_CLEAR_READY_ERROR NCR UPD watch socket failed to clear: %1
|
|
|
-This is an error message that indicates the application was unable to reset the
|
|
|
-UDP NCR sender ready status after completing a send. This is programmatic error
|
|
|
-that should be reported. The application may or may not continue to operator
|
|
|
-correctly.
|