Can't edit my sharepoint pages after enabling SSL on my site

From: A. Fox (e_at_mail.com)
Date: 05/25/04

  • Next message: Jay Griffin: "Rights to create virtual directories" 
    Date: Tue, 25 May 2004 16:54:32 +0100

    Hello all!
      firstly, sorry for the cross posting, but i'm not sure which group this
    belongs in!
    I've just enabled SSL on my sharepoint site, and tested it from both sides
    of the firewall, everything seems to be ok. The only problem is that now i
    can't customise my pages in Frontpage 2003 by clicking on the 'edit in
    frontpage' button from internet explorer. (This was working fine prior to my
    setting up SSL)
      The error that frontpage returns is as follows:

         ' 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. '

    I tried the following from a Microsoft article, but it didn't help.

    CAUSE
    This problem occurs when one or both of the following conditions are true:
      a.. You configure an Internet Information Services (IIS) virtual server
    that has an assigned IP address, and then extend that virtual server by
    using Windows SharePoint Services.
      b.. You configure an IIS virtual server that has a host header name, you
    extend that virtual server by using Windows SharePoint Services, and then
    you install Web Part assemblies in the Bin folder instead of in the global
    assembly cache.
    In each of these configurations, the Microsoft Office SharePoint Portal
    Server 2003 services cannot obtain sufficient information from the virtual
    server to load the Web Part or the Web Parts. Therefore, you receive the
    message that is described in the "Symptoms" section.
    WORKAROUND
    To work around this problem, use one of the following methods depending on
    your situation:
    Method 1: Modify the Internet Protocol Address Assignment
    If you have configured the virtual server with an assigned Internet Protocol
    (IP) address in Internet Information Services (IIS) Manager, configure the
    virtual server to use the (All Unassigned) IP address option.

    IP-bound virtual servers are not supported in SharePoint Portal Server 2003
    or in Windows SharePoint Services. You can use the (All Assigned) IP address
    option to configure IIS Host Header Web sites that do not cause this
    problem. For additional information about how to configure Host Headers,
    click the following article number to view the article in the Microsoft
    Knowledge Base:
    190008 HOW TO: Use Host Header names to host multiple sites from one IP
    address in IIS 5.0

    I'm really stuck now, so any suggestions are VERY welcome !!

    Thanks,

    Alasdair Fox

  • Next message: Jay Griffin: "Rights to create virtual directories"