We are getting a serialization error and after a few hours of tracking the
"real" problem down, we found that the System.Data.dll file for the Windows
Server 2003 version of Microsoft .Net Framework 1.1 SP1 is different than
the rest of the SP1's for the other Windows operating systems. While
de-serializing a SqlError instance, an exception is raised that states that
8 members of SqlError were expected but only 7 were deserialized. I looked
at the different members of the System.Data.dll file (version 1.1.4322.2032
from our Windows Server 2000 machine) and compared it to the members of the
System.Data.dll file (version 1.1.4322.2300 from our Windows Server 2003
machine). There is, in fact, 1 extra member in the assembly on the Windows
Server 2003 than there is on the Windows Server 2000 machine. I
cross-referenced this info with what was available on the net and found at
Wikipedia the list of version information for the .Net framework and noticed
that for Microsoft .Net Framework v1.1, there were different builds for
Windows Server 2003, and the version was 1.1.4322.2300.

Is there a patch that fixes the SP1 bug introduced in the Windows Server
2003 build that would fix this issue? Framework 2.0 introduced the
OptionalFieldAttribute and when I reviewed the members of Framework 2.0's
System.Data.dll assembly, I found that they applied this attribute to the
new member...but for v1.1, no such attribute exists and the addition of the
member broke deserialization....

Thanks,
Mythran

"Mythran" <(E-Mail Removed)> wrote in message
news:B5C5CB75-82C2-48B8-8788-(E-Mail Removed)...
> We are getting a serialization error and after a few hours of tracking the
> "real" problem down, we found that the System.Data.dll file for the
> Windows Server 2003 version of Microsoft .Net Framework 1.1 SP1 is
> different than the rest of the SP1's for the other Windows operating
> systems. While de-serializing a SqlError instance, an exception is raised
> that states that 8 members of SqlError were expected but only 7 were
> deserialized. I looked at the different members of the System.Data.dll
> file (version 1.1.4322.2032 from our Windows Server 2000 machine) and
> compared it to the members of the System.Data.dll file (version
> 1.1.4322.2300 from our Windows Server 2003 machine). There is, in fact, 1
> extra member in the assembly on the Windows Server 2003 than there is on
> the Windows Server 2000 machine. I cross-referenced this info with what
> was available on the net and found at Wikipedia the list of version
> information for the .Net framework and noticed that for Microsoft .Net
> Framework v1.1, there were different builds for Windows Server 2003, and
> the version was 1.1.4322.2300.
>
> Is there a patch that fixes the SP1 bug introduced in the Windows Server
> 2003 build that would fix this issue? Framework 2.0 introduced the
> OptionalFieldAttribute and when I reviewed the members of Framework 2.0's
> System.Data.dll assembly, I found that they applied this attribute to the
> new member...but for v1.1, no such attribute exists and the addition of
> the member broke deserialization....
>
> Thanks,
> Mythran
>
>

We contacted Microsoft and found that there is indeed a patch that fixes
this particular error but you have to contact Microsoft to receive the
hotfix.



Mythran