Application Pool shutting down

22
votes

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?

3
iisapplication-pool
Changing to a different identity keeps the app pools running. I would still like to know how to reset the profiles that the app pool is intended to run under – Dennis Burton

3 Answers

44
votes

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).

0
votes

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:

  • Take a zip of C:\Users\Default from a Windows 10 installation that doesn't have this problem
  • Rename C:\Users\Default on the Windows 10 install that is having problems, to Default.Old
  • Unzip the non-corrupt Default profile into C:\Users

Now try again with Load User Profile set to True. It should work.

0
votes

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.