J
Jackie
Hi all,
I'm trying to get the file upload component working, but have been having
problems.
I'm running Windows XP Pro, and have Server extensions running on my local
server. Forms, emails etc. all work.
I've set up a folder called Mireports, and have ticked the 'allow anonymous
upload' etc. check boxes within the folder properties (the only way I could
accomplish this was to right-click the published folder on a subsequent
Publish Web screen as they were greyed out when I tried anywhere else).
I've created a page called miupload.htm and inserted an upload form. I've
specified within form properties/file upload the destination folder
Mireports, but changed nothing else.
Within Inetpub I've given IUSR full permission on the Mireports folder, the
sub-web within which it's contained and - for good luck - the whole website!
I've gone into IIS and checked the server extensions, and had no problems
reported. I've recalculated the hyperlinks for the whole default website.
When I save the page miupload.htm and then preview in browser, I first of
all get a warning saying this page contains elements which may need to be
published to preview correctly. If I OK that, the C:\ page comes up in my
browser window and I can browse for the file I wish to upoad. When I submit,
I get a FrontPage Run-Time Component Page error.
When I publish the website to my local server, and run the
http://myservername page I get the error "Cannot run the FrontPage Server
Extensions' Smart HTML interpreter on this non-HTML page:" when I submit.
That looks as though the server extensions are not working, but if I go to a
page within the same website which uses forms (and sends an email) it works
OK.
When I publish this to my online host, which is running FrontPage 2002
server extensions and everything works OK with other forms etc, I get the
error Cannot run the FrontPage Server Extensions' Smart HTML interpreter on
this non-HTML page.
I've tried renaming the miupload.htm with an shtml extension as per an
archived recommendation, and that doesn't work either.
Does anyone have any idea what I could try next?
Thanks,
Jackie
I'm trying to get the file upload component working, but have been having
problems.
I'm running Windows XP Pro, and have Server extensions running on my local
server. Forms, emails etc. all work.
I've set up a folder called Mireports, and have ticked the 'allow anonymous
upload' etc. check boxes within the folder properties (the only way I could
accomplish this was to right-click the published folder on a subsequent
Publish Web screen as they were greyed out when I tried anywhere else).
I've created a page called miupload.htm and inserted an upload form. I've
specified within form properties/file upload the destination folder
Mireports, but changed nothing else.
Within Inetpub I've given IUSR full permission on the Mireports folder, the
sub-web within which it's contained and - for good luck - the whole website!
I've gone into IIS and checked the server extensions, and had no problems
reported. I've recalculated the hyperlinks for the whole default website.
When I save the page miupload.htm and then preview in browser, I first of
all get a warning saying this page contains elements which may need to be
published to preview correctly. If I OK that, the C:\ page comes up in my
browser window and I can browse for the file I wish to upoad. When I submit,
I get a FrontPage Run-Time Component Page error.
When I publish the website to my local server, and run the
http://myservername page I get the error "Cannot run the FrontPage Server
Extensions' Smart HTML interpreter on this non-HTML page:" when I submit.
That looks as though the server extensions are not working, but if I go to a
page within the same website which uses forms (and sends an email) it works
OK.
When I publish this to my online host, which is running FrontPage 2002
server extensions and everything works OK with other forms etc, I get the
error Cannot run the FrontPage Server Extensions' Smart HTML interpreter on
this non-HTML page.
I've tried renaming the miupload.htm with an shtml extension as per an
archived recommendation, and that doesn't work either.
Does anyone have any idea what I could try next?
Thanks,
Jackie