View Complete Thread | FoxWeb Forum Home
Search:
Date:    Msg ID:   
From:    Thread:   
Subject:   
Ok, just got back from a VERY long day slogging the web site to find it down again...
 
Stopped Foxweb, restarted Foxweb and miracle of miracles it worked again.
 
Then I looked at the error log in the control panel, finally something failed. Weirdest failure tho. It failed on a seek command with the error message "Record out of Range". So I packed and rebuilt the indexes on that table. Wondering if I should do it on all of them...
 
This made me think however of something. I keep my data out of the web path, way out of the web path, as well as my foxweb program root. So I logged onto my old server, happens to be still online but not serving anything and looked at the permissions on the data directory and foxweb program root. They had "Everyone" as the sole user.
 
Sooooooo......
 
I went back onto the new server and stuck "Everyone" in as users on both directories over there as well. Probably won't make any difference, but worth a try? It just seems that something awfully esoteric isn't set properly or something because of the behavior.
 
Will watch closely tomorrow to see if it fails again. If, or should I say when, it fails I'll do the checking you've just suggested and report back.
 
Thanks.
 
JB
 
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.

FoxWeb Support Team
support@foxweb.com email

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...
 
Joe Bigelow
 
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.

FoxWeb Support Team
support@foxweb.com email

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.
 
Then...
 
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!
 
Joe Bigelow
HV/Net