Email Socket Errors

Modified on Tue, 21 Apr at 12:20 PM

TABLE OF CONTENTS

Socket Error 10013:
Socket Error 10053:
Socket Error 10054:

This KB will go through some of the most common socket errors that are encountered by users of Synergetic.

Please note: Socket Errors are not generated by Synergetic, they are generated by the mail server and Synergetic is reporting them. As a result of this, it is outside the scope of Synergetic support to completely resolve these issues and we can only give general advice. Please direct any further questions to your internal ICT team.

Socket Error 10013:

This socket error is usually an intermittent problem with the machine that it occurs on, it is possible that it appears due to network disruptions on that machine or a program that is not properly configured, in which case it won't be intermittent and you will see this happen any time a bulk email or SMS is sent from this machine.

Your ICT department may be able to find a way to stop these errors from occurring, but if this is the first time they have appeared on this machine, there is a chance that a simple restart of that machine may fix it. If that doesn't work, they should look back and see if any newly installed programs might be the culprit.

Potentially useful links:

Microsoft List of Socket Errors (search for 10013)

WSAEACCES10013

Permission denied An attempt was made to access a socket in a way forbidden by its access permissions. An example is using a broadcast address for sendtowithout broadcast permission being set using setsockopt(SO_BROADCAST).Another possible reason for the WSAEACCES error is that when the bind function is called (on Windows NT 4.0 with SP4 and later), another application, service, or kernel mode driver is bound to the same address with exclusive access. Such exclusive access is a new feature of Windows NT 4.0 with SP4 and later, and is implemented by using the SO_EXCLUSIVEADDRUSE option.

Socket Error 10053:

This particular socket error can occur as a result of the mail server being choked by the number of emails coming through - either it thinks that the run is spam and terminates, or possibly the email address being used to send is hitting a limit on how many emails they are allowed to send in a given time period (the server may have some rules on amount sent vs time).

The below config keys may help to prevent the mail server killing the connection:

Potentially Useful Links:

Microsoft List of Socket Errors (Search 10053)

WSAECONNABORTED10053

Software caused connection abort.An established connection was aborted by the software in your host computer, possibly due to a data transmission time-out or protocol error.

Socket Error 10054:

This issue occurs because the TCP/IP driver does not close an incomplete TCP connection. Instead, the TCP/IP driver sends a notification that the TCP/IP driver is ready to receive data when the incomplete TCP connection is created. Therefore, the application receives an instance of the 10054 error that indicates that a connection is reset when the application receives data from the connection.

Potentially Useful Links:

WSAECONNRESET10054

Connection reset by peer.An existing connection was forcibly closed by the remote host. This normally results if the peer application on the remote host is suddenly stopped, the host is rebooted, the host or remote network interface is disabled, or the remote host uses a hard close (see setsockopt for more information on the SO_LINGER option on the remote socket). This error may also result if a connection was broken due to keep-alive activity detecting a failure while one or more operations are in progress. Operations that were in progress fail with WSAENETRESET. Subsequent operations fail with WSAECONNRESET.