Re: FrontPage and the dreaded SoapServerException problem
- From: "Shane Young" <shane at sharepoint911 .com>
- Date: Wed, 31 Aug 2005 11:23:04 -0400
Did you make sure you don't have Front Page Server Extensions installed on
the server?
--
Shane Young
SharePoint911 - "SharePoint Help...Now!"
"Dan Harner" <nospamforme@xxxxxxxxxx> wrote in message
news:e5u$KljrFHA.3080@xxxxxxxxxxxxxxxxxxxxxxx
> All,
>
> We're having a problem that seems to be fairly common - the difference
> being that none of the solutions that I have found work.
>
> What we have is an internally developed web part and web part package. The
> web part package was deployed via stsadm -addwppack. Running
> stsadm -enumwppacks after the fact shows the web part. The web part works
> fine when displayed by an end user. However, when we attempt to edit a
> page containing the web part with FrontPage, we get this all-too-familiar
> error:
>
> 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 necessary permissions, you can use this page to disable Web Parts
> temporarily or remove personal settings. For more information, contact
> your site administrator.
>
> The web part is properly registered as a safe control in the web.config.
>
> We changed the trust level to WSS_Medium - no dice.
>
> We changed the trust level to Full - no dice.
>
> We read KB830342 and modified the virtual server to use (All Unassigned)
> instead of a specific IP address - no dice.
>
> We configured the site to use host headers (there is one SharePoint and
> several non-Sharepoint sites on this box) - no dice.
>
> We copied the web part to the GAC - no dice.
>
> We made sure that the CentralAdminAppPool, MSSharePointAppPool, and
> MSSharePointPortalAppPool were configured to run as a particular domain
> account, as opposed to local system. This domain account is a member of
> the STS_WPG, SPS_WPG, SPS_Query, IIS_WPG, and Power Users groups on the
> Sharepoint box - no dice.
>
> Naturally, we reset IIS after each change..nothing we do seems to have any
> effect...
>
> Any thoughts?
>
> TIA,
>
> Dan Harner
>
.
- Follow-Ups:
- Re: FrontPage and the dreaded SoapServerException problem
- From: Dan Harner
- Re: FrontPage and the dreaded SoapServerException problem
- Prev by Date: Re: Can't access my server outside
- Next by Date: Re: Virtual Folders in a document library?
- Previous by thread: Re: Can't access my server outside
- Next by thread: Re: FrontPage and the dreaded SoapServerException problem
- Index(es):
Relevant Pages
|