You are currently offline, waiting for your internet to reconnect

FIX: The WSDL tool cannot generate a Web service proxy when the tool imports schema that includes multiple schema

This article has been archived. It is offered "as is" and will no longer be updated.
When the Web Services Description Language (WSDL) imports a schema that includes multiple schema by using the xsd:include element and when these schemas include any command schema, the WSDL tool (Wsdl.exe) cannot generate the proxy for the Web service. For example, you have the following files:
  • Example.wsdl
  • Top.xsd
  • Schema2.xsd
  • Schema3.xsd
  • Common.xsd
In this example, the Top.xsd schema includes the Schema2.xsd schema and the Schema3.xsd schema, and both of these schema include the Common.xsd schema. If the Example.wsdl file imports the Top.xsd schema, proxy generation by using the Example.wsdl file fails.
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 Microsoft .NET Framework 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.

The English version of this hotfix has the file attributes (or later) 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.
   Date         Time   Version       Size       File name                    Platform   ----------------------------------------------------------------------------------   30-May-2003  00:10  1.0.3705.430     20,480  Perfcounter.dll              x86   30-May-2003  11:48  1.0.3705.430  1,175,552  System.dll                   x86   30-May-2003  11:49  1.0.3705.430    311,296  System.runtime.remoting.dll  x86   30-May-2003  11:52  1.0.3705.430    503,808      x86   30-May-2003  11:49  1.0.3705.430  1,302,528  System.xml.dll               x86   30-May-2003  11:49  1.0.3705.430     65,536  Wsdl.exe                     x86
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section of this article.
For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates

Article ID: 821544 - Last Review: 01/17/2015 07:29:31 - Revision: 1.4

Microsoft .NET Framework 1.1

  • kbnosurvey kbarchive kbhotfixserver kbqfe kbhotfixserver kbqfe kbnetframe100presp3fix kbfix kbbug KB821544