Re: Frontpage2003 Error Accessing default.asp

From: David McKenzie (DavidMcKenzie_at_bonbon.net)
Date: 07/09/04 

Date: Thu, 8 Jul 2004 22:31:57 -0500

"John Jansen (MSFT)" <johnjan@online.microsoft.com> wrote ...
Hi John,
points in-line
> 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.
I am not exactly certain, that it is the amount, but the pages I have a
problem with are those with the most web parts.
I recall having the same message after moving to the 'release' version of
WSS and Office 2003 some time back, but that was resolved re-creating any
Web Capture web parts which were created with the Office 2003 beta web
components. There are none of those left now.
I can experiment a bit more with a test version of my site tommorrow.

I *have* seen some posts and informational pieces which describe this error
firing on a slow connection or poor performing server which leads me to
suppose that there might be a timeout condition.
If so - is there any way to extend the interval?

> What is the exact page directive you need to remove?
<%@ Register TagPrefix="WpNs1" Namespace="Leadit.SharePoint.Essentials"
Assembly="Leadit.SharePoint.Essentials, Version=1.0.0.1, Culture=neutral,
PublicKeyToken=74a77e060b19a1bf" %>
> Do you know when it showed up?
I had no idea it existed until it was discovered as described in the rather
lengthy post "Through the looking glass..." shortly before this post.
> 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.
good enough - as described in that earlier post, this directive causes
problems when I am attempting to get rid of this older version of the Leadit
webparts - I am certain I dont need it and it causes errors
Find and Replace is a neat idea, but I still have to get the page open in FP
> 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).
The situation I am describing is where the "Edit in Frontpage" option does
not appear at all (not even grayed out)
I close the browser, open a new instance and the Edit option appears.
This behavior is not particularly consistant

Thanks for your comments

David

Loading