The Winsock 10054 error signifies that one of the two sides of a socket connection dropped the connection unexpectedly, or that it crashed. The various FoxWeb components use sockets to communicate with each other, so it is hard to determine the type of connection that was dropped.
Here's an overview of FoxWeb's main components:
FoxWeb Broker: This component acts as a broker for FoxWeb channels. Each channel registers with it when it becomes available and individual instances of foxweb.exe and foxweb.dll, serving a particular user request, contact the broker to request a free channel.
FoxWeb Controller: The main purpose of this component is to start FoxWeb channels, as well as kill and restart them if they become unresponsive.
FoxWeb Control: This component is actually part of each channel and handles communications with the broker and foxweb.exe/dll. Each channel loads a separate instance of the FoxWeb Control.
ISAPI/CGI module: This is referred to above as foxweb.exe/dll. A separate process (or thread in the case of the DLL) is instantiated with each incoming FoxWeb request. The module first connects to the broker to get assigned a channel and then contacts the channel and passes the request information to it. The channel in turn executes the requested script and returns the script output to the ISAPI/CGI module, which in turn passes it through to the Web server and from there to the browser.
In this particular case the error is returned by the FoxWeb Control (indivudual channels), but it is not clear which component was on the other side of the connection. Although we have seen similar errors in the past, we have never found evidence suggesting that script execution ever fails or gets interrupted by this problem.