No erreur message.
I can change it without error. And after reboot:
In Control Panel\Administrative Tools\Services
In the "Startup Type" column it's "Automatic" but in the "Status" it's blank.
When I go to "FoxWeb Control Center " and press "Start FoxWeb" then it's start no problem.
When I do to verify the service status, in the status column, i see "Started".
in the fwstart.log the last entry are :
01/25/2009 11:16:09 FoxWeb has just been installed! Please configure.
01/25/2009 11:16:16 FoxWeb has just been installed! Please configure.
01/25/2009 11:16:45 Starting FoxWeb
01/26/2009 18:41:11 Starting FoxWeb
01/26/2009 18:41:23 Closing FoxWeb
01/26/2009 18:43:54 Starting FoxWeb
It's installed over a year now. Working just fine! I never get that problem solved.
Thanks for your help.
Sent by FoxWeb Support on 01/26/2009 02:32:08 PM:
Go to Control Panel\Administrative Tools\Services and locate the FoxWeb service.You mentioned that the startup type of this service is listed as "Manual" and that you couldn't get change it to "Automatic". What happens when you try to make this change in the service properties dialog? Do you get an error message? Can you change the startup type of any other services?
Sent by Martin Support on 01/26/2009 02:12:05 PM:
I'm in as Administrator
And YES, and foxweb box "Run as service" is checked!
What else I can look at to find the problem?
Sent by FoxWeb Support on 01/26/2009 01:35:18 PM:
The FoxWeb Control Center tries to modify the Services configuration, so you must be logged in with admin rights in order for your changes to be saved. Also, make sure that FoxWeb is configured to run as a service in the Configuration tab.
Sent by Martin Joncas on 01/26/2009 06:58:46 AM:
I try to get FoxWeb to restart automaticly as a service but, I can't get it.
Each times the server reboot, I have to manualy press the START button then foxweb tell me to save my changes? then it start.
FoxWeb in the "windows services" came back to manual. No way to get it start automatic.
I'm using last foxweb version with windows server 2003.
It's probably a right issue?