管道模式和池身份是否会影响使用集成安全性运行的应用程序？
我的应用程序基于 ASP.NET 2.0 构建，并托管在运行 Windows Server 2008 R2 的专用服务器上。
从最近几天开始，我的用户抱怨应用程序通过选择以前的 SQL Server 连接值开始出现故障。 GridView 开始显示 DropDown 控件的选项等。当我重新启动 SQL Server 后台服务时，一切都开始正常工作。我与人们进行了很多讨论，但很少有人认为这与应用程序池有关。
我查看了 IIS 属性以查看哪个应用程序池正在运行我的应用程序。我发现我的应用程序正在使用经典应用程序池，并将托管管道模式设置为：Classic。该应用程序还使用应用程序池标识运行：LocalSystemAccount。
在数据库连接字符串（在 web.config 文件中）中，我使用服务器名称作为带有 Integrated Security=SSPI 的 LocalHost。
我想知道上述设置是否与此故障有关。
我是否需要将管道模式更改为集成并将应用程序放在单独的池中？ Integrated Security=SSPI 与 PipeLine Mode 有关系吗？
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?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
回复：管道模式和集成安全设置是否相关：否。
管道模式指示 IIS 处理请求的方式。经典本质上是IIS6模型，ASP.NET代码通过ISAPI运行。 Integrated 将 ASP.NET 处理引入 IIS 7 新模型的主管道中。
集成安全性确定您的应用程序在建立连接时向 SQL 提供的身份验证。我相信 SSPI 意味着您将使用应用程序池进程的帐户凭据。由于您使用的是 LocalSystemAccount，因此它将是本地系统。如果 SQL Server 实例位于单独的计算机上，这可能会出现问题，但如果它是本地主机，我想它会受到信任。
至于不稳定行为的根源......我没有答案。应用程序池可能进入一种混乱的状态，但我认为该状态与管道模式无关。
Re: Are Pipeline Mode and Integrated Security setting related: No.
Pipeline Mode indicates the way that IIS handles requests. Classic is essentially the IIS6 model, with ASP.NET code running through ISAPI. Integrated brings ASP.NET processing into the main pipeline in a new model for IIS 7.
Integrated Security is determining the authentication your app presents to SQL when making a connection. SSPI I believe means that you will use the account credentials of the App Pool process. Since you are using LocalSystemAccount, it will be the Local System. This would probably present a problem if the SQL Server instance was on a separate machine, but if it is localhost I would imagine it would be trusted.
As to the root of the erratic behavior... I don't have an answer there. The app pool could be getting into a screwy state, but I don't think that state is related to pipeline mode.