Article ID: 905496
Article Last Modified on 3/23/2007
APPLIES TO
- Microsoft Windows Server 2003 Service Pack 1
SYMPTOMS
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:
<xs:attribute type="xs:string" use="required" fixed="RDBMS/Statements/emps" name="location"/>
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.
CAUSE
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.
RESOLUTION
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.
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.
Date Time Version Size File name -------------------------------------------------------------- 24-Aug-2005 00:26 1.1.4322.2345 573,440 System.web.services.dll 24-Aug-2005 00:30 1.1.4322.2345 1,355,776 System.xml.dll
WORKAROUND
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:
public class Test {
[DefaultValue("RDBMS/Statements/emps")]
public string location = "RDBMS/Statements/emps";
}
To work around this problem, remove the DefaultValue attribute:
public class Test {
public string location = "RDBMS/Statements/emps";
}
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
MORE INFORMATION
For more 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
Keywords: kbwinserv2003sp2fix kbtshoot kbfix kbbug kbpubtypekc kbqfe kbhotfixserver KB905496
