The fact that channels drop from the channel status window does not mean that they are gone. The channels are probably still running, but FoxWeb is unable to restart them for some reason. We have seen this in the past due to the channel process being locked by DrWatson (or the Fatal Error Reporting system is it is called in later versions).
As you mentioned in your original posting, the channels still show up in the task manager. It would be really helpful, if you could follow our previous instructions and made the unresponsive channels visible, so that you can look for dialog windows, or other indications of what the problem is. You can identify which window corresponds to a channel, by matching the channels that disappear from the FoxWeb Status Window, with the titles of individual channel windows. Click on the appropriate channel icon in the task bar to bring its window in the foreground and examine it for any visible hints.
Sent by B Wagner on 11/17/2003 02:16:33 PM:
We seemed to have fixed the scripts hanging when we moved FW to a new server. Since it would go a week or more before hanging would occur, it's wait and see. The problem now is channels dropping. We're configured to use the runtimes (VFP6) and now running as apps instead of as a service. Problem is 6 apps are running (as is configured) but FoxWeb Channel Status occasionally drops one and it doesn't come back. If I quit the FW App for the missing channel it will come back in Channel Status. We're running FW2.5
Sent by FoxWeb Support on 11/13/2003 05:14:05 PM:
There seems to be something that causes your channels to occasionally hang. The reason why this would be happening is not clear, but there are several possibilities, such as the use of Illegal Commands as outlined in the FoxWeb documentation, rogue 3rd-party components, broken network connections between FoxWeb and database tables, or other network resources it tries to access.
One method you can use to identify the problem is to disable the "Run as Service" and "hide Channels" options in the FoxWeb configuration and then restart FoxWeb. You should now be able to see a separate icon for each channel in the task bar. Size and arrange the channel windows on your screen, so that they are all visible at the same time. Call the offending script(s) and then minimize your browser window, so that the channel windows are visible. Look for a dialog box, or other indication that a channel is waiting for user input. In most cases, the script tries to use a table that is not open, which causes the Open Table dialog to pop up, halting script execution. If you can't find a visual indication of the problem, then you may need to trace through your script, using the techniques described in the Troubleshooting chapter. Once you isolate and fix the problem, you can re-enable the above configuration options as necessary.
Sent by B Wagner on 11/13/2003 12:17:24 PM:
We move FW to a new server. We changed to using run-time DLLs. The FoxWeb Channel status shows fewer than the 8 channels configured dropping as low as 2. But task manager shows 8 instances of FWServer running. Force quiting them in task manager would restart the channels.
Win2K server SP4
two -2.4gz xenon
We moved from an older box to find if it would fix a timeout problem. This has been an intermitant problem. It occures as a storm with all channels timing out and cpu and network activity droping to 0 as if waiting for a resource to free up. The FW startlog show it happening to a random sampling of programs.