KB928366 causes error in .NET BinaryFormatter.Deserialise

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

After applying the above hotfix, when deserialising a complex object
involving circular references I get the following exception:

System.Runtime.Serialization.SerializationException: The object with ID 28
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)

If I remove the hotfix, the same code works again. Any ideas? Where should I
go to report this kind of bug? I tried ringing Microsoft, but it seemed to be
over the head of the person I spoke to.
 
This appears to be where one would report bugs:
http://support.microsoft.com/gp/contactbug
Report a Microsoft Product Bug

If you think you have found a bug in a Microsoft product, contact our Microsoft Product
Support Services department.
(800) MICROSOFT (642-7676)
Click to expand...

Heck, I still can't figure out how MICROSOFT translates to 642-7676
MICROSO ? <w>

MowGreen [MVP 2003-2007]
===============
*-343-* FDNY
Never Forgotten
===============
 
That link just gives you phone numbers, and when you call they direct you to
google for you answer.

After searching for a while, I came across this site:

https://connect.microsoft.com/

I think this may be the appropriate place to post bugs.

MowGreen said:
This appears to be where one would report bugs:
http://support.microsoft.com/gp/contactbug
Report a Microsoft Product Bug

If you think you have found a bug in a Microsoft product, contact our Microsoft Product
Support Services department.
(800) MICROSOFT (642-7676)
Click to expand...

Heck, I still can't figure out how MICROSOFT translates to 642-7676
MICROSO ? <w>

MowGreen [MVP 2003-2007]
===============
*-343-* FDNY
Never Forgotten
===============

After applying the above hotfix, when deserialising a complex object
involving circular references I get the following exception:

System.Runtime.Serialization.SerializationException: The object with ID 28
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)

If I remove the hotfix, the same code works again. Any ideas? Where should I
go to report this kind of bug? I tried ringing Microsoft, but it seemed to be
over the head of the person I spoke to.
Click to expand...
Click to expand...
 
Typical MS 'thinking'. Why would anyone think to report a bug to a page
that says it's the place to report bugs ?
If you think you have found a bug in a Microsoft product, contact our Microsoft Product
Support Services department.
Click to expand...

Should read -
If you think you have found a bug in a Microsoft product, contact our Microsoft Product
Support Services department.
But don't expect anyone to know what you're talking about. Use Google instead.
Click to expand...

Phoeey

MowGreen [MVP 2003-2007]
===============
*-343-* FDNY
Never Forgotten
===============



That link just gives you phone numbers, and when you call they direct you to
google for you answer.

After searching for a while, I came across this site:

https://connect.microsoft.com/

I think this may be the appropriate place to post bugs.

:

This appears to be where one would report bugs:
http://support.microsoft.com/gp/contactbug

Report a Microsoft Product Bug

If you think you have found a bug in a Microsoft product, contact our Microsoft Product
Support Services department.
(800) MICROSOFT (642-7676)
Click to expand...

Heck, I still can't figure out how MICROSOFT translates to 642-7676
MICROSO ? <w>

MowGreen [MVP 2003-2007]
===============
*-343-* FDNY
Never Forgotten
===============


arbitrarily wrote:

After applying the above hotfix, when deserialising a complex object
involving circular references I get the following exception:

System.Runtime.Serialization.SerializationException: The object with ID 28
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)

If I remove the hotfix, the same code works again. Any ideas? Where should I
go to report this kind of bug? I tried ringing Microsoft, but it seemed to be
over the head of the person I spoke to.
Click to expand...
Click to expand...
Click to expand...
 
Back
Top