View Complete Thread | FoxWeb Forum Home
Search:
Date:    Msg ID:   
From:    Thread:   
Subject:   
Your fw_start.log contains a large number of entries like the following:
 
08/04/2004 11:23:53 Error: 1812 Message: "SQL: Statement too long." Program: "WWW_READ.FXP" Line Number: 75 Line: "CLOSE ..." Channel: 1
08/03/2004 11:23:54 Error: 1924 Message: "FRMSCK is not an object." Program: "WWW_READ.FXP" Line Number: 98 Channel: 2
 
The code in line 75 is simply "CLOSE DATABASES ALL".  I did not know that CLOSE DATABASES could return error 1812, but apparently it can.  The code that causes this error must be a SELECT statement in one of your scripts.
 
We will try to reproduce the problem, but if you can help us by identifying the offending code in your scripts, it would be very helpful.  Once we reproduce the problem, we may be able to modify FoxWeb so that it can recover from this situation.  Of course the fastest solution for your problem is to fix the code that creates the long SELECT statement in the first place.

FoxWeb Support Team
support@foxweb.com email

Sent by FoxWeb Support on 08/04/2004 07:56:06 PM:
If Restart Channels is enabled, then FoxWeb will attempt to restart channels that are marked as busy for longer than the Script Timeout setting + 5 seconds.  However, in some cases channel processes are locked in a way that prevents FoxWeb (or any other application for that matter) from killing them.  The primary example is when channels get locked by DrWatson, or the newer FoxPro Fatal Error Reporting (DW15.EXE and DWINTL.DLL).
 
I recommend that you:
  1. Send us a copy of fwstart.log via email.
  2. Disable the Run as Service and Hide Channels options, restart FoxWeb and look for the corresponding channel window when the problem happens.  Are there any visible queues, such dialog boxes?

FoxWeb Support Team
support@foxweb.com email

Sent by Joe Goldsmith on 08/03/2004 02:02:42 PM:
Hello. The problem I am having is that channels are not restarting locking up the webserver and the hosted email server. The problem occurs with a programming error but should channels not restart? My configuration may not be correct so here it is:
 
FOR two domains should I have more than two channels set?
 
CHECKED
=======
Close tables
Restart channels
Run as service
Buffer output
Session support
Keep Prgs
 
Script timeout = 40
Session timeout = 30
Total channels = 2
 
Virtual Server set as use web server's directory mapings
 
Ip-Addresses have no IP address in each of two boxes.
 
The logs do not show anything of usefulness that I can tell.
 
Can someone tell me what I can do better please?