Microsoft KB Archive/813739

= FP2002: How to Resolve Problems in a FrontPage Web When the Standard Resolutions Do Not Work =

Article ID: 813739

Article Last Modified on 2/1/2007

-

APPLIES TO


 * Microsoft FrontPage 2002 Standard Edition

-



SUMMARY
Your FrontPage Web may exhibit problems that appear to have an obvious cause, but the standard resolution or workaround does not resolve the problem.

These may include the following:
 * Hyperlinks are broken.
 * Frames functionality does not work or frames do not appear on a Web page.
 * The Web cannot be opened without generating an error message.
 * Pages in your Web cannot be opened without generating an error message.
 * The Navigation bar does not appear on a Web page.
 * The parent page listed in the navigation structure is incorrect.
 * Deleted text or deleted paragraphs appear when the Web is viewed in a browser.
 * FrontPage stops responding when you are working in a Web.
 * You receive an &quot;Illegal operation&quot; error message or other error messages when you try to save a Web page.
 * Navigation buttons or shared borders are displayed incorrectly on Web pages.
 * Some Web pages are duplicated after you publish the Web.

This article describes additional steps that you can take when the standard resolutions or workarounds do not resolve the problem.



MORE INFORMATION
Some of the problems described in the &quot;Symptoms&quot; section may be caused by damaged content in your Web. For example, a specific Web page contained in your Web may be damaged, or a part of your Web structure may be damaged.

How to Determine Whether the Content Is Damaged
To determine whether your Web contains damaged content, use the following methods:
 * Create a new Web similar to the problem Web, and then determine whether the same problems also occur in the new Web.
 * If the problem occurs on a specific Web page, create a new Web page in your Web. If the problem still occurs on the new Web page, try re-creating the new page in a new Web.
 * If the problem occurs only after the Web is published, the problem is most likely related to server extensions or your Internet connection.

How to Repair Damaged Content
To troubleshoot damaged content in your Web, follow these steps:  Can you isolate the problem to a specific Web page? If you cannot isolate it to a specific page and the problem appears to occur across many pages in your Web, go to step 3. After you have isolated the problem to a specific page in your Web, try the following:  Remove specific sections of the page. If this resolves the problem, try re-creating the section. Remove a specific component on your Web page. If this resolves the problem, try reinserting the component on your Web page. If the problem is not resolved after you remove specific sections or components on your Web page, try re-creating the page in your Web, or try re-creating the page in a new Web.

Note Do not use sections of other Web pages, or components from other pages, in your Web unless you know that the section or component is valid and does not cause an error. If the problem is not resolved after you re-create the page or component, the problem probably involves a Web component or the Web structure. Try re-creating a new Web. When you do so, use the following methods:  Copy the Structure.cnf file from the damaged Web to your new Web.</li> Import your damaged Web into a new Web.</li> Re-create your damaged Web in a new Web page by page.</li></ul> </li> Search the Microsoft Knowledge Base for articles that may resolve the problem that you are experiencing in your FrontPage Web. To do this, visit the following Microsoft Knowledge Base Web site:

FrontPage 2002 Articles in the Microsoft Knowledge Base

</li></ol>

Keywords: kbinfo KB813739

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.