Get Help:Ask a Question in our Forums|Report a Bug|More Help Resources
Last post Feb 24, 2012 11:01 AM by rpk2006
Feb 23, 2012 09:53 AM|LINK
My application is built on ASP.NET 2.0 and is hosted on a dedicated server running Windows Server 2008 R2.
From the last few days, my users are complaining that the application starts malfunctioning by picking previous SQL Server connection values. The GridView starts displaying options of a DropDown control and so on. When I restart the SQL Server background
service, everything starts working fine. I had a lot of discussion with people and few suggested that it has something to do with the Application Pool.
I looked into the IIS properties to see which application pool is running my application. I found that my application is using
Classic Application Pool with Managed Pipeline Mode set to:
Classic. The application is also running with Application Pool Identity set to
In the database connection string (in web.config file), I am using Server Name as
LocalHost with Integrated Security=SSPI.
I want to know whether the above settings have anything to do with this malfunction.
Do I need to change the Pipeline Mode to Integrated and put the application in a separate pool? Is Integrated Security=SSPI has anything to do with the PipeLine Mode?
Feb 24, 2012 09:41 AM|LINK
Try to create Pipeline to Integrated Mode and create a separate pipeline for your app!
Hope it helps u...
Feb 24, 2012 09:50 AM|LINK
When I change PipeLine Mode from Classic to Integrated, my application stop working. It gives some error of permissions. I don't remember the exact error.
How to create a separate pipeline for my application and what are the advantages?
Feb 24, 2012 09:59 AM|LINK
Sorry for the wrong name - It's Application Pool!
Try to create a separte Application Pool for your web application!
Feb 24, 2012 11:01 AM|LINK
But why it gives error when Pipeline Mode is Integrated?