« Previous Next »

Thread: Problems with asp.net 1.1 site and classic pipeline

Last post 06-08-2009 8:01 AM by Dunlop. 4 replies.

Average Rating Rate It (5)

RSS

Page 1 of 1 (5 items)

Sort Posts:

  • 06-06-2009, 10:04 PM

    • Dunlop
    • Not Ranked
    • Joined on 06-06-2009, 9:19 PM
    • Posts 3

    Problems with asp.net 1.1 site and classic pipeline

    Hi, I am having some problems getting an asp.net 1.1 site to run under iis 7, server 2008 64bit. I am receiving the error "Request is not available in this context" which apparently can be caused by running in the context of an integrated pipeline. However this is not the case for this site. I have successfully configured asp.net 1.1 to run under IIS 7 as per instructions elsewhere on this site. I have created an application pool specific to the site, configured to use 1.1, with classic pipeline and 32bit applications enabled. The configuration is identical to another .Net 1.1 based site on the same server that I have been running without problems. In fact both sites are running on an identical code base. The working site will definitely be executing the same code as that of the failing site. While IIS reports that the application pool is configured to run in classic pipeline mode, interestingly when selecting the application pool for the site none of the .Net 1.1 pools display pipeline mode like the others. I am not sure if this matters, but it implies that perhaps the classic pipeline mode is not being applied to the .Net 1.1 pools, or it is not 'sticking' for the new pool. The applicationHost.config has all the expected values with respect to pool configuration. Also, the line at which the code is failing is not within the scope of global application start and the site runs without error on 2003/IIS6. I am at a loss as to how I can proceed at this point.
  • 06-07-2009, 6:57 PM In reply to

    • Dunlop
    • Not Ranked
    • Joined on 06-06-2009, 9:19 PM
    • Posts 3

    Re: Problems with asp.net 1.1 site and classic pipeline

    Sorry if the post above is difficult to read. The forum software didn't respect my formatting.

    After more research it appears that the other site is failing on the same code. I don't believe these sites are running within a classic pipeline despite what IIS reports, otherwise I would never receive this error.

    Clearly something has gone awry somewhere, the question is how to fix it?

  • 06-08-2009, 4:35 AM In reply to

    Re: Problems with asp.net 1.1 site and classic pipeline

  • 06-08-2009, 4:40 AM In reply to

    • lextm
    • Top 10 Contributor
    • Joined on 10-22-2008, 4:18 AM
    • Shanghai, PRC
    • Posts 1,386

    Re: Problems with asp.net 1.1 site and classic pipeline

    "Request is not available in this context" can happen in many cases, not limited to ASP.NET incompatibilities with integrated application pipeline.

    Maybe you can forget about the pipeline side and focus on your application to narrow down the problem. For example, the exception call stack can be very helpful.

    Lex Li
    Support Engineer at Microsoft
    ---------------------------
    This posting is provided "AS IS" with no warranties, and confers no rights.
  • 06-08-2009, 8:01 AM In reply to

    • Dunlop
    • Not Ranked
    • Joined on 06-06-2009, 9:19 PM
    • Posts 3

    Re: Problems with asp.net 1.1 site and classic pipeline

    Thanks for your replies. I believe I have narrowed down the problem.  The configuration of this deployment was invoking some code that accesses the Request object during the control unload event.  Presumably this means that the request object is not available at that time?

    I copied the entire site to IIS6 and have replicated the fault, so yes am I wrong about it being pipeline issue.

Page 1 of 1 (5 items)
Microsoft Communities