Select the product you need help with
FIX: A hotfix is available to fix two problems in ASP.NET on IIS 7.0 for Windows Vista and Windows Server 2008Article ID: 967535 - View products that this article applies to. On This PageSYMPTOMSWhen you use Internet Information Services (IIS) 7.0 in the integrated mode, you may encounter the following two problems. Problem 1When a request hits the PublishingHttpModule module, the Request.TransmitFile method does not behave correctly.Note The PublishingHttpModule module handles the authorized request and serves a cached file if a cached file is present. Problem 2When you use the System.Web.Management.WebBaseEvent.Raise method in the Application_Start event for your Web application, the WebBaseEvent.Raise method will fail. Additionally, you receive an exception error that resembles the following:Server Error in '/<Application>' Application.
-------------------------------------------------------------------------------- Request is not available in this context 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. Exception Details: System.Web.HttpException: Request is not available in this context CAUSEProblem 2 occurs because the WebBaseEvent.Raise method internally refers the Request object from HttpContext. However, because of the design changes in IIS 7.0, the HttpContext.Current.Request object will not be populated in the Application_Start event under integrated pipeline mode. Therefore, the request is not available, and the WebBaseEvent.Raise method fails. RESOLUTIONHotfix informationNote This hotfix contains a regression that affects SharePoint sites. If you plan to deploy this hotfix on a server that hosts SharePoint sites, contact Microsoft Customer Service and Support for more information.A 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. This hotfix might 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 download this hotfix from the MSDN Code Gallery, visit the following Microsoft Web site: http://code.msdn.microsoft.com/KB967535
(http://code.msdn.microsoft.com/KB967535)
Note The MSDN Code Gallery displays the languages for which the hotfix is available. If you do not see your language listed, it is because the Code Gallery resource page is not available for that language. 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 Web site: http://support.microsoft.com/contactus/?ws=support
(http://support.microsoft.com/contactus/?ws=support)
PrerequisitesYou must have the Microsoft .NET Framework 3.5 Service Pack 1 (SP1) installed to apply this hotfix. You must apply this hotfix on Windows Vista SP1 or Windows Server 2008.Restart requirementYou do not have to restart the computer after you apply this hotfix.Hotfix replacement informationThis hotfix does not replace any other hotfixes.File informationThe 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.The .NET Framework 2.0, x86-based versionCollapse this table
The .NET Framework 2.0, x64-based versionCollapse this table
The .NET Framework 2.0, IA-64-based versionCollapse this table
WORKAROUNDTo work around Problem 2, assign a dummy Request object to the HttpContext.Current.Request object. STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. MORE INFORMATIONStack output for Problem 2[HttpException (0x80004005): Request is not available in this context] System.Web.HttpContext.get_Request() +11161416 ASP.global_asax.Application_Start(Object sender, EventArgs e) +112 [HttpException (0x80004005): Request is not available in this context] System.Web.HttpApplicationFactory.EnsureAppStartCalledForIntegratedMode(HttpContext context, HttpApplication app) +4165105 System.Web.HttpApplication.RegisterEventSubscriptionsWithIIS(IntPtr appContext, HttpContext context, MethodInfo[] handlers) +205 System.Web.HttpApplication.InitSpecial(HttpApplicationState state, MethodInfo[] handlers, IntPtr appContext, HttpContext context) +336 System.Web.HttpApplicationFactory.GetSpecialApplicationInstance(IntPtr appContext, HttpContext context) +350 System.Web.Hosting.PipelineRuntime.InitializeApplication(IntPtr appContext) +382 824684
(http://support.microsoft.com/kb/824684/
)
Description of the standard terminology that is used to describe Microsoft software updatesProperties | Article Translations |
Back to the top
