"FP could not parse" Old problem - New Question

D

DSG

Windows XP Pro 2002, IE7
FrontPage 2000 ver: 4.0.2.6625 Standalone package and adopted by Office 2000
when installed.
Error:
"The server sent a response which FrontPage could not parse."
"If you are trying to connect to a FrontPage server, check with the server's
administrator to make sure the FrontPage server extensions are installed
properly"
The only times I get this message (many, in the last couple of years) is at
the end of publishing to my ISP's Server (have never used FTP, only
'publish' ). It is always a 'good publish" - all files are uploaded
properly. and when I get tired of watching the timer spin, I exit out of the
publish procedure and all is well.

I have made many calls to the server's technicians and they tell me to go
(on my machine) to the panel where I can reset the server extensions. Or
sometimes they told me they would reinstall their server extensions for my
connection. Of course those procedures never did help.

About the time the 'could not parse' messages began to appear, the ISP may
have changed to 2003 server extensions, but not sure.

Now, I have an idea. When I started my web account with my ISP (broadband,
standard, first five MB free and over the years I have added more MB) I
specifically asked for "enable FrontPage" when I opened the account and they
told me their extensions were ver 2000. That was in 2001. I have read in
their "notice" files they later changed over to version 2003. I think many
events happen through the years that change things for the customer. For
instance, the company is larger now, and makes money on commercial accounts.
The last time (last year) I called about this error and finally made a fuss,
they said I was "just a residential customer" and they "don't have server
extensions for residential customers - only for commercial customers". That
was when I realized they have been telling me for a couple or three years to
use the control panel in my browser to re-enable FrontPage extensions
without anything happening, and I'm still dealing with the "could not parse"
thing.

Be that as it may, and with all the changes I'm reading lately about servers
dropping FrontPage extensions across the board, and because I'm not using
any Dynamic HTML components, forms, databases (just photos and text)

Will unchecking anything here get rid of the "could not parse" problem?
On Tools > Page Options, I have these technologies and they are all checked:
- Enabled with Microsoft FrontPage Server Extensions
- ActiveX Controls
- VBScript
- JavaScript
- Java Applets
- Dynamic HTML (don't use)
- Frames (don't use)
- CSS 1.0
- CSS 2.0
- Active Server pages (don't have/use them)
.............
Dar
 
R

Ronx

I have read in their "notice" files they later changed over to version
2003.
There are no such thing as 2003 extensions. The latest are FP2002
extensions.

The error message "The server sent a response which FrontPage could not
parse." is often (though not always) produced by a server that is
overloaded. The server simply cannot cope with updating your website,
as well as serving the may other websites that are loaded on it.

If your site is very large, consider breaking it up into subwebs - each
(smaller) subweb can be published as a separate website, avoiding the
error. It does, however, mean that your navigation (if using the
FrontPage components) will need attention. Also shared borders and
include pages will not work across subwebs.
Subwebs are ideal for large numbers of media files (images, photo's,
sound and video files).

None of the settings you mentioned will make any difference. The
problem is probably on the server.
--
Ron Symonds - Microsoft MVP (FrontPage)
Reply only to group - emails will be deleted unread.
FrontPage Support: http://www.frontpagemvps.com/
http://www.rxs-enterprises.org/fp
 
D

DSG

Thanks, Ronx,
Three years ago, though not really understanding the phrase, 'FP could not
parse', and the responses I was getting from the ISP, it seemed to me that
its customers were getting fluffed off somehow.

Your answer makes sense, because this ISP cut off new personal home pages
for new customers two or three years ago. Very recently they have bought
another national Internet Service Provider with all those customers
transferred over. I see by their current member services pages, they are
now advertising with new copy how to sign up for and maintain personal home
pages. However, on my account page where I can modify my account the last
line says: "there are currently no additional home pages" just like it said
three years ago.

My site is not large at all. I have 5 MB free and pay for an additional 15
MB. I think they must be thinking that since there are so many other hosting
companies available for the 'masses' that there is no profit in offering
free homepages, although I thought that was the deal the FCC made with ISPs.

So I guess it's time to move on to other places. With the changes in
discontinuing FrontPage, for instance, many of us will be changing software,
and maybe the way we build our pages and will welcome new host sites.
DSG

....................
:> I have read in their "notice" files they later changed over to version
: 2003.
: There are no such thing as 2003 extensions. The latest are FP2002
: extensions.
:
: The error message "The server sent a response which FrontPage could not
: parse." is often (though not always) produced by a server that is
: overloaded. The server simply cannot cope with updating your website,
: as well as serving the may other websites that are loaded on it.
:
: If your site is very large, consider breaking it up into subwebs - each
: (smaller) subweb can be published as a separate website, avoiding the
: error. It does, however, mean that your navigation (if using the
: FrontPage components) will need attention. Also shared borders and
: include pages will not work across subwebs.
: Subwebs are ideal for large numbers of media files (images, photo's,
: sound and video files).
:
: None of the settings you mentioned will make any difference. The
: problem is probably on the server.
: --
: Ron Symonds - Microsoft MVP (FrontPage)
: Reply only to group - emails will be deleted unread.
: FrontPage Support: http://www.frontpagemvps.com/
: http://www.rxs-enterprises.org/fp
:
:
:
: :
: > Windows XP Pro 2002, IE7
: > FrontPage 2000 ver: 4.0.2.6625 Standalone package and adopted by Office
2000
: > when installed.
: > Error:
: > "The server sent a response which FrontPage could not parse."
: > "If you are trying to connect to a FrontPage server, check with the
server's
: > administrator to make sure the FrontPage server extensions are installed
: > properly"
: > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
: >
: > The only times I get this message (many, in the last couple of years) is
at
: > the end of publishing to my ISP's Server (have never used FTP, only
: > 'publish' ). It is always a 'good publish" - all files are uploaded
: > properly. and when I get tired of watching the timer spin, I exit out of
the
: > publish procedure and all is well.
: >
: > I have made many calls to the server's technicians and they tell me to
go
: > (on my machine) to the panel where I can reset the server extensions.
Or
: > sometimes they told me they would reinstall their server extensions for
my
: > connection. Of course those procedures never did help.
: >
: > About the time the 'could not parse' messages began to appear, the ISP
may
: > have changed to 2003 server extensions, but not sure.
: >
: > Now, I have an idea. When I started my web account with my ISP
(broadband,
: > standard, first five MB free and over the years I have added more MB) I
: > specifically asked for "enable FrontPage" when I opened the account and
they
: > told me their extensions were ver 2000. That was in 2001. I have read in
: > their "notice" files they later changed over to version 2003. I think
many
: > events happen through the years that change things for the customer. For
: > instance, the company is larger now, and makes money on commercial
accounts.
: > The last time (last year) I called about this error and finally made a
fuss,
: > they said I was "just a residential customer" and they "don't have
server
: > extensions for residential customers - only for commercial customers".
That
: > was when I realized they have been telling me for a couple or three
years to
: > use the control panel in my browser to re-enable FrontPage extensions
: > without anything happening, and I'm still dealing with the "could not
parse"
: > thing.
: >
: > Be that as it may, and with all the changes I'm reading lately about
servers
: > dropping FrontPage extensions across the board, and because I'm not
using
: > any Dynamic HTML components, forms, databases (just photos and text)
: >
: > Will unchecking anything here get rid of the "could not parse" problem?
: > On Tools > Page Options, I have these technologies and they are all
checked:
: > - Enabled with Microsoft FrontPage Server Extensions
: > - ActiveX Controls
: > - VBScript
: > - JavaScript
: > - Java Applets
: > - Dynamic HTML (don't use)
: > - Frames (don't use)
: > - CSS 1.0
: > - CSS 2.0
: > - Active Server pages (don't have/use them)
: > ............
: > Dar
:
 
D

DSG

I'm thinking when I progress to Expression-web or similar, I might want to
be using DHTML and other "extra" stuff, and so would need a server upgrade
anyway. Have finally found the pages on the server that show their server
upgrades. Thanks for the replies. We're all learning, aren't we?
DSG

:A few years ago I had the same problem with a 1MB site, and 50MB of
: space. A server upgrade solved the problem.
:
: There are reliable, low cost hosts such as http://www.webhost4life.com
: that may be more suitable for you.
: --
: Ron Symonds - Microsoft MVP (FrontPage)
: Reply only to group - emails will be deleted unread.
: FrontPage Support: http://www.frontpagemvps.com/
: http://www.rxs-enterprises.org/fp
:
:
:
: :
: > Thanks, Ronx,
: > Three years ago, though not really understanding the phrase, 'FP could
not
: > parse', and the responses I was getting from the ISP, it seemed to me
that
: > its customers were getting fluffed off somehow.
: >
: > Your answer makes sense, because this ISP cut off new personal home
pages
: > for new customers two or three years ago. Very recently they have
bought
: > another national Internet Service Provider with all those customers
: > transferred over. I see by their current member services pages, they
are
: > now advertising with new copy how to sign up for and maintain personal
home
: > pages. However, on my account page where I can modify my account the
last
: > line says: "there are currently no additional home pages" just like it
said
: > three years ago.
: >
: > My site is not large at all. I have 5 MB free and pay for an additional
15
: > MB. I think they must be thinking that since there are so many other
hosting
: > companies available for the 'masses' that there is no profit in offering
: > free homepages, although I thought that was the deal the FCC made with
ISPs.
: >
: > So I guess it's time to move on to other places. With the changes in
: > discontinuing FrontPage, for instance, many of us will be changing
software,
: > and maybe the way we build our pages and will welcome new host sites.
: > DSG
: >
: > ...................
: > : > :> I have read in their "notice" files they later changed over to
version
: > : 2003.
: > : There are no such thing as 2003 extensions. The latest are FP2002
: > : extensions.
: > :
: > : The error message "The server sent a response which FrontPage could
not
: > : parse." is often (though not always) produced by a server that is
: > : overloaded. The server simply cannot cope with updating your website,
: > : as well as serving the may other websites that are loaded on it.
: > :
: > : If your site is very large, consider breaking it up into subwebs -
each
: > : (smaller) subweb can be published as a separate website, avoiding the
: > : error. It does, however, mean that your navigation (if using the
: > : FrontPage components) will need attention. Also shared borders and
: > : include pages will not work across subwebs.
: > : Subwebs are ideal for large numbers of media files (images, photo's,
: > : sound and video files).
: > :
: > : None of the settings you mentioned will make any difference. The
: > : problem is probably on the server.
: > : --
: > : Ron Symonds - Microsoft MVP (FrontPage)
: > : Reply only to group - emails will be deleted unread.
: > : FrontPage Support: http://www.frontpagemvps.com/
: > : http://www.rxs-enterprises.org/fp
: > :
: > :
: > :
: > : : > :
: > : > Windows XP Pro 2002, IE7
: > : > FrontPage 2000 ver: 4.0.2.6625 Standalone package and adopted by
Office
: > 2000
: > : > when installed.
: > : > Error:
: > : > "The server sent a response which FrontPage could not parse."
: > : > "If you are trying to connect to a FrontPage server, check with the
: > server's
: > : > administrator to make sure the FrontPage server extensions are
installed
: > : > properly"
: > : > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
: > : >
: > : > The only times I get this message (many, in the last couple of
years) is
: > at
: > : > the end of publishing to my ISP's Server (have never used FTP, only
: > : > 'publish' ). It is always a 'good publish" - all files are uploaded
: > : > properly. and when I get tired of watching the timer spin, I exit
out of
: > the
: > : > publish procedure and all is well.
: > : >
: > : > I have made many calls to the server's technicians and they tell me
to
: > go
: > : > (on my machine) to the panel where I can reset the server
extensions.
: > Or
: > : > sometimes they told me they would reinstall their server extensions
for
: > my
: > : > connection. Of course those procedures never did help.
: > : >
: > : > About the time the 'could not parse' messages began to appear, the
ISP
: > may
: > : > have changed to 2003 server extensions, but not sure.
: > : >
: > : > Now, I have an idea. When I started my web account with my ISP
: > (broadband,
: > : > standard, first five MB free and over the years I have added more
MB) I
: > : > specifically asked for "enable FrontPage" when I opened the account
and
: > they
: > : > told me their extensions were ver 2000. That was in 2001. I have
read in
: > : > their "notice" files they later changed over to version 2003. I
think
: > many
: > : > events happen through the years that change things for the customer.
For
: > : > instance, the company is larger now, and makes money on commercial
: > accounts.
: > : > The last time (last year) I called about this error and finally made
a
: > fuss,
: > : > they said I was "just a residential customer" and they "don't have
: > server
: > : > extensions for residential customers - only for commercial
customers".
: > That
: > : > was when I realized they have been telling me for a couple or three
: > years to
: > : > use the control panel in my browser to re-enable FrontPage
extensions
: > : > without anything happening, and I'm still dealing with the "could
not
: > parse"
: > : > thing.
: > : >
: > : > Be that as it may, and with all the changes I'm reading lately about
: > servers
: > : > dropping FrontPage extensions across the board, and because I'm not
: > using
: > : > any Dynamic HTML components, forms, databases (just photos and text)
: > : >
: > : > Will unchecking anything here get rid of the "could not parse"
problem?
: > : > On Tools > Page Options, I have these technologies and they are all
: > checked:
: > : > - Enabled with Microsoft FrontPage Server Extensions
: > : > - ActiveX Controls
: > : > - VBScript
: > : > - JavaScript
: > : > - Java Applets
: > : > - Dynamic HTML (don't use)
: > : > - Frames (don't use)
: > : > - CSS 1.0
: > : > - CSS 2.0
: > : > - Active Server pages (don't have/use them)
: > : > ............
: > : > Dar
: > :
:
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Hosting Options 13
Parsing Error, with Front Page .... 11
Frontpage 2000 problem - any ideas 4
upload form problem / server question 1
Non-FP Substitute for FORMS 2
Unable to open remote website to publish 2
Front Page Run-Time Error 2
FrontPage Run-Time Component Page 2

Top