FIX: The WSDL tool cannot successfully generate the proxy when the WSDL file imports multiple schemas that in turn import a common schema in the .NET Framework 1.1 Service Pack 1

The Web Services Description Language (WSDL) tool that is named Wsdl.exe cannot successfully generate the proxy when the WSDL file imports multiple schemas that in turn import a common schema in the Microsoft .NET Framework 1.1 Service Pack 1. A WSDL file can import a schema that includes multiple schemas by using the xsd:include element. However, when these schemas include a common schema or import a common schema, the WSDL tool cannot generate the proxy for the Web service.

When this problem occurs, you receive multiple error messages that are similar to the following:For example, consider a scenario that includes the following files:

• Example.wsdl
• Top.xsd
• Schema2.xsd
• Schema3.xsd
• Common.xsd

In this scenario, the Top.xsd schema includes both the Schema2.xsd schema and the Schema3.xsd schema. The Schema2.xsd schema and the Schema3.xsd schema include the Common.xsd schema. If the Example.wsdl file imports the Top.xsd file, the WSDL tool cannot successfully generate the proxy.

Note When you apply this hotfix, you must also apply one of the hotfixes that is described in the following Microsoft Knowledge Base articles.

If the .NET Framework 1.1 Service Pack 1 is installed, but Visual Studio .NET 2003 is not installed:

If the .NET Framework 1.1 Service Pack 1 and Visual Studio .NET 2003 are both installed:

If you have a later version of the .NET Framework installed, or the computer is running Microsoft Windows Server 2003 Service Pack 1 or a later service pack, no additional hotfix is required.

A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next .NET Framework 1.1 service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

Prerequisites

You must have the .NET Framework 1.1 Service Pack 1 installed. In addition, you must have either Visual Studio .NET 2003 or the .NET Framework 1.1 Software Development Kit (SDK) installed.

Restart requirement

You do not have to restart your computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

For additional information about a hotfix that is available for the .NET Framework 1.1, click the following article number to view the article in the Microsoft Knowledge Base: For additional information, click the following article number to view the article in the Microsoft Knowledge Base: