Re: Frontpage2003 Error Accessing default.asp

From: John Jansen \(MSFT\) (johnjan_at_online.microsoft.com)
Date: 07/08/04 

Date: Thu, 8 Jul 2004 16:18:24 -0700

Are you sure that it is the number of web parts and not the web parts
individually causing your problems? Can you remove them one by one and see
if that enables you to then edit the page in FrontPage? (in other words,
make it so the page always has 18 web parts, but remove one and test; put it
back, remove a different one and test, put it back). The most common reason
I've seen this rather unhelpful error is due to a specific web part, not the
number of web parts.

What is the exact page directive you need to remove? Do you know when it
showed up? I assume you mean "found its way to the top of every page in
every site" not just "every site", correct? If you are positive you really
don't need it, and you know for sure it is there by mistake (something I
haven't ever seen before) your only best bet, I'm afraid is to use Find and
Replace in FrontPage. This will allow you to find the string, replace it
with nothing, and then save the query to your desktop so you can at least
just load it up for each site and run it instead of having to
copy/paste/check box/check box/click button every time.

The Edit in MS FrontPage button may be grayed out if the page is being
rendered with URL parameters (like when you click on "Modify this page"
sometimes), as well as other reasons (like some metatags, but that doesn't
sound like your issue). 

-- 
Thanks!
John Jansen
Microsoft Office FrontPage
This posting is provided "AS IS" with no warranties, and confers no rights.
"David McKenzie" <DavidMcKenzie@bonbon.net> wrote in message 
news:uJR6lsSZEHA.4092@TK2MSFTNGP11.phx.gbl...
>I have had inconsistant levels of success with Frontpage2003 opening the
> default.aspx of various sites.
> Failure is characterized by the 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."
> There is a "Details" button, but clicking it results in an empty text 
> box -
> I am guessing this is something like the "inner error" object.
>
> Anyways, I get this error on pages with more than a couple web parts (for
> example, my main site page has 18 web parts and is uneditable).
> In the past I have deleted all the web parts from a page before making
> modifications.
> As our WSS site gains wider adoption and complexity, this situation has
> become less acceptable.
>
> My current problem is the need to remove an @ Register directive which has
> found it's way on to the top of every site in my virtual server.
> I would prefer not having to do this off hours - there are just so many
> better things to do on the weekend.
>
> I am guessing that this message appears after some time interval.  If I
> could extend that value, I might be able to edit the page.
> Alternativly, if anyone knows another way to edit the source of a WSS aspx
> page, that might do.
>
> And of course, I would love to know how the %^*&^) @ Register got there in
> the first place.
> I have @ Register directives for
> 1.    an older version of Leadit.Sharepoint.Essentials
> 2.    Microsoft.Office.DataParts
> 3.    another home-grown web part (only on a couple pages)
>
> I have half a dozen home grown web parts - only one gets the special @
> Register treatment
>
>
>
> Also...Does anyoine know why the "Edit in Microsoft Frontpage" opetion 
> does
> not always show up in the IE File menu?
> Flaky stuff - I think a previous poster used the work "squirrely"  - but I
> love it.
> ^_^
>
>
>
Loading