Select the product you need help with
- Internet Explorer
- Windows Phone
- More products
FIX: You receive an error message when you try to transfer data between an application that runs on the .NET Framework 2.0 and an application that runs on the .NET Framework 1.1
Article ID: 907262 - View products that this article applies to.
Consider the following scenario. You have an application that runs on the Microsoft .NET Framework 2.0 and an application that runs on the Microsoft .NET Framework 1.1. You try to use Microsoft .NET Framework remoting or binary serialization to transfer data between the applications. In this scenario, you receive an error message that is similar to one of the following error messages:
Error message 1
Unhandled Exception: System.NullReferenceException: Object reference not set to an instance of an object
Error message 2
Unhandled Exception: System.ArgumentOutOfRangeException: Ticks must be between DateTime.MinValue.Ticks and DateTime.MaxValue.Ticks. Parameter name: ticks
Error message 3
System.Runtime.Serialization.SerializationException: Possible Version mismatch. Type MyNamespace.MyInnerClassV2 has 2 members, number of members deserialized is 1
Error message 4
System.Runtime.Serialization.SerializationException: Wrong number of Members. Object MyNamespace.MyInnerClassV2 has 2 members, number of members deserialized is 1
Error message 5
System.Runtime.Serialization.SerializationException: Member name 'MyNamespace.MyInnerClassV1 v2Field' not found
Error message 6
This problem occurs when all the following conditions are true:
System.IndexOutOfRangeException : Index was outside the bounds of the array
Service pack informationTo resolve this problem, obtain the latest service pack for Windows Server 2003. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/889100/ )How to obtain the latest service pack for Windows Server 2003
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.
To download this hotfix from the MSDN Code Gallery, visit the following Microsoft Web site:
Note The MSDN Code Gallery displays the languages for which the hotfix is available. If you do not see your language listed, it is because the Code Gallery resource page is not available for that language.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
PrerequisitesYou must have the .NET Framework 1.1 Service Pack 1 (SP1) installed to apply this hotfix.
Restart informationYou must restart the computer after you apply this hotfix.
Hotfix file informationThis hotfix contains only those files that are required to correct the issues in the Binary Runtime Serializer that this article lists. This hotfix may not contain all the files that you must have to fully update a product to the latest build.
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.
Global hotfix for x86
Collapse this tableExpand this table
Microsoft Windows Server 2003 hotfix for x86
Note Because of file dependencies, the most recent hotfix that contains these files may also contain additional files.
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 problem was first corrected in Windows Server 2003 Service Pack 2.