DetailPage-MSS-KB

Microsoft small business knowledge base

Article ID: 2733944 - Last Review: August 17, 2012 - Revision: 6.0

Hotfix Download Available
View and request hotfix downloads
 

On This Page

Summary

This article describes hotfix rollup 2733944 for the Microsoft .NET Framework 4. This hotfix rollup provides fixes for stability, reliability, and performance issues in the .NET Framework 4.

This hotfix rollup is available for the following operating systems:
  • Windows XP Service Pack 3 (SP3)
  • Windows Server 2003 Service Pack 2 (SP2)
  • Windows Vista Service Pack 2 (SP2)
  • Windows Server 2008 Service Pack 2 (SP2)
  • Windows 7
  • Windows 7 Service Pack 1 (SP1)
  • Windows Server 2008 R2
  • Windows Server 2008 R2 Service Pack 1 (SP1)

Issues that are fixed

Issue 1

When you use System.Messaging namespaces in the .NET Framework 4, you may encounter the following scenarios:
  • If there is an outstanding asynchronous MessageQueue.BeginReceive method, and if the queue is deleted out from under the request, the application may crash because of an unhandled exception.

    After you apply this hotfix, a MessageQueueException that has the MessageQueueErrorCode property set to 0x8007002 may be raised by the MessageQueue.EndReceive method. If this problem occurs, the exception should be handled by the application.

  • Under heavy load, the finalizer for the following classes may throw a System.NullReferenceException exception:
    • MessageEnumerator
    • MessageQueueEnumerator
    • Cursor
    • SecurityContext

Issue 2

Consider the following scenario. In the .NET Framework 4.0, Windows Communication Foundation (WCF) closes the response stream when the server returns an HTTP status code of 400, 404, 415, 503, or 504. In this scenario, a System.ObjectDisposedException exception is thrown when the response body is accessed.

To prevent the response from being closed, add the following configuration to the application's Web.config file after you apply this hotfix:
<configuration>
   <appSettings>
      <add key="wcf:HttpTransport:DoNotCloseResponseOnError" value="true" />
   </appSettings>
</configuration>

Note After HttpWebResponse is accessed, the Close method should be called to free any held resources.

Issue 3

When you call the DateTime.Parse method in a .NET Framework 4-based application, some strings may be rejected by the method. However, the DateTime.Parse method correctly parses the string in .NET Framework 3.5-based applications.

The fix introduces a new compatibility flag, DateTime_NetFX35ParseMode. This can be set either in the registry as an environment variable or in an application's App.config file. When the environment variable is set to True, the .NET Framework 3.5 behavior is used for mapping an abbreviated name to a type instead of the .NET Framework 4 behavior. This lets the date be parsed successfully.

You can add the new flag under the "runtime" element in your configuration file. The following example shows how to specify .NET Framework 3.5 parsing behavior when you run a .NET Framework 4.0-based application:
<configuration>
   <runtime>
      <DateTime_NetFX35ParseMode enabled="true" />
   </runtime>
</configuration>

Note This issue is most likely to occur in locales that have the same abbreviation for a month name and a day name.

Issue 4

An application that is created by using Microsoft .NET Framework 4 may crash under a heavy load, and the following exception occurs:
Exception type: System.InvalidOperationException
Message: Hashtable insert failed. Load factor too high

Note The exception occurs near the top of the following call stack:
  • System.Xml.Serialization.DynamicAssemblies.IsTypeDynamic

Resolution

Hotfix information

A supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that is described in this article. Apply it only 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 software update that contains this hotfix.

To resolve this problem immediately, contact Microsoft Customer Support Services to obtain the hotfix. For a complete list of Microsoft Customer Support Services telephone numbers and information about support costs, visit the following Microsoft website:
http://support.microsoft.com/contactus/?ws=support (http://support.microsoft.com/contactus/?ws=support)
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 4 installed on one of the following operating systems to apply this hotfix:
  • Windows XP Service Pack 3 (SP3)
  • Windows Server 2003 Service Pack 2 (SP2)
  • Windows Vista Service Pack 2 (SP2)
  • Windows Server 2008 Service Pack 2 (SP2)
  • Windows 7
  • Windows 7 Service Pack 1 (SP1)
  • Windows Server 2008 R2
  • Windows Server 2008 R2 Service Pack 1 (SP1)

Restart information

You may have to restart the computer after you apply this hotfix if any affected files are being used when you install the hotfix. We recommend that you close all .NET Framework-based applications before you apply this hotfix to avoid having to restart the computer.

Replacement information

This hotfix does not replace a previously released hotfix.

File information

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 item in Control Panel.

For all supported x86-based systems
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Clr.dll4.0.30319.5776,730,28024-Jul-201216:09x86
Mscordacwks.dll4.0.30319.5771,143,37624-Jul-201216:09x86
Mscordbi.dll4.0.30319.577956,46424-Jul-201216:09x86
Mscorlib.dll4.0.30319.5775,201,99224-Jul-201216:09x86
Nlssorting.dll4.0.30319.57756,91224-Jul-201216:09x86
Sos.dll4.0.30319.577517,69624-Jul-201216:09x86
System.data.sqlxml.dll4.0.30319.577752,73624-Jul-201216:09x86
System.identitymodel.dll4.0.30319.577398,43224-Jul-201216:09x86
System.messaging.dll4.0.30319.577257,62424-Jul-201216:09x86
System.servicemodel.dll4.0.30319.5776,116,42424-Jul-201216:09x86
System.xml.dll4.0.30319.5772,208,33624-Jul-201216:09x86
For all supported x64-based systems
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Clr.dll4.0.30319.5776,730,28024-Jul-201216:09x86
Clr.dll4.0.30319.5779,794,62424-Jul-201216:51x64
Mscordacwks.dll4.0.30319.5771,143,37624-Jul-201216:09x86
Mscordacwks.dll4.0.30319.5771,515,60024-Jul-201216:51x64
Mscordbi.dll4.0.30319.577956,46424-Jul-201216:09x86
Mscordbi.dll4.0.30319.5771,455,17624-Jul-201216:51x64
Mscorlib.dll4.0.30319.5775,201,99224-Jul-201216:09x86
Mscorlib.dll4.0.30319.5774,971,59224-Jul-201216:51x64
Nlssorting.dll4.0.30319.57756,91224-Jul-201216:09x86
Nlssorting.dll4.0.30319.57768,17624-Jul-201216:51x64
Sos.dll4.0.30319.577517,69624-Jul-201216:09x86
Sos.dll4.0.30319.577598,59224-Jul-201216:51x64
System.data.sqlxml.dll4.0.30319.577752,73624-Jul-201216:09x86
System.identitymodel.dll4.0.30319.577398,43224-Jul-201216:09x86
System.messaging.dll4.0.30319.577257,62424-Jul-201216:09x86
System.servicemodel.dll4.0.30319.5776,116,42424-Jul-201216:09x86
System.xml.dll4.0.30319.5772,208,33624-Jul-201216:09x86
For all supported IA-64-based systems
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Clr.dll4.0.30319.5776,730,28024-Jul-201216:09x86
Clr.dll4.0.30319.57719,375,68024-Jul-201217:44IA-64
Mscordacwks.dll4.0.30319.5771,143,37624-Jul-201216:09x86
Mscordacwks.dll4.0.30319.5773,759,18424-Jul-201217:44IA-64
Mscordbi.dll4.0.30319.577956,46424-Jul-201216:09x86
Mscordbi.dll4.0.30319.5773,296,32824-Jul-201217:44IA-64
Mscorlib.dll4.0.30319.5775,201,99224-Jul-201216:09x86
Mscorlib.dll4.0.30319.5774,470,34424-Jul-201217:44IA-64
Nlssorting.dll4.0.30319.57756,91224-Jul-201216:09x86
Nlssorting.dll4.0.30319.577143,92824-Jul-201217:44IA-64
Sos.dll4.0.30319.577517,69624-Jul-201216:09x86
Sos.dll4.0.30319.5771,203,77624-Jul-201217:44IA-64
System.data.sqlxml.dll4.0.30319.577752,73624-Jul-201216:09x86
System.identitymodel.dll4.0.30319.577398,43224-Jul-201216:09x86
System.messaging.dll4.0.30319.577257,62424-Jul-201216:09x86
System.servicemodel.dll4.0.30319.5776,116,42424-Jul-201216:09x86
System.xml.dll4.0.30319.5772,208,33624-Jul-201216:09x86
Note Because of file dependencies, the most recent fix that contains these files may also contain additional files.

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

References

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684  (http://support.microsoft.com/kb/824684/ ) Description of the standard terminology that is used to describe Microsoft software updates


Applies to
  • Microsoft .NET Framework 4
Keywords: 
kbqfe kbhotfixserver kbexpertiseinter kbsurveynew kbbug kbfix KB2733944
Share
Additional support options
Ask The Microsoft Small Business Support Community
Contact Microsoft Small Business Support
Find Microsoft Small Business Support Certified Partner
Find a Microsoft Store For In-Person Small Business Support