Some really old versions of FoxWeb had a bug that would keep socket connections open for a few minutes after they were needed. This would cause problems on some busy servers. I believe that this problem was fixed with the release of FoxWeb version 3.
You should be able to determine if this is the problem by running the following command in a CMD window and sending me the file netstat.txt, which gets created by this command in the current folder:
netstat -a -p tcp -b > netstat.txt
By the way, the email address you configured in the forum preferences seems to be incorrect, because notification messages are bouncing back to our mail servers with the error "
Sent by Gabriel Badea on 11/18/2008 12:41:38 PM:
Hi, thanks for the speedy reply.
I was asked to troubleshoot the problem this morning. I do not have access to the server yet but I'll get back to you with the required info in a day or two and I'll let you know if rebooting fixed the problem. The problem occurs with every call to a fwx script. I'll also check the log file. I believe the version is 2.6.
Sent by FoxWeb Support on 11/18/2008 12:08:40 PM:
FoxWeb uses tcp sockets for its internal communication. The error message you received indicates that the FoxWeb had trouble creating such a socket. There are many reasons why this could be happening. In general, if you only see this error once, there's no reason to worry about it, but if you see it repeatedly -- especially if a reboot doesn't fix it -- it is cause for concern.
Sent by Gabriel Badea on 11/18/2008 11:46:19 AM:
Hi I got the following error message: