应用程序池关闭
每当我尝试启动 4.0 应用程序池中的站点时，它会立即关闭（如果它曾经启动过），事件日志中会留下一个事件：
Windows 找不到本地配置文件，并使用临时配置文件让您登录。当您注销时，您对此配置文件所做的更改将会丢失。 指定的用户是 IIS APPPOOL\DefaultAppPool，
后跟另一个事件日志条目 Windows 无法让您登录，因为无法加载您的配置文件。检查您是否已连接到网络，并且网络是否正常运行。
此计算机正在运行 Win 7 Ultimate
如果错误实际上是事件日志中指示的内容，我该如何重置应用程序池用户？
Whenever I try to launch a site in the 4.0 App Pool shuts down immediately (if it ever started) an leaves an event in the event log:
Windows cannot find the local profile and is logging you on with a temporary profile. Changes you make to this profile will be lost when you log off.
The user specified is IIS APPPOOL\DefaultAppPool
followed by another event log entry
Windows cannot log you on because your profile cannot be loaded. Check that you are connected to the network, and that your network is functioning correctly.
This machine is running Win 7 Ultimate
If the error is actually what is indicated in the event log, how can I reset the app pool users?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
我刚刚将我的 Win7 Ultimate x64 机器升级到 SP1 后遇到了这个问题。在应用程序事件日志中发现了上述消息。它伴随着它的好朋友，“由于为该应用程序池提供服务的进程中出现一系列故障，应用程序池“DefaultAppPool”被自动禁用。”在系统事件日志中。
我将应用程序池的高级设置“加载用户配置文件”从 True 更改为 False，并且我的应用程序池使用配置的身份再次运行（在我的例子中是域帐户）。
I just ran into this after upgrading my Win7 Ultimate x64 machine to SP1. The aforementioned message was found in the Application event log. It was accompanied by its good friend, "Application pool 'DefaultAppPool' is being automatically disabled due to a series of failures in the process(es) serving that application pool." in the System event log.
I changed the advanced setting of the app pool, "Load User Profile" from True to False and my app pool is running again using the configured identity (which, in my case is a domain account).
从 Windows 8 升级后，我在 Windows 10 上遇到了这个问题。问题是我的默认配置文件已损坏。 （升级到 Windows 10 时显然会发生这种情况。）
使用新用户首次登录时，将复制默认配置文件以为新用户创建配置文件。如果它损坏，可能会导致新用户登录失败。
这在 Windows 10 上对我有用：
现在，将
Load User Profile设置为True重试。它应该有效。I had this problem on Windows 10, following an upgrade from Windows 8. The problem was I had a corrupt Default profile. (This can apparently occur when upgrading to Windows 10.)
When logging in for the first time with a new user, the Default profile is copied to create the profile for the new user. If it's corrupt, this can cause the login to fail for the new user.
This worked for me on Windows 10:
Now try again with
Load User Profileset toTrue. It should work.就我而言，Windows 10 版本 1909、IIS 10、在域帐户下运行的应用程序池、应用程序池的“加载用户配置文件”或“快速失败保护”设置对问题没有影响。
当我从 IIS 中删除应用程序及其应用程序池并重新创建它们时，问题得到解决。新的应用程序池确实将“加载用户配置文件”设置为 true，就像以前一样。
In my case, Windows 10 version 1909, IIS 10, app pool running under domain account, app pool's "Load User Profile" or "Rapid-Fail Protection" settings had no effect on the issue.
When I deleted both application and it's app pool from IIS, recreated them, issue got resolved. New app pool does have Load User Profile set to true just like it was before.