TCP Alert (EventCode=4227)

OL Connect Professional
1

The error below came from the event logs. All the event logs are pulled into Splunk and then filtered and emails when event ID 4227 gets triggered. This is copied this right out of the System Event Log on the server. There wasn’t anything else before this alert in the any of the other event logs that would help identify the root cause unfortunately.

Is this a know issue with OL Connect?
Just trying to identify what the cause was and how to prevent this from happening again.

Alert: Planet Press TCP Alert
EventCode=4227

11/18/2023 04:57:33 PM
    LogName=System
    EventCode=4227
    EventType=3
    ComputerName=aaaa9999.corp.aaa.com
    SourceName=Tcpip
    Type=Warning
    RecordNumber=917940
    Keywords=Classic
    TaskCategory=None
    OpCode=None
    Message=TCP/IP failed to establish an outgoing connection because the selected local endpoint was recently used to connect to the same remote endpoint. This error typically occurs when outgoing connections are opened and closed at a high rate, causing all available local ports to be used and forcing TCP/IP to reuse a local port for an outgoing connection. To minimize the risk of data corruption, the TCP/IP standard requires a minimum time period to elapse between successive connections from a given local endpoint to a given remote endpoint.
2

Eventcode 4227 has seems Network Connectivity issue on OS level.

「This error typically occurs when outgoing connections are opened and closed at a high rate, causing all available local ports to be used and forcing TCP/IP to reuse a local port for an outgoing connection.」
Try to refresh the protocol configuration on the network interface by disabling it and then enabling it again.

You can find articles such as the following using search engines, etc.

You can find articles such as the following using search engines, etc.