Can PipeLine mode and pool identifier affect an application that works with integrated security?

Question

My application is built on ASP.NET 2.0 and is hosted on a dedicated server running Windows Server 2008 R2.

Since the last few days, my users have complained that the application starts to work incorrectly by selecting previous SQL Server connection values. GridView starts displaying DropDown control options, etc. When I restart the SQL Server background service, everything starts working fine. I had a lot of discussions with people, and some of them suggested that this has something to do with the application pool.

I looked at IIS properties to find out which application pool my application is running in. I found that my application uses the Classic Application Pool with the Managed Pipeline Mode set to: Classic . The application also works with Application Pool Identifier : LocalSystemAccount .

In the database connection line (in the web.config file) I use the server name as LocalHost with built-in Security=SSPI .

I want to know if the above settings have anything to do with this malfunction.

Do I need to change Pipeline mode to Integrated and put the application in a separate pool? Integrated Security=SSPI has anything to do with PipeLine Mode ?

Answer 1

Re: Are the parameters of the pipeline mode and integrated safety related: No.

Pipeline mode indicates how IIS requests are processed. A classic is essentially an IIS6 model, with ASP.NET code running through ISAPI. Integrated porting of ASP.NET to the main pipeline in the new model for IIS 7.

Integrated Security is the authentication definition that an application represents SQL when it connects. SSPI I believe that you will use credentials for the add process to the application. Since you are using LocalSystemAccount, this will be the local system. This could probably be a problem if the instance of SQL Server was on a separate machine, but if it is localhost, I would assume that it would be trusted.

As for the root of the erroneous behavior ... I have no answer. The application pool could get into a frozen state, but I do not think that this state is related to the pipeline mode.