Home Bulletins Calendar Contact Us Lit. Minister Schd. Mass Times Music New Parishioner Organizations Photo Album Search Table of Contents Youth Group


Website Issue on May 16, 2002

 

After the old website was removed using Bulletproof FTP, the new website was published using Microsoft FrontPage 2002.  However the top and bottom shared borders contained text (images were left off) from the actual homepage itself.  Iwaynet confirmed that a fix had to be made.  Read about the fix from support.microsoft.com below:

FP: Include Components and Shared Borders Are Displayed Incorrectly on IIS (Q298827)


The information in this article applies to:

 

  • SharePoint Team Services from Microsoft
  • FrontPage 2002 Server Extensions from Microsoft
  • Microsoft FrontPage 2002
  • Microsoft FrontPage 2000
  • Microsoft FrontPage 98 for Windows


 


IMPORTANT : This article contains information about editing the registry. Before you edit the registry, make sure that you understand how to restore it if a problem occurs. For information about how to do this, see the "Restoring the Registry" Help topic in Regedit.exe or the "Restoring a Registry Key" Help topic in Regedt32.exe.

 

SYMPTOMS

After you upgrade your Microsoft Internet Information Services-based Web site to FrontPage 2002 Server Extensions or SharePoint Team Services from Microsoft, the include components and shared borders are not displayed correctly. The body of the main page is displayed as part of the shared border or the include component, appearing to duplicate data throughout the page. Also, after you insert a PhotoGallery or an Include page, you see the path to the page rather than the content of the page. In Normal view in FrontPage, the page appears correctly, but when you view it in a Web browser, you see only the path.


 

CAUSE

This problem is caused by the configuration of the performance tuning settings on the server, in particular, the Max Cache Document Size setting. For information about how to configure these settings, see the "More Information" section later in this article.


 

WORKAROUND

Remove the registry keys that affect the components. To do this, follow these steps.

WARNING : Using Registry Editor incorrectly can cause serious problems that may require that you reinstall your operating system. Microsoft cannot guarantee that problems that result from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk.

For information about how to edit the registry, see the "Changing Keys and Values" Help topic in Registry Editor (Regedit.exe) or the "Add and Delete Information in the Registry" and "Edit Registry Data" Help topics in Regedt32.exe. Microsoft recommends that you back up the registry before you edit it. If you are running Windows NT or Windows 2000, Microsoft also recommends that you update your Emergency Repair Disk (ERD).
 

Global Settings

IMPORTANT : Follow these steps carefully, because these settings affect all sites on your server.

  1. On the Windows Start menu, click Run .

     
  2. In the Open box, type regedit and then click OK .

     
  3. Locate the following registry key:

     

    HKEY_LOCAL_MACHINE\Software\Microsoft\Shared Tools\Web Server Extensions\All Ports

  4. Remove the following entries:

     
    • CacheMaxDocMeta

       
    • CacheMaxInclude

       
    • CacheMaxImage

       
    • CacheMaxIncludeSize

       
  5. Quit Registry Editor.

     
  6. Recalculate any affected Webs on the Web server.

     

Site-Specific Settings

IMPORTANT : Follow these steps for each site that is still experiencing problems.

  1. On the Windows Start menu, click Run .

     
  2. In the Open box, type regedit and then click OK .

     
  3. Locate the following registry subkey

     

    HKEY_LOCAL_MACHINE\Software\Microsoft\Shared Tools\Web Server Extensions\Ports\Port /LM/W3SVC/#:

    where # is the Microsoft Internet Information Services (IIS) instance of the site.

     

  4. Remove the following entries:

     
    • CacheMaxDocMeta

       
    • CacheMaxInclude

       
    • CacheMaxImage

       
    • CacheMaxIncludeSize

       
  5. Quit Registry Editor.

     
  6. Recalculate any affected Webs on the specific Web site.

     

 


 

RESOLUTION

To resolve this problem, obtain the latest service pack for Microsoft Office XP. For additional information, please see the following article in the Microsoft Knowledge Base:

Q307841 OFFXP: How to Obtain the Latest Office XP Service Pack

 


 

STATUS

Microsoft has confirmed this to be a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Microsoft Office XP Service Pack 1.


 

MORE INFORMATION

For more information about the performance tuning options and registry values used by FrontPage 2002 Server Extensions and SharePoint Team Services, visit the following Microsoft Web site:

http://www.microsoft.com/TechNet/prodtechnol/sharepnt/proddocs/admindoc/ows000.asp

For additional information about this problem and UNIX servers, click the article number below to view the article in the Microsoft Knowledge Base:

Q299360 FP2002: Include Component and Shared Borders Are Displayed Incorrectly on UNIX Servers

 

This page was last updated on: Wednesday May 22, 2002.
Visitors: Hit Counter


Questions or Comments?  E-mail the Webmaster at Webmaster@SaintJosephCathedral.org.

 

This Diocese of Columbus WebRing
site is maintained by
Saint Joseph Cathderal
of Columbus, Ohio
.
 

 
[Webring Home] [Prev] [Next] [Random]