They are currently running as the Local System, but that's the only way we were able to get it to work.
The errors were being thrown when I had it set as Network Service, Local Service, or a specific domain AD user account.
After each change, I'd recycle the app pool, reset IIS, and then, to be very specific, recycle the app pool.
-AC
----- Ken Schaefer wrote: -----
Please go into IIS Manager, expand the Application Pools node, and locate
the MSSharePointAppPool. What is the process identity for it?
Cheers
Ken
"AC" <anonymous.DeleteThis@discussions.microsoft.com> wrote in message
news:8CD460D1-FDE5-40FC-BA4F-713CA7DDAA48@microsoft.com...
: The message we see in the browser is "Service Unavailable"... nothing
else.
:
: The exact errors we're getting:
: Event Type: Error
: Event Source: W3SVC
: Event Category: None
: Event ID: 1002
: Date: 4/27/2004
: Time: 4:36:23 PM
: User: N/A
: Computer: XXXXXXXX
: Description:
: Application pool 'CentralAdminAppPool' is being automatically disabled due
to a series of failures in the process(es) serving that application pool.
:
: For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
:
: AND
:
: Event Type: Warning
: Event Source: W3SVC
: Event Category: None
: Event ID: 1021
: Date: 4/27/2004
: Time: 4:38:32 PM
: User: N/A
: Computer: XXXXXXXXX
: Description:
: The identity of application pool, 'MSSharePointPortalAppPool' 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
http://go.microsoft.com/fwlink/events.asp.
:
: We can't tell anything happened on the site at all. >> Stay informed about: AppPool keeps dying