“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 I

Answer 1

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

1. Open IIS Manager

2. Application Pool

3. Select pool that your app are run in it

4. In right panel select Basic Setting

5. Manage Pipeline Mode change to Integrated

Answer 2

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.

Answer 3

For Visual Studio 2012 while debugging that error accrued

Website Menu -> Use IIS Express did it for me

Answer 4

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

Answer 5

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

1. In Visual Studio, select "Project properties".

2. Select the "Web" Tab.

3. Select "Use Local IIS Web server".

4. Check "Use IIS Express"

Answer 6

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

1. <%: System.Web.Hosting.HttpRuntime.UsingIntegratedPipeline %> and
2. <%: System.Web.Hosting.HttpRuntime.IISVersion %>

are no longer valid and they are now:

1. <%: System.Web.HttpRuntime.UsingIntegratedPipeline %> and
2. <%: System.Web.HttpRuntime.IISVersion %>