This hotfix rollup is available for the following operating systems:
- Windows 7 Service Pack 1 (SP1)
- Windows Server 2008 R2 SP1
- Windows Server 2008 SP2
- Windows Vista SP2
- Windows XP SP3
- Windows Server 2003 SP2
Hotfix InformationA 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.
If the hotfix is available for download, there is a "Hotfix Download Available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.
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 website: Note The "Hotfix Download Available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
Prerequisites To apply this hotfix, you must have the .NET Framework 4.0 installed.
Restart requirementYou have to restart the computer after you apply this hotfix if any affected files are being used. We recommend that you exit all .NET Framework-based applications before you apply this hotfix.
Hotfix replacement informationThis hotfix package does not replace a previously released hotfix package.
Issue 1.NET applications that are running on single core computers may freeze in GC code.
SymptomsWhen you are using AppFabric session state provider, you may experience a failure when the SetAndReleaseItemExclusive method is called. Additionally, you may receive the following error message:
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Call stack information
[DataCacheException: ErrorCode<ERRCA0012>:SubStatus<ES0001>:Object being referred to is not locked by any client.]
Microsoft.ApplicationServer.Caching.DataCache.ThrowException(ResponseBody respBody) +336
(String key, Object value, DataCacheLockHandle lockHandle, TimeSpan timeout, DataCacheTag tags, String region) +244
(String key, Object value, DataCacheLockHandle lockHandle, TimeSpan timeout) +136
(HttpContext context, String id, SessionStateStoreData item, Object lockId, Boolean newItem) +1381
System.Web.SessionState.SessionStateModule.OnReleaseState(Object source, EventArgs eventArgs) +929
System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +266
SymptomsConsider the following scenario:
- You use the BinaryMessageEncoder class to serialize a typed dataset object between a .NET Framework 4.0-based Windows Communication Foundation (WCF) client application and a WCF server on a computer that is running Windows 7 or Windows Server 2008 R2.
- You request a dataset from the WCF service, and then you change the dataset in the WCF client.
- You pass the dataset back to the WCF service.
Message: Key cannot be null.
Parameter name: key
TargerSite: System.Object get_Item(System.Object)
Issue 4DirectorySearcher.FindOne() may throw overflow exceptions when it runs as a 32-bit process that is linked with the LARGEADDRESSAWARE compiler flag and runs on a 64-bit operating system that is configured to use 3 gigabytes (GB) of memory. Applications hosted inside IIS may see this exception when w3wp.exe is compiled as a LARGEADDRESSAWARE application.
This fix makes sure that memory addresses greater than 2 GB are handled correctly.
SymptomsCopying formatted text from a long XPS document can take several minutes, depending on the position of the text within the document, and can cause the application to freeze.
CauseThis issue occurs because some formatting declarations require scanning the document from the beginning up to the desired selection. These declarations are rare (they come from custom elements that have a TextElementEditingBehaviorAttribute that is not marked IsTypographicOnly).
The logic has been changed in this hotfix to avoid the expensive scan when no such declarations appear in the desired selection.
Issue 6When a third-party application queries .NET performance counters either concurrently or multiple times within a few milliseconds, a divide-by-zero error may occur based on the last time performance counters were queried.
Article ID: 2926986 - Last Review: 18 Aug 2014 - Revision: 1