New Problem with Form Results after Security Update

[Doug Barlow]

I've got a new problem with retrieving the results from Forms. I swear this
worked two months ago; now it fails on two separate systems. What I want to
do is have the results from a form placed into a comma separated text file,
then I periodically move new entries in that file off into another database.
I did this before by just moving the CSV file off of the web site to
wherever else I wanted it (doesn't matter how; FTP, etc.). The FrontPage
Server Extensions would simply create a new CSV file the next time someone
entered data.

Now suddenly, if the CSV file gets moved, the form page can't submit new
entries! When I click the 'Submit' button, I get a page that says:

FrontPage Error.
User: please report details to this site's webmaster.
Webmaster: please see the server's application event log for more
details.

And there's nothing at all in the server's application event log anywhere
near the time in question. (All Event Logs cleared prior to the problem are
still empty following the problem.)

Replacing the CSV file does not fix the problem. This behavior reproduces
even with a form consisting of only a 'Submit' button.

Both servers are running FrontPage Server Extensions 2002 in IIS. One is
Windows XP Professional and the other is Windows 2000 Server. Both have the
February 10th security update, which I find highly suspicious, since I
didn't have this problem two months ago.

 

[Thomas A. Rowe]

Try this, rename the file to have a .txt extension, instead of .csv.

--

==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
WEBMASTER Resources(tm)

FrontPage Resources, WebCircle,
MS KB Quick Links, etc.
==============================================

 

[Doug Barlow]

It still breaks if it is set to be a tab separated text file ending with
".txt".

Doug Barlow
The Soft Pedal Shop
http://www.softpedal.net
--

 

[Thomas A. Rowe]

Have you re-checked all permissions on the server, after the update?

If yes, then consider storing the data in an Access database.

--

==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
WEBMASTER Resources(tm)

FrontPage Resources, WebCircle,
MS KB Quick Links, etc.
==============================================

 

[Doug Barlow]

I've found a work around. Instead of moving the file away, I copy it off
and then truncate it to be empty. This seems to keep the FrontPage Server
Extensions from crashing the next time the form is used.

It's not perfect, since now there's a finite period of time where form
entries can get lost; but it's pretty small and should be OK for this
application.

Longer term, hopefully Microsoft will address the bug.

Doug Barlow
The Soft Pedal Shop
http://www.softpedal.net