After deploying my Windows Communication Foundation service on IIS 7.5, i was getting the following error.HTTP Error 500.24 – Internal Server Error
An ASP.NET setting has been detected that does not apply in Integrated managed pipeline mode.
I tried to google it out but unable to find exact solution for this one. Later on, after researching and looking into IIS settings, I resolved the issue and here in this WCF Tutorial, you can find the steps to resolution.
1. Firstly, ensure that WCF is registered properly with IIS and ASP.NET (exact version).
For details on how to register WCF with IIS and ASP.NET?
For details on how to register WCF with IIS and ASP.NET?
2. Secondly, Open IIS and go to Advanced Settings of your website/virtual directory. In “Advance Setting” popup, change the Application Pool to “Classic .NET AppPool” and click ok.
Important thing to remember is that the Application Pool that is being used by our application should have two important settings.
a) Managed Pipeline Mode of AppPool should set to “Classic” instead of “Integrated”.
b) .NET Framework Version of AppPool should be the same we used for the WCF service.
Having these two settings, we can create and use a new AppPool for our application and we don’t need to be specific to “Classic .NET AppPool”.
Top 10 Interview Questions and Answers Series:
- Comprehensive Series of WCF Interview Questions
- Top 10 HTML5 Interview Questions
- Top 10 ASP.NET Interview Questions
- Comprehensive Series of ASP.NET Interview Questions
- Top 10 ASP.NET MVC Interview Questions
- Top 10 ASP.NET Web API Interview Questions
- Top 10 ASP.NET AJAX Interview Questions
The post An ASP.NET setting has been detected that…. appeared first on WCF Tutorial.
