FIX: The data for the values may be missing in the XML instance documents if you use a proxy for a Web service that was created by importing schema

Consider the following scenario. You use a proxy for a Web service that was created by importing schema. The schema contains values for attributes that are fixed and required in Microsoft Windows Server 2003 Service Pack 1 (SP1). When you use the proxy, the data for the values may be missing in the XML instance documents, even though the schema specifies that the values are required. For example, this problem may occur for the following schema definition: The value for the location attribute may be missing in the XML instance documents, even though the value is required. This problem may occur with elements and attributes.

Note This problem may exist in other versions of the Windows operating systems. However, this hotfix applies only to Windows Server 2003 SP1.

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

• You serialize classes that were created by importing a schema that contains values for attributes or elements that are fixed and required.
• You use a proxy for a Web service that uses a schema that contains values for attributes or elements that are fixed and required. The data for the fixed and required values may be missing in the XML instance documents, even though the schema specifies that the values are required.
• An element has a fixed value and the element’s minOccurs property is 1 or larger. This value indicates that the element is required.

This problem occurs because of the way that the Wsdl.exe tool, the Xsd.exe tool, and other schema-import mechanisms, such as the Add Web Reference dialog box in Microsoft Visual Studio, handle fixed values. Typically, schema-import mechanisms treat values and default values in the same way and generate a member with an initializer and a DefaultValue custom attribute.

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To apply this hotfix, you must have the .NET Framework 1.1 Service Pack 1 (SP1) installed on your computer.

Restart requirement

You do not have to restart the computer after you apply this software update.

Hotfix replacement information

This hotfix does not replace any other software updates.

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.

To work around this problem, generate the code file for the proxy class by using the Wsdl.exe tool, and then remove the DefaultValue attribute. For example, you have code that is similar to the following:To work around this problem, remove the DefaultValue attribute:

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

For more information, click the following article number to view the article in the Microsoft Knowledge Base: