Hotfix InformationA supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that this article describes. Apply it only to systems that are experiencing this specific problem.
To resolve this problem, 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: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.
PrerequisitesTo apply this hotfix, you must have the .NET Framework 4 installed on a computer that is running one of the operating systems:
- Windows 7
- Windows 7 Service Pack 1 (SP1)
- Windows Server 2003 Service Pack 2 (SP2)
- Windows Server 2008 R2
- Windows Server 2008 R2 SP1
- Windows Server 2008 SP2
- Windows Vista SP2
- Windows XP Service Pack 3 (SP3)
Restart requirementYou must restart the computer after you apply this hotfix if any affected files are being used. We recommend that you close all .NET Framework-based applications before you apply this hotfix.
Hotfix replacement informationThis hotfix package does not replace a previously released hotfix package.
Issues that this hotfix rollup resolves
Common language runtime (CLR) issues
An incorrect value is returned by the DateTime.TryParse method when you use code that resembles the following:
In this example, the incorrect output is 4:00 P.M. on today’s date.
DateTime dt = DateTime.Parse("4/21 5pm");
if (DateTime.TryParse("4/21 5pm", out dt))
After you install the hotfix, it tries to make better attempts at parsing this specific pattern.
To enable the hotfix, add the following code in the application configuration file:
Note No other date or time pattern will benefit from the hotfix.
<EnableAmPmParseAdjustment enabled=”1” />
ASP.NET issuesIssue 1
A race condition in the ASP.NET CacheManager class may cause the Internet Information Services (IIS) worker process to crash if an ASP.NET Web application creates new MemoryCache objects when CacheManager trims the cache.
This issue occurs because the ASP.NET CacheManager class might use multiple threads to read or write to a collection in a way that is not thread-safe. This causes an unhandled exception.
If an ASP.NET Web application uses output cache when the operating system adjusts the clock, it causes exceptions and causes requests to fail.
Windows Communication Foundation (WCF) issuesIssue 1
When you invoke an ASMX Web service that is hosted in IIS, the Web service fails and is intermittently inaccessible until the IIS worker process is recycled.
Note This issue typically occurs when the operating system experiences high "burst loads."
Additionally, a System.InvalidOperationException exception is thrown with the following call stack:
at System.Web.Services.Protocols.WebServiceHandlerFactory.CoreGetHandler(Type type, HttpContext context, HttpRequest request, HttpResponse response)
at System.Web.Services.Protocols.WebServiceHandlerFactory.GetHandler(HttpContext context, String verb, String url, String filePath)
at System.Web.Script.Services.ScriptHandlerFactory.GetHandler(HttpContext context, String requestType, String url, String pathTranslated)
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
Note "Method Name" represents the Web service method that you invoke.
This issue occurs because of a race condition that occurs during the resetting and the reading of the configuration in the <webServices> section.
An issue exists in the .NET Framework 4 in the way that WCF handles aborted ServiceChannel objects when they are being initialized. For example, the Abort call cannot release ServiceThrottle objects. In this case, the Abort call exhausts the throttle quota for the lifetime of the application domain. Additionally, this issue leads to fewer calls being concurrently executed in WCF even though the serviceThrottle setting allows for more. In extreme cases, all throttles can be exhausted, and the service will be unresponsive until the application domain is recycled.
Windows Presentation Foundation (WPF) issuesIssue
Assume that you try to print an XML Paper Specification (XPS) document to a Graphics Device Interface (GDI) printer on a non-English operating system. In this situation, some characters are printed incorrectly. These incorrect characters may be displayed too small or too bold, and may be lacking fine details, such as hooks at the end of long strokes. The incorrect characters typically come from a font that contains non-Latin glyphs, for example an Asian font like "MS Mincho."
ID d'article : 2803771 - Dernière mise à jour : 12 févr. 2013 - Révision : 1