SYMPTOMS
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:
Unhandled Exception: System.NullReferenceException: Object reference not set to an instance of an object
Unhandled Exception: System.ArgumentOutOfRangeException: Ticks must be between DateTime.MinValue.Ticks and DateTime.MaxValue.Ticks. Parameter name: ticks
System.Runtime.Serialization.SerializationException: Possible Version mismatch. Type MyNamespace.MyInnerClassV2 has 2 members, number of members deserialized is 1
System.Runtime.Serialization.SerializationException: Wrong number of Members. Object MyNamespace.MyInnerClassV2 has 2 members, number of members deserialized is 1
System.Runtime.Serialization.SerializationException: Member name 'MyNamespace.MyInnerClassV1 v2Field' not found
System.IndexOutOfRangeException : Index was outside the bounds of the array
This problem occurs when all the following conditions are true:
- Both applications use either Microsoft .NET Framework remoting or runtime serialization.
- Data transfer flows from the .NET Framework 2.0 to the .NET Framework 1.1.
This data transfer may occur in any one of the following scenarios:- A .NET Framework 2.0 server returns data to a .NET Framework 1.1 client.
- A .NET Framework 2.0 client sends data to invoke a .NET Framework 1.1 service.
- Data is serialized on the .NET Framework 2.0, and data is deserialized on the .NET Framework 1.1.
RESOLUTION
Hotfix information
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it 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 Microsoft .NET Framework 1.1 service pack that contains this hotfix.
To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:
Note 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.
Prerequisites
You must have the .NET Framework 1.1 Service Pack 1 (SP1) installed to apply this hotfix.
Restart information
You must restart the computer after you apply this hotfix.
Hotfix file information
This 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
|
| Corperfmonext.dll | 1.1.4322.2359 | 81,920 | 08-Dec-2005 | 00:06 | x86 |
| Ddpatch.hotfixexefile | 1.0.0.1 | 53,248 | 17-Jun-2005 | 16:45 | Not Applicable |
| Ddpatch.updategacfile | 1.1.4318.0 | 81,920 | 18-May-2005 | 19:07 | Not Applicable |
| Ddpatch.updateutilfile | 1.0.3705.3 | 147,456 | 17-Jun-2005 | 16:45 | Not Applicable |
| M911205.unpatchfile | Not Applicable | 7,744,000 | 08-Dec-2005 | 19:25 | Not Applicable |
| Mscorlib.dll | 1.1.4322.2359 | 2,142,208 | 07-Dec-2005 | 23:59 | x86 |
| Mscorlib.ldo | Not Applicable | 10,944 | 08-Dec-2005 | 00:00 | Not Applicable |
| Mscorsvr.dll | 1.1.4322.2359 | 2,519,040 | 08-Dec-2005 | 00:05 | x86 |
| Mscorwks.dll | 1.1.4322.2359 | 2,510,848 | 08-Dec-2005 | 00:06 | x86 |
Microsoft Windows Server 2003 hotfix for x86
|
| Corperfmonext.dll | 1.1.4322.2359 | 81,920 | 09-Dec-2005 | 02:07 | x86 | SP1 |
| Mscorlib.dll | 1.1.4322.2359 | 2,142,208 | 09-Dec-2005 | 00:40 | x86 | SP1 |
| Mscorlib.ldo | Not Applicable | 10,944 | 09-Dec-2005 | 05:58 | Not Applicable | SP1 |
| Mscorsvr.dll | 1.1.4322.2359 | 2,519,040 | 09-Dec-2005 | 02:08 | x86 | SP1 |
| Mscorwks.dll | 1.1.4322.2359 | 2,510,848 | 09-Dec-2005 | 02:08 | x86 | SP1 |
| Netfxupdate.exe | 1.0.3705.0 | 106,496 | 30-Aug-2005 | 00:02 | x86 | SP1 |
| Setregni.exe | 1.1.4322.2034 | 106,496 | 30-Aug-2005 | 00:02 | x86 | SP1 |
| Togac.exe | 1.1.4322.573 | 118,784 | 09-Dec-2005 | 02:07 | x86 | SP1 |
Note Because of file dependencies, the most recent hotfix that contains these files may also contain additional files.