By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
439,978 Members | 1,373 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 439,978 IT Pros & Developers. It's quick & easy.

Application pool being disabled

P: n/a
I have 2 web servers on which I am running a .net version 2 application, both
of which I want to use an application pool with the same domain user's id and
password to tighten security. I have this working fine on one web server
(http), but keep getting the error below on the other (https). I cannot see
any difference in how I have set up the application pool, and the messages
below do not shed any light on the matter. Can you help me locate what the
issue is? Thanks. The error message follows (the link below didn't help at
all):

The identity of application pool, 'SBAApps' is invalid. If it remains
invalid when the first request for the application pool is processed, the
application pool will be disabled. The data field contains the error number.
For more information, see Help and Support Center at
The identity of application pool 'SBAApps' is invalid, so the World Wide Web
Publishing Service can not create a worker process to serve the application
pool. Therefore, the application pool has been disabled.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

May 21 '07 #1
Share this Question
Share on Google+
2 Replies


P: n/a
The account needs:
* "Log on as a service" (Local Security Settings -User Rights
Assignment)
* Membership in the "IIS_WPF" group (Computer Management -Local
Users and Groups)
* "Read & Execute", ""List Folder Contents" and "Read" permissions on
the codebase (Explorer -Properties)
* read/write access to the assigned temp area

I have also seen reference to (but never needed)
* start CGI processes: adjust memory quotas for a process and replace
a process level token
* access to the "Logon local" policy group

Watch out: the app-pool window in MMC does not auto-refresh; once an
app-pool has died it must be manually resurrected to try again.

Hope this helps; post back to let us know...

Marc
May 21 '07 #2

P: n/a
IIS_WPF should have read IIS_WPG... force of habit ;-p

Marc
May 21 '07 #3

This discussion thread is closed

Replies have been disabled for this discussion.