eG Help

In computing, the Windows Sockets API (WSA), which was later shortened to Winsock, is a technical specification that defines how Windows network software should access network services, especially TCP/IP. It defines a standard interface between a Windows TCP/IP client application (such as an FTP client or a web browser) and the underlying TCP/IP protocol stack. The WinSockTest test scans the Windows event logs for winsock-related errors and reports the count of such errors.

Measurement	Description	Measurement Unit	Interpretation
Send_errors	Indicates the number of send errors captured by the event log during the last measurement period.	Number	The send function and WSAsend functions send data on a connected socket. The value of this measure will be incremented when errors are returned on failed send and WSAsend requests. Ideally, the value of this measure should be 0. In case of a non-zero value, use the detailed diagnosis of this measure to know what send errors occurred. Typically, event IDs 1003, 1005, 1007, 1011, 1013, and 3007 are classified as send errors.
Receive_errors	Indicates the number of receive errors captured by the event log during the last measurement period.	Number	The recv, WSARecv, and WSARecvEx functions receive data from a connected socket or a bound connectionless socket. If the recv, WSARecv, and WSARecvEx requests fail and return errors, such errors are captured by the event log. The value of this measure represents the count of these errors. Ideally, the value of this measure should be 0. In case of a non-zero value, use the detailed diagnosis of this measure to know what receive errors occurred. Typically, event IDs 1004, 1006, 1009, 1012, 1015 are classified as receive errors.
Connect_errors	Indicates the number of connect errors captured by the event log during the last measurement period.	Number	The connect, ConnectEx, WSAConnect, WSAConnectByList, or WSAConnectByName functions typically establish a connection to a specified socket. If calls to these functions fail owing to errors, such error events are captured by the event logs. The value of this measure denotes the count of such errors. Ideally, the value of this measure should be 0. In case of a non-zero value, use the detailed diagnosis of this measure to know what connect errors occurred. Typically, event IDs 1017, 1018, 1020, 1021, 3006 are classified as connect errors.
Accept_errors	Indicates the number of accept errors that occurred during the last measurement period.	Number	The accept, AcceptEx, and WSAAccept functions permit an incoming connection attempt on a socket. If calls to any of these functions fail, then the errors causing the failures are captured by the event logs. The value of this measure denotes the count of such errors. Ideally, the value of this measure should be 0. In case of a non-zero value, use the detailed diagnosis of this measure to know what accept errors occurred. Typically, event IDs 1023, 1024, 1026, 1027 are classified as accept errors.
Bind_errors	Indicates the number of bind errors that occurred during the last measurement period.	Number	If the implicit or explicit binding of a socket handle fails, then errors causing the bind failure will be captured by the event logs. The value of this measure denotes the count of such errors. Ideally, the value of this measure should be 0. In case of a non-zero value, use the detailed diagnosis of this measure to know what bind errors occurred. Typically, event IDs 1029 and 1030 are classified as bind errors.
Abort_errors	Indicates the number of abort errors that occurred during the last measurement period.	Number	An abort/cancel operation can be Winsock-initiated or transport-initiated. The value of this measure represents the count of both types of abort operations. A Winsock-initiated abort can occur due to the following reasons: An abort due to unread receive data buffered after close An abort after a call to the shutdown function with the how parameter set to SD_RECEIVE and a call to the closesocket function with receive data pending. An abort after a failed attempt to flush the endpoint. An abort after an internal Winsock error occurred. An abort due to a connection with errors and the application previously requested that the connection be aborted on certain circumstances. One example of this case would be an application that set SO_LINGER with a timeout of zero and there is still unacknowledged data on the connection. An abort on a connection not fully associated with accepting endpoint. An abort on a failed call to the accept or AcceptEx function. An abort due to a failed receive operation. An abort due to a Plug and Play event. An abort due to a failed flush request. An abort due to a failed expedited data receive request. An abort due to a failed send request. An abort due to canceled send request. An abort due to a canceled called to the TransmitPackets function. A transport-initiated abort can occur if a reset is indicated by the transport. Ideally, the value of this measure should be 0. In case of a non-zero value, use the detailed diagnosis of this measure to why aborts occurred. Typically, event IDs 1032 and 1033 are classified as abort errors.
Listen_errors	Indicates the number of listen errors that occurred during the last measurement period.	Number	Ideally, the value of this measure should be 0. In case of a non-zero value, use the detailed diagnosis of this measure to know what listen errors occurred. Typically, event IDs 1026 and 1037 are classified as listen errors.
Indication_errors	Indicates the number of indication errors that occurred during the last measurement period.	Number	An indicated operation can be: A connection indicated operation: This occurs when an application receives a connection request. A data indicated operation: This occurs when an application receives data on a connected socket. Data indicated from transport operations: This occurs when an application posts a receive request and receives data. Disconnect indicated from transport operations: This occurs when an application receives a disconnect indication. Errors in these processes are categorized under Indication errors. Ideally, the value of this measure should be 0. In case of a non-zero value, use the detailed diagnosis of this measure to know what indication errors occurred. Typically, event IDs 3000, 3001, 3003, 3004 are classified as indication errors.
Other_errors	Indicates the number of other errors that occurred during the last measurement period.	Number	Errors that cannot be classified as send, receive, connect, accept, bind, abort, listen, or indication, will be grouped under Other errors. Ideally, the value of this measure should be 0. In case of a non-zero value, use the detailed diagnosis of this measure to know what other errors occurred. Typically, event IDs 1000,1001,1002,1035 are classified as other errors.