Yes I am running as a service.
Foxweb is loaded under "All Users". My user is "Administrator" so should be okay.
Looked in fwstart.log all that shows is start / close etc.
Within the Services section the Foxweb item is set to "Local User".
There must be a setting somewhere that I cannot see.
I access the server using "Remote Desktop".
Sent by FoxWeb Support on 06/09/2004 05:39:48 AM:
Don't worry about the SmartMail.dll error. This DLL is not used by FoxWeb 2.6 and was included accidentally.
Regarding the Cannot Start FoxWeb error, are you running FoxWeb as a system service? If this is the case, check the user that is configured to run the FoxWeb service. Make sure that you have specified the correct password and that the user has sufficient rights. You may also want to look at the file fwstart.log. It may contain additional information about the problem.
Sent by Stephen Ames on 06/06/2004 03:09:28 PM:
Wow. I answered this one once. Took 15 minutes or so to get it all down and hit the send button - then it all disappeared.
Okay. Thank you. I managed to get it working properly again. I have a referrer dbf that had 500k records marked as "deleted" out of 600k. This file is accessed by every visitor. As soon as I packed the file the server returned to normal.
Anyway, due to the fact that we expect to increase our visitors over the coming months I decided to upgrade to a bigger faster Windows 2003 server.
A couple of problems came up when I installed Foxweb 2.6 after first installing Visfox 6.
First of all at the end of the installation I go the error message"One or nore files could not self register" and below that "c:\windows\system32\aspSmartMail.dll". "The specified module could not be found".
Also when I try and start Foxweb after rebooting I get the error "Cannot Start Foxweb - Check your user rights". I am set up as an administrator.
Sent by FoxWeb Support on 06/03/2004 04:23:47 PM:
Most probably there's code in one or more scripts that is causing channels to hang. The first thing you should do is look at the file fwstart.log. Are there any errors that would point you to the cause of the problem? If not, then follow the procedure below:
While you are troubleshooting this problem I recommend that you disable the Run as Service and Hide Channels options in the FoxWeb Control Center. You will need to restart FoxWeb for your changes to take effect. Once you restart you should be able to see the FoxWeb icon in the tray area of the task bar, as well as separate icons for each channel in the task bar.
You can open the channel status window by right-clicking on the tray icon and selecting Channel Status. You should also be able to click on the channel icons to view the VFP windows for each channel.
Once you experience the problem again, please check the status of the channels and inspect the various windows to see if there any hints that would help you identify the problem. Look for open dialog windows or anything else that would halt execution of a script.
Sent by Stephen Ames on 06/02/2004 08:05:15 AM:
My site has never been busier than today and even though I have stopped and restarted the Server and Foxweb we are still getting the "Foxweb Broker Timed Out" error. I have turned off our main referrer so that the traffic has reduced a lot but still no good.