Just to let you know I fixed the problem. There was nothing in fwstart.log of interest but I did track down a message to do with the TEMP directory in the Windows Event Log. With the TEMP path corrected, Foxweb now starts automatically on reboot as desired.
Thanks for your help and pointers.
Sent by FoxWeb Support on 03/12/2007 12:14:21 PM:
What kind of trouble are you having getting FoxWeb to start after a reboot? Are you getting any error messages in the Windows Event Log, or in fwstart.log? Did you enable the Run As Service checkbox in the FoxWeb Control Center? You should also make sure that the Startup Type setting for the FoxWeb service is set to "Enabled". This is done in the Control Panel/Administrative Tools/Services.
The 1500 error is probably not related to FoxWeb, but is preventing the FoxWeb setup program from running. It's telling you that an installation for another product never completed. Have you tried rebooting?
Sent by John Waite on 03/10/2007 02:34:15 AM:
Foxweb 3 seems to be running fine, but I am having trouble getting it to run on start up / reboot and believe I need to reinstall.
On trying to reinstall or even remove Foxweb 3, I get the following error message:
Error 1500. Another installation is in progress. You must complete that installation before continuing this one.
All the best,