"This operation requires IIS integrated pipeline mode."

Question

I have a web application being developed on Windows 8.1, .NET 4.5.1, IIS 8.5 (under Integrated AppPool), Visual Studio 2013 over the default template that includes ASP.NET Identity, Owin, etc. and locally it works fine.

Then I uploaded it to a Windows Server 2008 using IIS 7.5 (Integrated Pipeline) Host and I get:

This operation requires IIS integrated pipeline mode.

Exception Details:
System.PlatformNotSupportedException: This operation requires IIS integrated pipeline mode.

Stack Trace:

[PlatformNotSupportedException: This operation requires IIS integrated pipeline mode.]
  System.Web.HttpResponse.get_Headers() +9687046
  System.Web.HttpResponseWrapper.get_Headers() +9
  Microsoft.Owin.Host.SystemWeb.OwinCallContext.CreateEnvironment() +309
  Microsoft.Owin.Host.SystemWeb.IntegratedPipeline.IntegratedPipelineContext.GetInitialEnvironment(HttpApplication application) +246
  Microsoft.Owin.Host.SystemWeb.IntegratedPipeline.IntegratedPipelineContext.PrepareInitialContext(HttpApplication application) +15
  Microsoft.Owin.Host.SystemWeb.IntegratedPipeline.IntegratedPipelineContextStage.BeginEvent(Object sender, EventArgs e, AsyncCallback cb, Object extradata) +265
  System.Web.AsyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +285
  System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +155

I am unable to find anything except for directing the reader to change the pipeline from classic mode to integrated mode, which I already did with no success.

What can I do to fix the problem? Does "Microsoft.Owin.Host.SystemWeb" not like IIS 7.5 or something?

Is there anything else in the stack trace? No frames below HttpApplication.ExecuteStep? — Levi, Mar 10 '14 at 23:07
Nope, only footer that .net framework version number : (Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.0.30319.18067 ) — wooer, Mar 10 '14 at 23:24
:( indeed. Weird question: if you use the Empty Web Application Project template and add a single Default.aspx with the lines <%: System.Web.Hosting.HttpRuntime.UsingIntegratedPipeline %> and <%: System.Web.Hosting.HttpRuntime.IISVersion %>, what does it output on your production server? Perhaps the runtime is misidentifying the IIS mode in use. — Levi, Mar 11 '14 at 00:30
Returns False, 7.5. But it returns false what ever I set for the pipeline... I set classic it is false, I set integrated it is false too. I forwarded the problem to the host. I am waiting for a response now. — wooer, Mar 11 '14 at 07:49
The problem solved! Thanks. I suppose my host had problems with its system, since even I change the setting into classic or Integrated my app doesnt recognize it. I suppose your code helped me a lot to see it. PS: .Hosting. part is extra it shouldnt be there: <%: System.Web.HttpRuntime.UsingIntegratedPipeline %> — wooer, Mar 11 '14 at 17:27
connect the application to application pool under integreted mode f.w 4.0 — Ziv.Ti, Nov 05 '14 at 14:48
check the link below, it worked for a lot of people: http://stackoverflow.com/a/5918197/1912383 — user1912383, Feb 13 '15 at 14:17

Mohammadreza · Answer 1 · 2014-11-02T09:50:01.007

63

Your Application Pool is in classic mode but your Application need integrated mode to fire. change it to Integrated Mode:

Open IIS Manager
Application Pool
Select pool that your app are run in it
In right panel select Basic Setting
Manage Pipeline Mode change to Integrated

edited Nov 02 '14 at 09:50

answered Apr 10 '14 at 04:50

Mohammadreza

3,139
8
35
56

How do I change it if my website is published in a virtual host? – manudicri Sep 12 '19 at 15:22
it's not working for. – Neeraj Jan 04 '22 at 06:29

score 58 · Answer 2 · edited Aug 21 '19 at 21:03

58

Try using Response.AddHeader instead of Response.Headers.Add()

edited Aug 21 '19 at 21:03

TylerH

20,799
66
75
101

answered Sep 01 '14 at 17:08

billpg

3,195
3
30
57

1

This answer works if the exception was caused by adding a header. Tested with MSVS 2010 and Casinni (I think). – crokusek Sep 02 '14 at 22:41
2

Where would i find Response.AddHeader – drex drex Apr 17 '15 at 08:55
@drexdrex - Do Have a Response object? What happens if you try Response.AddHeader("X-billpg", "is so very clever."); ? – billpg Apr 17 '15 at 08:58
I dont now why where to find Response.AddHeader to change it to Response.Headers.Add(), by the way i'm using asp.net mvc5 – drex drex Apr 17 '15 at 09:05
1

I don't understand what code to change, since the stack trace in the question only shows standard MS library code. – Steve Smith Apr 28 '17 at 14:34
I was dealing with HttpContextWrapper and HttpResponseWrapper and this is the only thing that worked. – N73k Sep 01 '18 at 05:04
@billpg alternate for `Response.Headers.Remove("`...? I used your solution for `Response.Header.Add`. – Pranesh Janarthanan Nov 26 '19 at 11:26

score 32 · Answer 3 · edited Aug 21 '19 at 21:04

32

I was having the same issue and I solved it doing the following:

In Visual Studio, select "Project properties".
Select the "Web" Tab.
Select "Use Local IIS Web server".
Check "Use IIS Express"

edited Aug 21 '19 at 21:04

TylerH

20,799
66
75
101

answered May 17 '15 at 04:40

kakon

701
6
18

score 9 · Answer 4 · edited Aug 21 '19 at 21:04

9

This error means the application pool to which your deployed application belongs is not in Integrated mode.

Create a new application pool with .NET 4 version selected, and Managed Pipeline mode as Integrated.
Change your application's app pool to the above created one and try now.

edited Aug 21 '19 at 21:04

TylerH

20,799
66
75
101

answered Jul 21 '16 at 17:36

Yogitha Mahadasu

116
1
1

score 7 · Answer 5 · answered Aug 17 '14 at 22:56

7

The way to fix this issue is not within IIS. I was trying to run my application within IIS Express within Visual Studio. I searched the web and some articles were saying to add an identity tag to the system.web tag. This is not the correct way.

The way I was able to solve this issue was to click on the project file and go to properties. Under managed pipeline, I changed the property value from classic to integrated.

This solved my issue.

answered Aug 17 '14 at 22:56

Tyrone Moodley

3,442
1
15
16

1

Where exactly did you change the property? Im on VS2013 and in the project properties there is a "Web" tab but there is no "managed pipeline" property. – Mark Nov 17 '16 at 14:58
1

Found the answer to my question above here: http://stackoverflow.com/a/9023297/837507 – Mark Nov 18 '16 at 10:09
I changed properties setting from "Integrated" to "classic" and back to "Integrated", then saved the changes and things resumed working. – Zarepheth Oct 31 '18 at 16:37
Press F4 after clicking on Project Link. – abksharma Jul 05 '19 at 14:50

score 6 · Accepted Answer · edited Aug 21 '19 at 21:06

This was a strange problem since my hosts IIS shouldn't complain that it requires integrated pipeline mode when it already is in that mode as I stated in my question as:

I have searched a lot and unable to find anything except for directing the reader to change the pipeline from classic mode to integrated mode that which I already did with no luck..

Using Levi's directions, I put ~~<%: System.Web.Hosting.HttpRuntime.UsingIntegratedPipeline %>~~ and ~~<%: System.Web.Hosting.HttpRuntime.IISVersion %>~~* on an empty aspx page and told my host what going on and asked them to fix the problem and confirm the problem using the page I uploaded... I checked very often if something has changed at the state of the page and I can see that they struggled 3-4 hours to solve it...

When I asked what they have done to solve the problem, their answer was kind of 'classified', since they said:

Our team made the required changes on the server

The problem was all with my host.

* Update: As Ben stated in the comments

<%: System.Web.Hosting.HttpRuntime.UsingIntegratedPipeline %> and

<%: System.Web.Hosting.HttpRuntime.IISVersion %>

are no longer valid and they are now:

<%: System.Web.HttpRuntime.UsingIntegratedPipeline %> and

<%: System.Web.HttpRuntime.IISVersion %>

The [System.Web.Hosting](https://msdn.microsoft.com/en-us/library/system.web.hosting(v=vs.110).aspx) namespace doesn't appear to have the [HttpRuntime](https://msdn.microsoft.com/en-us/library/system.web.httpruntime(v=vs.110).aspx) class. — Ben, Oct 13 '15 at 15:18

score 4 · Answer 7 · answered Jan 23 '15 at 08:33

4

I resolved this problem by following steps:

Right click on root folder of project.
Goto properties
Click web in left menu
change current port http://localhost:####/
click create virtual directory
Save the changes (ctrl+s)
Run

may be it help you to.

answered Jan 23 '15 at 08:33

Ravi Kumar Mistry

1,063
1
13
24

Avinash · Answer 8 · 2018-07-12T13:56:47.670

4

For Visual Studio 2012 while debugging that error accrued

Website Menu -> Use IIS Express did it for me

edited Jul 12 '18 at 13:56

answered Sep 30 '15 at 09:53

Avinash

305
6
14

score 3 · Answer 9 · edited Jan 02 '16 at 17:56

3

Those who are using VS2012

Goto project > Properties > Web

Check Use Local IIS Web server

Check Use IIS Express

Project Url http://localhost:PORT/

edited Jan 02 '16 at 17:56

Serjik

10,543
8
61
70

answered Jan 02 '16 at 13:25

Techvalens

119
1
2

score 2 · Answer 10 · answered Jan 09 '19 at 15:46

2

GitHub solution solved the problem for me by adding

Global.asax.cs: Set AntiForgeryConfig.SuppressXFrameOptionsHeader = true; in Application_Start:
Manually add the X-Frame-Options header in Application_BeginRequest

answered Jan 09 '19 at 15:46

Thulasiram

8,432
8
46
54

score 1 · Answer 11 · answered Nov 12 '20 at 12:53

1

Press F4 in your Project for the property window. Then change the pipeline mode

answered Nov 12 '20 at 12:53

Eranga Ananda

43
8

Super Working Fine. Thanks :) – Thulasiram Mar 25 '21 at 06:03

"This operation requires IIS integrated pipeline mode."

This operation requires IIS integrated pipeline mode.

11 Answers11

Linked