You receive a "Soap:Server Exception of Type Microsoft.SharePoint.SoapServer.SoapServerException" message when you try to edit a portal by using FrontPage 2003 or when you try to export a Web part
- You try to edit your portal site Web page by using Microsoft Office FrontPage 2003.
- You try to export a Web Part.
For more information, click the Details button.
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 administrator.
You may also find the following error in the application event log:
Event ID: 1000
Source: “Windows SharePoint Services 2.0”
Message: “Error: Failure in loading assembly: AssemblyName”
- 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.
- 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.
Method 1: Modify the Internet Protocol Address AssignmentIf 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 more information about how to configure Host Headers, click the following article number to view the article in the Microsoft Knowledge Base:
Method 2: Move Assemblies to the Global Assembly CacheIf you host a virtual server that has a host header name and you install your assemblies to the Bin folder, move the assemblies to the global assembly cache.
Method 3: Use the Windows SharePoint Services Scalable Hosting ModeIf none of the previous hosting configurations work for your situation, consider the scalable hosting mode in Windows SharePoint Services. This mode is described in the Windows SharePoint Services Administrator's Guide. View the "Server Farm with Multiple Host Names Deployment" topic under "Deployment Scenarios." To obtain the Windows SharePoint Services Administrator's Guide, visit the following Microsoft Web site:
Article ID: 830342 - Last Review: 12/08/2015 05:04:45 - Revision: 5.5
- kbnosurvey kbarchive kbbug kbnofix kberrmsg KB830342