Article ID: 927495 - View products that this article applies to.
Consider the following scenario. In a Microsoft .NET Framework 1.1-based application, you set two objects to reference one another. You use a serialization surrogate to serialize XML data or to deserialize XML data. You compile the application. In this scenario, a SerializationException exception occurs. Additionally, you receive the following error message:
This problem occurs if one of the following conditions is true:
The object with ID 3 was referenced in a fixup but does not exist.
Hotfix informationA supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that is described in this article. Apply it only 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 Windows Server 2003 service pack or the next .NET Framework 1.1 service pack that contains this hotfix.
To resolve this problem immediately, contact Microsoft Customer Support Services to obtain the hotfix. For a complete list of Microsoft Customer Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=supportNote 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.Note After you install this hotfix, you must change the application. For more information, see the "More information" section.
PrerequisitesYou must have the .NET Framework 1.1 SP1 installed to apply this hotfix. If you run the application in Windows Server 2003, you must have Windows Server 2003 SP2 installed to apply this hotfix.
Restart requirementYou do not have to restart the computer after you apply this hotfix.
Hotfix replacement informationThis hotfix replaces the hotfix that is described in the following Microsoft Knowledge Base article:
(http://support.microsoft.com/kb/893251/ )FIX: Errors may occur when you use the BinaryFormatter class or the SoapFormatter class to serialize an object in the .NET Framework 1.1
File informationThe 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 item in Control Panel.
Windows Server 2003
Collapse this tableExpand this table
Microsoft .NET Framework 1.1
Collapse this tableExpand this table
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
This hotfix adds a new method that is called GetSurrogateForCyclicalReference to the FormatterServices class. To resolve the problem that is described in the "Symptoms" section, you must use the GetSurrogateForCyclicalReference method to return a serialization surrogate. The serialization surrogate can handle the cyclical references that cause the problem. The following sample code shows how the new method is used:
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/824684/ )Description of the standard terminology that is used to describe Microsoft software updates
This problem may also occur in the .NET Framework 2.0. To obtain the hotfix for the .NET Framework 2.0, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/931634/ )FIX: Error message when you use a serialization surrogate to serialize XML data or to deserialize XML data in the Microsoft .NET Framework 2.0: "The object with ID 3 was referenced in a fixup but does not exist"