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

When you try to modify a portal site that contains a Web Part, you receive a message. Additionally, when you add an Online Library Web Part to a page, you receive the following error message: This problem occurs when you try to modify a portal site that contains a Web Part by using a method that is similar to one of the following methods:

• You try to edit your portal site Web page by using Microsoft Office FrontPage 2003.
• You try to export a Web Part.

You receive the following message: If you click Details, the following appears in the Message Details dialog box: You can successfully view the Web page when you open the portal site in Microsoft Internet Explorer, and you have configured all Web Parts correctly.

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”
Category: Devices

This problem occurs when one or both of the following conditions are true:

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

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.

To resolve this problem, obtain the latest service pack for Windows SharePoint Services. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

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 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 Cache

If 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 Mode

If 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:

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in Windows SharePoint Services Service Pack 2.