Deserialization Problem CLR 1.1.4322.2379

[SpruceSB]

We have an application (VS 2003) that uses binary serialization /
deseralization with formatter surrogates for some features. It works ok on
CLR Versions 1.1.4322.573, 1.1.4322.2032, and 1.1.4322.2300 however on CLR
Version 1.1.4322.2379 it receives the following exception during
deserialization:

System.Runtime.Serialization.SerializationException: The object with ID 3
was referenced in a fixup but does not exist.
at
System.Runtime.Serialization.ObjectManager.GetCompletionInfo(FixupHolder
fixup, ObjectHolder& holder, Object& member, Boolean bThrowIfMissing)
at System.Runtime.Serialization.ObjectManager.CompleteObject(ObjectHolder
holder, Boolean bObjectFullyComplete)
at System.Runtime.Serialization.ObjectManager.DoFixups()
at
System.Runtime.Serialization.Formatters.Binary.ObjectReader.Deserialize(HeaderHandler
handler, __BinaryParser serParser, Boolean fCheck, IMethodCallMessage
methodCallMessage)
at
System.Runtime.Serialization.Formatters.Binary.BinaryFormatter.Deserialize(Stream
serializationStream, HeaderHandler handler, Boolean fCheck,
IMethodCallMessage methodCallMessage)
at
System.Runtime.Serialization.Formatters.Binary.BinaryFormatter.Deserialize(Stream
serializationStream)
at SerFixupErr.Form1.Button1_Click(Object sender, EventArgs e)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons
button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg,
IntPtr wparam, IntPtr lparam)

I cannot find the CLR Version 1.1.4322.2379 documented anywhere but it is
getting installed when our customers apply SP2 to Windows Server 2003.
There appears to be no way to just back out the CLR 1.1 update after the SP2
install so basically installing SP2 on Windows Server 2003 is "breaking" for
us.

I can provide a small program that exhibits this behavior (works on all but
1.1.4322.2379) if that would be helpful. This program is just a modified
version of the program shown in the following feedback (but CLR 2 / VS 2005
related).

http://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=93814

There appears to be a hotfix (KB931634) for what sounds like a similar
problem in CLR 2.0.

Any assistance would be appreciated.

 

[Walter Wang [MSFT]]

Hi,

Yes 1.1.4322.2379 is included in Win2003 SP2.

I've done some research and found a similar case report regarding similar
symptom, which also have some workaround from product group. Would you
please send the reproducible project to me so that I can verify if the
workaround applies? You can send me the code via email. My email address is
in my signature. Thanks.


Regards,
Walter Wang ([email protected], remove 'online.')
Microsoft Online Community Support

==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================

This posting is provided "AS IS" with no warranties, and confers no rights.

 

[SpruceSB]

Thank you for your response.

I have emailed you VB 2003 project files that produce the same exception as
our application (hopefully for the same underlying reasons).

 

[Walter Wang [MSFT]]

Thanks. I've been able to reproduce the issue as you described and
currently investigating it. I'll keep you updated.


Regards,
Walter Wang ([email protected], remove 'online.')
Microsoft Online Community Support

==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================

This posting is provided "AS IS" with no warranties, and confers no rights.

 

[Walter Wang [MSFT]]

For everyone who's monitoring this thread, the issue has been fixed by a
hotfix:

#FIX: Error message when you use a serialization surrogate to serialize XML
data or to deserialize XML data in the .NET Framework 1.1: "The object with
ID 3 was referenced in a fixup but does not exist"
http://support.microsoft.com/kb/927495/

Regards,
Walter Wang ([email protected], remove 'online.')
Microsoft Online Community Support

==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================

This posting is provided "AS IS" with no warranties, and confers no rights.