This is not exactly the same problem as what Lew En Lai was experiencing, but the remedy may be the same: Try a different user for the service. FoxWeb 2 is a totally different product, so it has different requirements than FoxWeb 1. Many files are in different locations and it is possible that your old user does not have rights to these locations. Start with placing the current user in the Administrators group just to determine whether this fixes the problem. If it does, then undo your previous change and try to strike a balance between security and providing enough rights to run FoxWeb and your scripts.
Sent by FoxWeb Support on 03/30/2004 12:14:30 AM:
First of all you should check the Windows Event Log and the file fw_start.log for clues as to what is happening. You should also try specifying a different user for the FoxWeb service. This is done in the Log On pane of the properties window. Start with a local account with admin rights just to determine whether this fixes the problem and then try a different account with more appropriate rights.
Sent by Lew En Lai on 03/29/2004 08:20:50 AM:
Just recently downloaded the Foxweb 2.6 trial version and installed into a Windows 2003 server with IIS6.
After installing foxweb, I was unable to run the services in the services applet of the control panel.
When I click to start the service in returned an error pop-up message :
Could not start foxweb service on local computer.
Error 1053 - The service did not respond to the start or control request in a timely fashion.
From the previous postings in the forum, I read that I will need to add an application extension
in the Internet Services Manager. Is the above message related to the application extension in
the Internet Services manager as I have not added it yet? Please advise. Thank you