Inconsistant SharePoint FrontPage Operation - The Server Could Not Complete Your Request...

D

David McKenzie

Sometimes FrontPage 2003 works just fine editing Windows SharePoint Services
aspx pages,
but other times I get an error:

"The server could not process your request.
Contact your Internet service provider or web server administrator to make
sure that the server has FrontPage Server Extensions installed."

Being that WSS decided to place a @ Register for a component I no longer
want, need or use at the top of many pages, and the *only* supported way to
edit these pages is by using FP2003, the function *really* should work.....


Manby pages work, the problem seems to be mor frequent on pages with a fair
number of web parts.
 
T

Tom Pepper Willett

Try the Share Point Newsgroups:

news://msnews.microsoft.com/microsoft.public.sharepoint.windowsservices

news://msnews.microsoft.com/microsoft.public.sharepoint.teamservices
(Usability)

news://msnews.microsoft.com/microsoft.public.sharepoint.teamservices.caml
(Custom Development)
--
===
Tom "Pepper" Willett
Microsoft MVP - FrontPage
---
About FrontPage 2003:
http://office.microsoft.com/home/office.aspx?assetid=FX01085802
FrontPage 2003 Product Information:
http://www.microsoft.com/office/frontpage/prodinfo/default.mspx
Understanding FrontPage:
http://msdn.microsoft.com/office/understanding/frontpage/
===
| Sometimes FrontPage 2003 works just fine editing Windows SharePoint
Services
| aspx pages,
| but other times I get an error:
|
| "The server could not process your request.
| Contact your Internet service provider or web server administrator to make
| sure that the server has FrontPage Server Extensions installed."
|
| Being that WSS decided to place a @ Register for a component I no longer
| want, need or use at the top of many pages, and the *only* supported way
to
| edit these pages is by using FP2003, the function *really* should
work.....
|
|
| Manby pages work, the problem seems to be mor frequent on pages with a
fair
| number of web parts.
|
|
|
 
D

david mckenzie

Hmmm - About the amount of support I might have expected from FrontPage
Is it any wonder why developers are upset Visual Studio isn't the IDE for
SharePoint?
 
K

Kevin Spencer

Hmmm - About the amount of support I might have expected from FrontPage
Is it any wonder why developers are upset Visual Studio isn't the IDE for
SharePoint?
Click to expand...

Visual Studio.Net IS the IDE for developing Web Parts. FrontPage has a
number of tools for editing SharePoint pages. And SharePoint itself has
administration web pages that do the rest. There are good reasons for this.
SharePoint is completely database-driven, and accessed through a number of
..Net classes. I'm not sure what "developers" you're referring to, but
whoever they are, they don't know much about SharePoint.

As to your question, I don't know the exact sequence of events that lead to
your problem, as you didn't specify.

Finally, sending you to the appropriate support group for a given technology
is the amount of support you SHOULD expect from anyone. FrontPage can do
quite a few things. Among them are some capabilities for doing some work
with SharePoint sites. Most people use FrontPage for other purposes, and
therefore are not as knowledgable about SharePoint as you may need. The
SharePoint newsgroups support the entire SharePoint technology, and have
MVPs that work with SharePoint every day on a continuing basis.

--
HTH,
Kevin Spencer
..Net Developer
Microsoft MVP
Big things are made up
of lots of little things.
 
D

David McKenzie

Sorry for being a little pissy there.
What can I say, from where I sit, SharePoint has a multiple personality
disorder.
It's an Office product that is a free add-on to the Server product. There
are Data View Web Parts which are entirely designed in FrontPage 2003,
other web parts which are developed in VS.Net 2003.
And the ONLY supported way to access the portion of the page I need to edit
is through FP2003.
Which sputters out on me whenever that page has more than a handfull of web
parts.

In the past, I have removed all the web parts, made modifications in FP2003
and then re-added all the web parts.
The problem is that I now have actual users, and find it more difficult to
schedule this activity.

The root of this particular problem *does* lie in WSS, I guess your
recommendations to go elswhere are appropriate.

I had just hoped that someone might be able to help me understand why
FrontPage would behave inconsistantly.
the error message:
"The server could not process your request.
Contact your Internet service provider or web server administrator to make
sure that the server has FrontPage Server Extensions installed."
is not in the least bit helpful - I suspect it is related to some sort of
request not being fulfilled in a given time.
Clicking "Details" on this dialog box returns a blank message.
A little clicking around google tells me that my guess is valid, but I did
not see any way to increase the tim-out threashold
 
K

Kevin Spencer

Hi David,

FWIW, I can probably give you a few clues as to the nature of your problem.

SharePoint is a technology which depends ENTIRELY upon a SQL Server
database. Not only are WebParts stored in the database, but EVERYTHING is
stored in a database, including the pages/HTML/images/files it serves.
Naturally, this can make for quite a load on the database.

When you "create" WebParts in FrontPage, you're not actually creating
WebParts at all. You're creating .dwp xml files that specify set properties
of an instance of a WebPart. The WebPart itself is a class in a DLL located
in either the Global Assembly Cache, or the \bin folder of your site (if you
are using custom WebParts). FrontPage can create and allow you to modify
..dwp files, and insert them into a WebParts Page, as well as modify the HTML
of the Template. FrontPage does this by interacting with the SharePoint .Net
object model, just as the web page administration does.

It is entirely possible that you may be overtaxing the back end of WSS, but
it's hard to know for sure, as you can certainly do some things in FrontPage
that can cause problems, although this is rare. It depends upon what exactly
you're doing. If you're simply inserting and customizing WebParts, it's
probably a performance issue.

Again, the SharePoint newsgroups would have more experts than this one.
Although I have used WSS and SPS a fair amount, I would hardly call myself
an expert.

--
HTH,
Kevin Spencer
..Net Developer
Microsoft MVP
Big things are made up
of lots of little things.
 
D

David McKenzie

Thanks for the reply Kevin

I was aware of the considerations listed below, but it is good to share the
knowledge.
^_^
As to the backend server , it is a 3 GHZ processor with 4 GB memory which
serves a WSS deployment which totals about 5000 hits a month.
So if there is a performance problem, I do not think it is over-utilization
by users.
All I am doing is trying to open the default.aspx page in FP.
But, all the web parts on the page and in the web part page gallery need to
load as well (as best as I can tell)
There are 18 web parts on the page, which while more than a few, is the
number of things our users thought would be useful.

All this might be a bit off-topic for the list, but what with WSS gaining
popularity and VS2005 in public beta, this stuff is less esoteric by the
day.

All this leading to the actual, kinda on-topic question:

If this message is the result of a specific time interval, can that interval
be modified for more involved web part pages?
 
K

Kevin Spencer

If this message is the result of a specific time interval, can that
interval
be modified for more involved web part pages?
Click to expand...

Well, David, now you know why you were referred to the SharePoint
newsgroups! You're definitely out of the realm of my expertise now!

--
HTH,
Kevin Spencer
..Net Developer
Microsoft MVP
Big things are made up
of lots of little things.
 
D

David McKenzie

Did mention that Tom was right with the re-direct?
^_^
I didnt really get a Frontpage answer, but a perfectly acceptable
work-around
 
T

Tom Pepper Willett

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

"THE SERVER COULD NOT COMPLETE YOUR REQUEST" 4
Search Button Functionality - Errror - FrontPage Server Extensions 1
FrontPage could not parse 0
Server Could Not Complete Request 2
404 Not Found - Not Found The requested URL /_vti_bin/shtml.exe/_vti_rpcwas not found on this server 2
Frontpage Database Question 2
How do I display data from an SQL server in SharePoint? 1
Hit counter 1

Top