"Sharepoint Services" error after upgrade to FP2003

[Ivor Jones]

I hope someone here can assist. For a couple of years I've been using
FrontPage 2000 to create and administer my small home site, which until
now has been ok. The host server is running the FP extensions and
everything was working fine until recently when I started getting errors
when trying to publish, saying something along the lines of "The server
sent a response which FrontPage could not parse" and to check with the
host that the FP extensions were installed correctly. I checked with them
and they said there was no problem at their end. The machine on which the
site was maintained was a rather elderly 200 MHz machine and was having
more than a few problems with other things as well, so I decided to
install FP2003 on my main PC which is a 3.06GHz P4 machine and run the
site from there.

After installation, I published the site back from the host server to the
PC, but on trying to publish changed pages back, I am still getting a
similar error, as follows:

"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".

The difference is that on this machine with FP2003 the pages I am trying
to publish do seem to be published ok, but the error message persists.

Any ideas..?

Ivor

 

[Robb Topolski]

After installation, I published the site back from the host server to the
PC, but on trying to publish changed pages back, I am still getting a
similar error, as follows:

"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".

I was receiving this error when there was a problem with my .htaccess files
on the webserver.

I would check your directories and see if you can rename these files as a
troubleshooting step. You can't use FrontPage to do that -- but you might
be able to use your provider's utilities if you don't have shell access to
the account.

Robb Topolski

 

[Wes]

You need to publish your entire site after upgrading.

 

[Ronx]

This error sometimes occurs when the site is too big or complex for the
server. While there are no inbuilt size limitations, some servers time out
or produce errors when the site grows, the actual size depends on the server
system, how busy the server is (how many websites are hosted on the box),
your use of FrontPage components (include pages, shared borders, forms etc.)
and (IMO) the weather in Outer Mongolia. There are no rules that determine
the size limits, in either number of files, or megabytes.

If you can, split the site into subwebs, and publish each subweb
independently.

 

[Ivor Jones]

This error sometimes occurs when the site is too big or complex for the
server. While there are no inbuilt size limitations, some servers time
out or produce errors when the site grows, the actual size depends on
the server system, how busy the server is (how many websites are hosted
on the box), your use of FrontPage components (include pages, shared
borders, forms etc.) and (IMO) the weather in Outer Mongolia. There are
no rules that determine the size limits, in either number of files, or
megabytes.

If you can, split the site into subwebs, and publish each subweb
independently.

It very much doubt it's the site size..! It's only my home page site, the
whole thing is probably only around 20 to 25 MB..! Only two pages include
themes, plus one is a mail form and another the FP guestbook, the rest are
basic HTML.

Think it's time for a phone call to the hosts tech support on Monday.

Ivor

 

[Ronx]

It could still be the site size. I had this problem 4 years ago - the site
weighed in at 1.5Mbytes (50 pages plus images) - just too much to fit on a
floppy disc, no themes, no shared borders, one form. A temporary cure was
to publish at 6AM GMT on Sunday morning when traffic on the server was
quiet. The host upgraded the server and problem went away.

Also, the other websites hosted on the same processor as yours will have an
effect.

 

[Ivor Jones]

It very much doubt it's the site size..! It's only my home page site,
the whole thing is probably only around 20 to 25 MB..! Only two pages
include themes, plus one is a mail form and another the FP guestbook,
the rest are basic HTML.

Think it's time for a phone call to the hosts tech support on Monday.

Ivor

An update on this, I called the hosts and they said that the FP extensions
are ok and to try reinstalling FP2003 and answering no to any question re.
setting up SharePoint services. I don't know what this means but in the
Remote Website Properties tab there's an option to select the type of
remote server and the only one that seems to apply is the one that says
"FrontPage or SharePoint Services - The Remote Web Server supports
FrontPage Server Extensions or SharePoint Services" - there's no option to
select FP extensions without reference to SharePoint.

What am I doing wrong..? The site seems to publish ok but sometimes I have
to have a couple of tries to get all the changed files across and the log
file always reports the SharePoint Services error.

If the host doesn't know, I'm sure I don't..!

Ivor

 

[Thomas A. Rowe]

You are doing nothing wrong regarding the dialog. The dialog means that FP2003 will support either
and any error mean either as well.

--
==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
WEBMASTER Resources(tm)

FrontPage Resources, WebCircle, MS KB Quick Links, etc.
==============================================

 

[Ivor Jones]

You are doing nothing wrong regarding the dialog. The dialog means that
FP2003 will support either and any error mean either as well.

Thanks Thomas, but have you any idea why I'm getting the error..? The host
insists the FP extensions are installed. Is there anything to configure in
FP2003 that will correct the problem..?

Ivor

 

[Thomas A. Rowe]

Try opening the site in IE, then select File Menu | Edit with FP and see if you open the site that
way.

--
==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
WEBMASTER Resources(tm)

FrontPage Resources, WebCircle, MS KB Quick Links, etc.
==============================================

 

[Ivor Jones]

Try opening the site in IE, then select File Menu | Edit with FP and see
if you open the site that way.

Yes I can do that, but I am getting the error when I try and publish a
locally edited copy of the site to the host server. I don't see how
opening the remote web directly makes a difference..?

Ivor

 

[Wes]

Thomas wants to see if you can edit live on the site so he can suggest other
options.

 

[Ivor Jones]

Thomas wants to see if you can edit live on the site so he can suggest
other options.

Ah, I see. Yes I can, no problems.

Ivor

 

[Thomas A. Rowe]

Ok, with the site open either directly or via IE's Edit with FP, open you local copy and try
publishing.

What is/was the error message when publishing?
--
==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
WEBMASTER Resources(tm)

FrontPage Resources, WebCircle, MS KB Quick Links, etc.
==============================================

 

[Ivor Jones]

The process seems to go ok, but at completion I get the 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." The file(s) that have been uploaded appear to be on the remote
server ok and can be accessed from the web, but they also show as being in
conflict on the split window page in FP (ie. local site on left, remote on
right). The publish status is shown as cancelled and the log file records
the above error.

Ivor

 

[Stefan B Rusynko]

At what type / size of file did it fail (from logs)
- open you online site in FP and run a Tools Recalculate Hyperlinks
- then in the remote site select the option to publish (changes only) from remote (your other location) to local (the online site
that is open)




|
| The process seems to go ok, but at completion I get the 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." The file(s) that have been uploaded appear to be on the remote
| server ok and can be accessed from the web, but they also show as being in
| conflict on the split window page in FP (ie. local site on left, remote on
| right). The publish status is shown as cancelled and the log file records
| the above error.
|
| Ivor
|
|
| | > Ok, with the site open either directly or via IE's Edit with FP, open
| > you local copy and try publishing.
| >
| > What is/was the error message when publishing?
| > --
| > ==============================================
| > Thomas A. Rowe (Microsoft MVP - FrontPage)
| > WEBMASTER Resources(tm)
| >
| > FrontPage Resources, WebCircle, MS KB Quick Links, etc.
| > ==============================================
| > To assist you in getting the best answers for FrontPage support see:
| > http://www.net-sites.com/sitebuilder/newsgroups.asp
|
|