Sharepoint Forum

Ask Question   UnAnswered
Home » Forum » Sharepoint       RSS Feeds

FrontPage soap:Server Exception - not registered as safe on this site WORKAROUND

  Asked By: Adam    Date: Jul 24    Category: Sharepoint    Views: 2049

Just thought I would share this workaround to a problem that has bugged me
for a some time now.

As you may know, IP-bound Web Sites (SharePoint Virtual Servers) are not
supported in SPS or in WSS (see KB 830342). You can only use the (All
Assigned) IP address option.

Consequently, to host multiple SPS or WSS we must either use unique IIS host
headers OR use unique ports.

When using host headers, custom Web Parts must be placed in the GAC or pages
on which these Web Parts are included will not be editable in FrontPage even
though they are properly created and configured as safe. When we attempt to
edit the page in FrontPage 2003, it will display the following error:

The server could not complete your request. Contact your Internet service
provider or Web server administrator to make sure that the server has the
FrontPage Server Extensions or SharePoint Services installed.

With the following additional details:

soap:Server Exception of type

Microsoft.SharePoint.SoapServer.SoapServerException was thrown. A Web Part
or Web Form Control on this Web Part Page cannot be displayed or imported
because it is not registered as safe on this site. You may not be able to
open this page in an HTML editor that is compatible with Microsoft Windows
SharePoint Services, such as Microsoft Office FrontPage. To fix this page,
contact the site administrator to have the Web Part or Web Form Control
configured as safe. You can also remove the Web Part or Web Form Control
from the page by using the Web Parts Maintenance Page. If you have the
correct permissions, you can use this page to disable Web Parts temporarily
or remove personal settings. For more information, contact your site

To work around this bug, configure a unique port number for localhost in the
host headers of the IIS Web Site instead of OR in addition to the existing
host headers. Then open the Web Site in FrontPage using the localhost port
version of the host header.

For instance, if the original host header created was http://DC01> on port
80. We could add an unused port (like port 88) to access the site at
http://localhost:88 (using a unique port requires the use of the http://
prefix in Internet Explorer). When we want to edit the site in FrontPage we
would use the http://localhost:88 address and we skirt the host header bug
described above editing pages that contain custom Web Parts. We can browse
to the site in Internet explorer using either URL.



1 Answer Found

Answer #1    Answered By: Travis Turner     Answered On: Jul 24

We have the same issue today, came to the same conclusions as yours. Hopefully this will be fixed in a service pack