Microsoft FrontPage
This page is meant to collect problems I've encountered and solutions I've
come across.
Problem: "The server sent a response which frontpage could not parse"
Solution:This is one of those "generic" Microsoft error messages
that tell you absolutely nothing, but refer you to an administrator. (the
administrator will get nothing from this error message either. 1. In my experience, the problem was caused by NTLM / Kerberos authentication
into our corporate DMZ. When I turned off "Integrated Windows Authentication",
and turned on "Basic Authentication" the problem went away. While I'm vague
on specifics, Kerberos (the default authentication protocol for Windows 2000
forward) is easily thwarted by firewalls and proxy servers.
While researching the problem, I encountered red herrings -- suggestions that
weren't my problem -- but I'll include them here, in case my issue isn't the
same as yours.
2. HTTP Keep-Alives. One web site claimed that HTTP Keep-Alives need to be
on in order for FrontPage to publish. If you're having the error message described,
this may be your issue.
3. Per the Microsoft Web Site, turn off you may have virus software that acts
as a proxy. Turn off the proxy features if possible.
|