Include components and shared borders are displayed incorrectly on IIS (298827)
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
This article was previously published under Q298827 IMPORTANT: This article contains information about modifying the registry.
Before you modify the registry, make sure to back it up and make sure that you
understand how to restore the registry if a problem occurs. For information
about how to back up, restore, and edit the registry, click the following
article number to view the article in the Microsoft Knowledge Base: 256986 Description of the Microsoft Windows Registry
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: If you use Registry Editor incorrectly, you may cause serious
problems that may require you to reinstall your operating system. Microsoft
cannot guarantee that you can solve problems that result from using Registry
Editor incorrectly. Use Registry Editor at your own risk. Global SettingsIMPORTANT: Follow these steps carefully, because these settings affect all
sites on your server.
- On the Windows Start menu, click Run.
- In the Open box, type regedit and then click OK.
- Locate the following registry key:
HKEY_LOCAL_MACHINE\Software\Microsoft\Shared Tools\Web Server Extensions\All Ports
- Remove the following entries:
- CacheMaxDocMeta
- CacheMaxInclude
- CacheMaxImage
- CacheMaxIncludeSize
- Quit Registry Editor.
- Recalculate any affected Webs on the Web server.
Site-Specific SettingsIMPORTANT: Follow these steps for each site that is still experiencing
problems.
- On the Windows Start menu, click Run.
- In the Open box, type regedit and then click OK.
- 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.
- Remove the following entries:
- CacheMaxDocMeta
- CacheMaxInclude
- CacheMaxImage
- CacheMaxIncludeSize
- Quit Registry Editor.
- Recalculate any affected Webs on the specific Web
site.
RESOLUTIONTo resolve this problem, obtain the latest
service pack for Microsoft Office XP. For additional information, click the
following article number to view the article in the Microsoft Knowledge Base: 307841 OFFXP: How to Obtain the Latest Office XP Service Pack
STATUSMicrosoft
has confirmed that this is 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.
Modification Type: | Major | Last Reviewed: | 8/12/2005 |
---|
Keywords: | kbUpgrade kbWebServer kbdisplay kbOfficeXPsp1Fix KB298827 |
---|
|