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: LocalSystemAccount.
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?