Hi,
I administer 3 seperate environments of IIS using the same code (different areas of development). They are all hosted on 2003 SP2 servers and each environment cosists of a DC, SQL Server, 3x IIS Servers. The App Pools are using a Domain Account which password does not expire.
Infrequently the errors occur in the environments which can stop the site.
Event Type: Warning
Event Source: W3SVC
Event Category: None
Event ID: 1057
Date: 10/12/2008
Time: 13:41:00
User: N/A
Computer: Computer1
Description:
The identity of application pool 'AppPool' 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/fw
Event Type: Error
Event Source: W3SVC
Event Category: None
Event ID: 1059
Date: 10/12/2008
Time: 13:41:00
User: N/A
Computer: Computer1
Description:
A failure was encountered while launching the process serving application pool 'AppPool'. The application pool has been disabled.
For more information, see Help and Support Center at http://go.microsoft.com/fw
Event Type: Failure Audit
Event Source: Security
Event Category: Logon/Logoff
Event ID: 537
Date: 05/12/2008
Time: 05:04:45
User: NT AUTHORITY\SYSTEM
Computer: Computer1
Description:
Logon Failure:
Reason: An error occurred during logon
User Name: svcAccount
Domain: Domain
Logon Type: 4
Logon Process: Advapi
Authentication Package: Negotiate
Workstation Name: Computer1
Status code: 0xC000005E
Substatus code: 0x0
Caller User Name: Computer1$
Caller Domain: Domain
Caller Logon ID: (0x0,0x3E7)
Caller Process ID: 1940
Transited Services: -
Source Network Address: -
Source Port: -
For more information, see Help and Support Center at http://go.microsoft.com/fw
I've done a fair bit of research in to this and it seems reasonably common and I've tried the following:
Reset Account Password on the DC & IIS - didn't fix the issue
Enabling the domain account in 'Act as Part of OS' - didn't fix the issue
Added Account to IIS_WPG user group - didn't fix the issue
I've read deleting the account and creating another may fix this but I've also been told this is just a bug in IIS6.
Are there any other suggestions on this issue or proof this is a bug as I've not found MS declaring this.
Thanks
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
After a bit more investigation I think I've found the problem.....not sure how I missed it before.
Looks like the severs had hotfixes applied in the domain and then all rebooted at the same time so the DC wasn't up to authenticate the user ID and flagged it as invalid.
I'll get the reboot schedule changed first and if the problem still persists I'll look further at the App Pool as suggested.
Business Accounts
Answer for Membership
by: crokeefe28Posted on 2009-02-26 at 08:27:27ID: 23746382
First and foremost...in IIS 6 there is no real benefit in running the application pool under a domain service account. The NETWORK SERVICE or ISR account is just fine and has less of a chance in having permissions to network resources than a domain account. If you need access to resources in the application, such as a network share, this can be setup in the IDENTITY Element within the web.config and then encrypted so no one can see it. In IIS 7, this has changed and Application Service accounts are then ultilized. I would delete and recreate the App Pool using the NETWORK SERVICE account (default in Application Isolation Mode for IIS6)