The tray icon only appears if you are not running FoxWeb as a service. I recommend that you do so while you are troubleshooting this problem. This will allow you to see your channel windows and detect any pop up dialog boxes that may appear.
Sent by Joe Bigelow on 04/29/2004 09:20:01 PM:
PS - Foxweb isn't in the tray, never has been. I used to worry about it, but then got busy with other things..., like a nap... ;-O
I'm also wondering if as I'm on 2003 if I should move up to FW2.6. Are there any differences other than VFP support for higher versions?
To whom would you like me to send the fw_start.log?
Sent by FoxWeb Support on 04/28/2004 09:17:55 PM:
This is very interesting. I have never seen a situation like this one before. Can you find anything interesting in fw_start.log? If you are not sure, please send us a copy. Also, what's the channel status at the time? You can check it by selecting the Channel Status option from the right-click menu on the FoxWeb icon in the tray area. Alternatively, you can call show_channels.fwx. In fact, try this one first to see if it responds.
Another thing to try is changing the fwx script mapping configuration in the Internet Service Manager so that it points to foxweb.exe (instead of foxweb.dll) just to see if it makes a difference.
Sent by Joe Bigelow on 04/28/2004 04:18:57 PM:
So, no sooner did I log off this forum and checked the server than it had happened again...
I opened Foxweb Control Center, stopped service, restarted and it worked again... HELP!!!!!!!!!!!!! :-)
I going to check permissions again I think, doing something is better than doing nothing...
Sent by FoxWeb Support on 04/27/2004 12:38:29 PM:
Your configuration seems to be correct. The fact that FoxWeb works for a few hours or days and then stops seems really strange. What happens when it stops working? Do you get an error message? What's the exact text of the message and where does it appear (browser, fwstart.log, IIS server log, FoxWeb Error Log)?
An interesting test would be for you to simply restart FoxWeb after it stops working (without touching anything else) to see if this fixes the problem.
Sent by Joe Bigelow on 04/27/2004 11:55:55 AM:
I've installed new servers and had Windows Servier 2003 Web edition put on them. What a pain in the short run...
I want to make sure if there is a "correct" installation of FoxWeb, other than what I've cobbled together. It works, more or less.
Created a new Web Service Extension (who knew...) and have put both the foxweb.dll and foxweb.exe in "inetpub/AdminScripts" as required files.
I then discovered that inetpub/AdminScripts didn't have the Internet Guest Account automatically installed in security, so I installed it. I then put that user into the security set up for my program root as well.
Because I want to use script mapping, so I opened the properties for the web site in IIS and added ".fwx" to use inetpub/AdminScripts/foxweb.dll with GET,HEAD,POST.
I think this is all correct, hopefully that is. Now here's the question/problem. It works, then stops working after a few hours to couple of days. I go back, check all the settings and configurations, no changes, open FoxWeb Control Center, stop it, restart it and it works again. This has happened three times now. Something seems not to "stick" as it were.
I decided to go with 2003 specifically because of security issues I've had in the past. A server was totally trashed by someone coming in through an undocument feature back door in 2000, (god bless BG...), and using the server to hyper-transfer hundreds of thousands of copies of pirated films, (why me?). I can only think that I have not gotten a permission correct or something else not "just right" and it's making be batty.
Do you see any problems with what I did or have suggestions on things I haven't done or not done correctly? Your advice is MUCH appreciated!