You receive a content is blocked error message when you preview a Web page in FrontPage 2003 (817939)
The information in this article applies to:
- Microsoft Office FrontPage 2003
SYMPTOMS When you install FrontPage 2003 on a computer that is
running Windows Server 2003, you may experience any of the following symptoms:
- When you use the Inline Frame to embed an
existing Web page in your page, and then you click the Preview
tab, you receive the following error message:
Content
within this application coming from the Web site listed below is being blocked
by Internet Explorer Enhanced Security Configuration.
file://C:\Documents and Settings\Administrator\Local Settings\Temporary
Internet Files\FrontPageTempDir\pvw1.htm When you click
Add, and then in the Trusted sites dialog
box, you click Add to "Add this Web site to the zone", you
receive the following error message: You have entered an
invalid wildcard sequence. Examples of valid patterns:
*://*.microsoft.com http://*.microsoft.co.jp ftp://157.54.23.41/
file:\\localsvr\share *://157.54.100-200.* Examples of invalid
patterns: http://microsoft.*.com ftp://*
FrontPage
2003 uses a temporary local path for the embedded existing Web page, but you
cannot add the temporary local path to a Trusted sites zone
because Internet Explorer does not support adding a local file path to
Trusted sites zones. - When you click Publish on the
File menu, and then click the WPP's button in
the Publish destination dialog box to view a list of Web
Presence Providers (WPPs), the Web page may not appear correctly in Internet
Explorer. For example, you may not be prompted by Internet Explorer to add the
site to the Trusted sites zone, and the Web page is
blank.
Note This issue does not occur if the site is added to the
Trusted sites zone.
For additional
information about this issue, click the following article number to view the
article in the Microsoft Knowledge Base: 816706 Web Page Is Not Displayed Correctly When You Click the WPP's Button - When you create a hyperlink, and then click the hyperlink
in a preview, nothing occurs. The hyperlink does not work.
- When you open a Web on a SharePoint Team Services server,
you are always prompted for username and password even if the SharePoint Team
Services server uses Windows Authentication.
- Some FrontPage 2003 dynamic HTML (DHTML) content is
blocked. When you preview the preview the page, DHTML content does not work or
appear correctly in the browser.
- When you preview a Web, content from outside the current
Web is blocked if it contains "unsafe" content such as scripts, or ActiveX
Controls.
CAUSE This issue may occur if the Internet Explorer Enhanced
Security Configuration feature is enabled on your Windows Server 2003-based
computer. By default, this feature is enabled in Internet Explorer on Windows
Server 2003-based computers.
This enhanced level of security may
prevent certain Web sites from appearing as expected in Internet Explorer or
FrontPage 2003 previews, and programs that require the browser may not work as
expected because scripts, ActiveX Controls, and downloads are
disabled.RESOLUTION To resolve these issues, turn off Internet Explorer
Enhanced Security Configuration. To do this, click Add or remove
programs in Control Panel, click Add/Remove Windows
Components, and then click to clear the Internet Explorer
Enhanced Security Configuration check box. WARNING: If you turn off Enhanced Security Configuration, you may expose
your server to potential security attacks. Regardless of the browser
that you use, it is a good idea to restrict browsing on your server. To reduce
the risk to your server of potential attacks from malicious Web-based content:
- Do not use servers for browsing general Web
content.
- Use client computers to download files such as drivers and
service packs.
- Do not view sites that you cannot confirm are
secure.
- Use a limited user account instead of an administrator
account for general Web browsing.
- Use the Group Policy feature to keep unauthorized users
from making inappropriate changes to browser security settings.
- Use client computers to develop content using FrontPage
2003.
STATUS Microsoft
has confirmed that this is a problem in the Microsoft products that are listed
at the beginning of this article.
Modification Type: | Minor | Last Reviewed: | 1/10/2006 |
---|
Keywords: | kbwindowsinstaller kberrmsg kbprb KB817939 |
---|
|