The server sent a response which FrontPage could not parse.......

[William LaMartin]

After years of no problems, today when trying to publish from my local
computer to one of my FrontPage web sites I received the following FrontPage
error message and can go no further.

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.

I receive this same message if I try to open the remote site in FrontPage.
However, in this case a second try to open usually works. Then when I
double-click on folders I sometimes get the above message. Again, a second
try usually allows me to open the folder. Trying to recalculate the
hyperlinks at the site produces the error and cannot be done no matter how
many times you try.

I checked at other sites I am hosting at the same web hosting company, and
this problem does not exist for them.

The hosting company has reinstalled the FrontPage extensions, etc. We have
deleted all the content at the site except the required FrontPage folders
(the current tech I am dealing with says he cannot delete these folders--I
know if I had my hands on the server I could delete the whole website and
create a new one in a second--and I think this would solve the problem
unless there is something peculiar about this server.)

Anyone seen this problem and a solution?

 

[Nicholas Savalas - http://savalas.tv]

Dear William,
Error handling, error handling, error handling. Why do you think most
Internet application developers have gray hair? We sit all day in front
of some stupid text editor, usually notepad, trying to find one colon
that should've been a semi-colon, or some similar miniscule mistake.
Would you be so kind as to include the source code of the page in
question? I bet the problem could be fixed with something as simple as
setting the response buffer to true, or destroying the variables at the
end of the code. I am waiting breathlessly for your response. Good
luck.

 

[p c]

Check this out:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;q304407

If thats isn't, google for the error description fro other possibilities.

 

[William LaMartin]

It is not a firewall problem as the article suggests, since I have tried it
from a dial-up connection from a computer running no firewall and not on a
network.

I have Googled the problem to death with no solution and am waiting to see
in the hosting company will simply delete the web and recreate it.

 

[William LaMartin]

There is no code to worry about since there is only one page at the site
now--index.htm--which says that the site is temporarily down. I removed
every thing else with the hope that deleting all the content, reinstalling
the FP extensions and republishing would solve everything.

Note--you can not even recalculate the hyperlinks.

Now my hope is to get the hosting company to delete the site completely and
recreate it.

 

[p c]

I got that same of problem occasionally, too, last year off and on. I
wasn't sure exactly what was the cause. It was an intranet site hosted
on a WinNT4 server

I did some troubleshooting and narrowed my suspicions to the following:

1. Network configuration issues. During that time the company had
upgraded the network and the servers from Win Nt4 and Win 2000 to
Windows 2003 based. My server remained as NT4.

2. FP or FPSE issues. I had replaced my win 98 old desktop with a new PC
running Windows and had to install FP 2000 to the new PC.

I have no control over the network issues and the servers. The IT person
was no help.

The problem went away after I replaced the NT server with a Win 2003 server.

...PC

 

[William LaMartin]

The problem was solved by a new technician coming on duty at the webhosting
company. When he reset the FP extensions the problem went away. Two
previous attempts by another technician did not solve the problem.