This hotfix rollup package resolves an issue that is described in the "More Information" section.
Issue that this hotfix resolvesIssue
When you invoke an ASMX Web service that is hosted in Internet Information Services (IIS), the Web service fails and is intermittently inaccessible until the IIS worker process is recycled.
Note This issue typically occurs when your 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)
NoteMethod Name represents the Web service method that you invoke.
This issue occurs because of a race condition that occurs during the resetting and reading configuration of the Web services section.
After you apply this hotfix, the process that uses configuration sections to read from the Web services section of the configuration file is changed. Additionally, the hotfix prevents the race condition.
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 3.5 SP1 installed on a computer that is running Windows 7 or Windows Server 2008 R2.
Restart requirementYou must restart the computer after you install the hotfix if the affected files are being used during the installation. We recommend that you exit all applications that use the .NET Framework before you install the hotfix.
File informationThe global 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.
Article ID: 2784145 - Last Review: Dec 19, 2012 - Revision: 1