We don't really have enough information about the problem yet.
There does seem to be a problem with one, or more of your scripts (see the Hanging Channels, or Channels that Get Restarted Often section in the Troubleshooting page of the FoxWeb documentation), but I'm not sure if this is causing the problem. Another possibility is that certain requests occupy channels for long periods of time (or indefinitely). If this happens to all your channels, then FoxWeb will return the above error. You can experiment with running more channels, or changing your Script Timeout setting, so that FoxWeb will kill these requests and restart channels sooner. Obviously the real solution would be to find out the offending scripts and optimize them so that they don't tie up FoxWeb channels.
Sent by Fernando Medan on 08/02/2004 07:13:37 AM:
I'm using Windows 2003 y FoxWeb 2.6.
Some times I must reset the service because foxweb does not work:
It happens to different scripts, but not always:
07/28/2004 10:55:17 Killed Channel 1: /busq@dbn
07/28/2004 10:55:18 Restarting Channel 1
07/28/2004 10:57:29 Killed Channel 1: /veralbum@dbn
07/28/2004 10:57:30 Restarting Channel 1
07/28/2004 10:58:35 Starting FoxWeb
07/28/2004 18:37:03 Killed Channel 2: /busq@dbn
07/28/2004 18:37:04 Restarting Channel 2
07/28/2004 18:37:34 Restarting Channel 2
07/29/2004 07:12:58 Closing FoxWeb
07/29/2004 07:12:59 Starting FoxWeb
Thanks for help