Deleting the _fwsession.dbf, .fpt and .cdx files is a reasonable remedy. The table _fwsession contains session variable data stored during previous requests. Records holding expired sessions get re-used, but as whenever session variables get changed during a request, they update a memo field, causing the associated .fxp to grow in size. Space in memo files can only be reclaimed by packing, which FoxWeb attempts to do upon startup. Of course if the FoxWeb service does not get restarted very often and if you are running a busy site with lots of session variable updates, the .fxp file can get really big. You can try to pack the file while FoxWeb is running, but this can prove difficult if channels are constantly keeping the file locked.
Another problem is that when VFP processes hang, or crash, they can cause corruption to open tables. The _fwsession table is open during request execution and it is possible for this table to get corrupted if the channel crashes.
Sent by James Williams on 10/05/2006 11:42:43 AM:
I have had the session table become corrupt a few times. it seems to do this when it gets too large. I just delete the table, foxweb will recreate it on the next request.
Sent by on 10/05/2006 11:15:00 AM:
Can I delete the old session records in _fwsession.dbf? This table is up to 500 Mb.
I started getting errors in the error log saying that _fwsession.dbf could not be accessed.
"File access is denied d:\tmp\_fwsession.dbf."
It's sporadic in nature, but will happen for a short period of time (I'll get 10 to 20 error messages over a span of 3 or 4 mintues, depending on site traffic at the time).