ERROR 500 't' command not understood

[Bms Jeff]

I am using Godaddy.com. Have Frontpage Extensions installed on their
Windows Server platform. I have confirmed this with the support staff.

When I try to publish to ftp://ftp.xxx.com I receive the Error 500 message
When I try to publish to ftp://www.xxx.com I get the following:

When I attempt to publish All, I receive the message
"The following pages in your web site contain dynamic Frontpage components,
such as a Search Form or a FrontPage form handler. They will not work
because the server you are publishing to does not have the Frontpage Server
Extensions or SharePoint Team Services from Microsoft installed."

After this message FrontPage tells me that it was Published Successfully.

When I try to use the form on the website, I get:
FrontPage Run-Time Component Page
You have submitted a form or followed a link to a page that requires a web
server and the FrontPage Server Extensions to function properly.

This form or other FrontPage component will work correctly if you publish
this web to a web server that has the FrontPage Server Extensions installed.

Click the <Back> arrow to return to the previous page.
What might I be doing wrong.

 

[Ronx]

Using FTP will corrupt the extensions. Re-install the extensions, then
publish using HTTP. The address to publish to will be similar to
http://www.example.com NOT, repeat NOT ftp://www.example .com

If you are on a Windows server be aware that that GoDaddy do not support
email destinations for form data when using the FrontPage extensions to
process the form.

 

[Bms Jeff]

Thank you, that was exactly the problem. I miss read a Godaddy help file
about using FTP.

FYI, email destinations are working for me.
Here is the code:
<FORM METHOD="POST" ACTION="--WEBBOT-SELF--"
onSubmit="location.href='_derived/nortbots.htm';return false;"
webbot-onSubmit>
<!--webbot bot="SaveResults" u-file="_private/feedback.txt" s-format
s-email-address="<user>@juno.com" s-email-format="TEXT/PRE"
startspan --><strong>[FrontPage Save Results Component]</strong><!--webbot
bot="SaveResults" endspan i-checksum="6561" --><P>

Thanks again for you help.

 

[Ronx]

Are you on a Windows server, or Unix? GoDaddy has told users that they
do not support email on Windows, except when using asp or other server
side scripts. Unix servers have (apparently) no similar restriction.
--
Ron Symonds - Microsoft MVP (FrontPage)
Reply only to group - emails will be deleted unread.

http://www.rxs-enterprises.org/fp

Thank you, that was exactly the problem. I miss read a Godaddy help file
about using FTP.

FYI, email destinations are working for me.
Here is the code:
<FORM METHOD="POST" ACTION="--WEBBOT-SELF--"
onSubmit="location.href='_derived/nortbots.htm';return false;"
webbot-onSubmit>
<!--webbot bot="SaveResults" u-file="_private/feedback.txt" s-format
s-email-address="<user>@juno.com" s-email-format="TEXT/PRE"
startspan --><strong>[FrontPage Save Results Component]</strong><!--webbot
bot="SaveResults" endspan i-checksum="6561" --><P>

Thanks again for you help.

Using FTP will corrupt the extensions. Re-install the extensions, then
publish using HTTP. The address to publish to will be similar to
http://www.example.com NOT, repeat NOT ftp://www.example .com

If you are on a Windows server be aware that that GoDaddy do not support
email destinations for form data when using the FrontPage extensions to
process the form.

--
Ron Symonds - Microsoft MVP (FrontPage)
Reply only to group - emails will be deleted unread.

http://www.rxs-enterprises.org/fp

 

[Bms Jeff]

I am using the Windows Server.

Are you on a Windows server, or Unix? GoDaddy has told users that they do
not support email on Windows, except when using asp or other server side
scripts. Unix servers have (apparently) no similar restriction.
--
Ron Symonds - Microsoft MVP (FrontPage)
Reply only to group - emails will be deleted unread.

http://www.rxs-enterprises.org/fp

Thank you, that was exactly the problem. I miss read a Godaddy help file
about using FTP.

FYI, email destinations are working for me.
Here is the code:
<FORM METHOD="POST" ACTION="--WEBBOT-SELF--"
onSubmit="location.href='_derived/nortbots.htm';return false;"
webbot-onSubmit>
<!--webbot bot="SaveResults" u-file="_private/feedback.txt" s-format
s-email-address="<user>@juno.com" s-email-format="TEXT/PRE"
startspan --><strong>[FrontPage Save Results
Component]</strong><!--webbot
bot="SaveResults" endspan i-checksum="6561" --><P>

Thanks again for you help.

Using FTP will corrupt the extensions. Re-install the extensions, then
publish using HTTP. The address to publish to will be similar to
http://www.example.com NOT, repeat NOT ftp://www.example .com

If you are on a Windows server be aware that that GoDaddy do not
support
email destinations for form data when using the FrontPage extensions to
process the form.

--
Ron Symonds - Microsoft MVP (FrontPage)
Reply only to group - emails will be deleted unread.

http://www.rxs-enterprises.org/fp





I am using Godaddy.com. Have Frontpage Extensions installed on their
Windows Server platform. I have confirmed this with the support
staff.

When I try to publish to ftp://ftp.xxx.com I receive the Error 500
message
When I try to publish to ftp://www.xxx.com I get the following:

When I attempt to publish All, I receive the message
"The following pages in your web site contain dynamic Frontpage
components,
such as a Search Form or a FrontPage form handler. They will not work
because the server you are publishing to does not have the Frontpage
Server
Extensions or SharePoint Team Services from Microsoft installed."

After this message FrontPage tells me that it was Published
Successfully.

When I try to use the form on the website, I get:
FrontPage Run-Time Component Page
You have submitted a form or followed a link to a page that requires a
web
server and the FrontPage Server Extensions to function properly.

This form or other FrontPage component will work correctly if you
publish
this web to a web server that has the FrontPage Server Extensions
installed.

Click the <Back> arrow to return to the previous page.
What might I be doing wrong.