Parsing error during publishing on FP 2003

[synlupri]

Recently, every time I attempt to publish from my server to my local
drive (trying to create a new backup copy of the website), I get the
following error:

"The server sent a response which frontpage could not parse. If you
are trying to connect to a Windows SharePoint Services server, check
with the server's administrator to make sure Windows SharePoint
Services is installed properly."

This error happens on two different laptops, that connect to the same
Intranet server to update and publish files.

After searching for a week on this topic, all I could find were posts
from at least 3 years ago, with no final resolution.

We're running Win 03 (server), Winxp Pro (locally), FP 03 (locally),
Server extensions 02 web, IE 7 (server and locally), all updates,
plenty of RAM. We are not running SharePoint svcs.

Can anyone offer more suggestions?

So far this is what I've tried:

Running FP Cleaner and deleting all temp files.
Recalculated hyperlinks with FP.
Deleting all temps on the server.
Recalculated server extensions on the server itself.
Manually deleted a few files that may have had bad or long file names.

I have a call into MS Support now, but if I can save the $250 charge,
I'd really like to do so.

Please respond if you've encountered this and were able to resolve it.

Thanks for the help.

 

[Tom [Pepper] Willett]

Run a health check on the host server extensions and see what happens.
--
Tom [Pepper] Willett
Microsoft MVP - FrontPage
"You're a daisy if you do!"
---
FrontPage Support:
http://www.frontpagemvps.com/
===
: Recently, every time I attempt to publish from my server to my local
: drive (trying to create a new backup copy of the website), I get the
: following error:
:
: "The server sent a response which frontpage could not parse. If you
: are trying to connect to a Windows SharePoint Services server, check
: with the server's administrator to make sure Windows SharePoint
: Services is installed properly."
:
: This error happens on two different laptops, that connect to the same
: Intranet server to update and publish files.
:
: After searching for a week on this topic, all I could find were posts
: from at least 3 years ago, with no final resolution.
:
: We're running Win 03 (server), Winxp Pro (locally), FP 03 (locally),
: Server extensions 02 web, IE 7 (server and locally), all updates,
: plenty of RAM. We are not running SharePoint svcs.
:
: Can anyone offer more suggestions?
:
: So far this is what I've tried:
:
: Running FP Cleaner and deleting all temp files.
: Recalculated hyperlinks with FP.
: Deleting all temps on the server.
: Recalculated server extensions on the server itself.
: Manually deleted a few files that may have had bad or long file names.
:
: I have a call into MS Support now, but if I can save the $250 charge,
: I'd really like to do so.
:
: Please respond if you've encountered this and were able to resolve it.
:
: Thanks for the help.