Socket Errors

The LoggerNet Server uses TCP/IP sockets for communications. Various problems can occur with these socket connections. Some of the most common errors and remedies are listed below.

Maximum Number of Sockets Open

The Windows operating system has limits on the number of socket connections that can be held open. For most operations this should be more than enough to cover the open applications that use sockets. One situation that does cause problems is using the IPPorts to communicate with dataloggers where the socket is being opened and closed quickly. For example if you have 20 stations on IPPorts and you do normal data collection every 5 seconds, 20 new sockets are created every 5 seconds. The normal lifetime of the created socket is about 4 minutes leaving about 1000 active sockets at a time. If there are other applications that use sockets, it is possible to exceed the allowed number of sockets.

To work around this problem, either slow down the rate of data collection, or use the Delay Hangup setting for the IP Port (accessed from the Setup Screen) to keep the stations online.

Socket Error Messages

When you get an error message that says Socket Error and a number, check the chart below for the type of error that occurred and what to do about it. Note that these error messages can show up either in pop up error boxes or as part of the LoggerNet Communications log.

Socket Error Messages
Socket Error Number	Message Meaning	User Response to Message
10013	Permission Denied. The requested socket connection has refused the connection.	This is normally a network type of issue. Check with your computer network operator.
10024	Too many open files. Too many open sockets for the applications running.	This can occur when you have many applications that are using sockets running at the same time.
10047	Address family not supported by protocol family. The socket being addressed does not support the type of connection being attempted.	This message shows up when the LoggerNet Toolbar comes up but the server did not come up because TCP/IP is not installed on the computer. Install TCP/IP and restart LoggerNet..
10055	No buffer space available. Cannot create more temporary sockets.	The operating system cannot create any more socket connection. See the text above about Maximum Number of Sockets Open.
10058	Cannot send after socket shutdown. A message was sent to a socket that has been closed.	This would be an indication that an application is not communicating well with the server. Check the application.
10060	Connection timed out.	Either the server has crashed and is not responding or the application did not maintain the connection to the server. Try restarting LoggerNet. This message can also be seen in connection with the NL201 Network Link Interface.
10061	Connection refused. The LoggerNet server or an NL201 refused to allow the socket connection.	This is normally associated with the NL201 and occurs because the last connection did not have enough time to close before a new connection is requested. Slow down the low level polling delay interval.
10065	No route to host. The application is trying to connect to a host address that isn’t in the routing table.	This occurs with remote connections to a LoggerNet server running on another computer. The requested host name can’t be found.