I did see that before I posted but I was confused as to what it means and where it was originating. I narrowed it down to the machine which was running OpenSTA but I still don't know how to fix it. Here is the error defined from your page:
No buffer space available.
An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full.
[This message has been edited by Papa Perf (edited 05-19-2003).]
Address already in use.
Typically, only one usage of each socket address (protocol/IP address/port) is permitted. This error occurs if an application attempts to bind a socket to an IP address/port that has already been used for an existing socket, or a socket that was not closed properly, or one that is still in the process of closing.
It's almost like the socket is never released by the virtual user. I disconnect and exit at the end of each script. What am I missing?
Error 10055 occurs when the system has not enough memory or other system resources to open new TCP/IP socket or to handle socket data.In most cases the problem occurs when total count of opened sockets reaches some magical number. MicroSoft writes that this limit is 3976 simultaneously opened sockets but it seems that on Win9x systems the real limit is much lower.
Proxy uses permanently about 10-20 opened sockets (it depends on configuration, number of defined Mapped Links,...) and each client request allocates two sockets - one for client side and one for server side of connection. Because TCP/IP system doesn't free sockets immediately when they are closed (socket remains allocated for 240 seconds after application closes it) it is possible that system will report this error due to lack of free socket resources.
You can obtain a list of opened sockets (including sockets in close state) using netstat utility:
Run DOS Prompt and then type:
netstat -an | more
when you will press the Enter key you see a list of opened sockets (you will see big number in *_WAIT state probably).