A is e domain controller with active directory
B is a server of domain where is installed IIS 6.0
I Would like to start an application pool over a WebSite of B with an
identity of domain and not as "Network Service"
So, I created an user on active directory ( _usrsvc ) that's member of
Administrator of domain, of Domain Admins, of Domain Users and of
IIS_WPG, but when I start up the website I receive this message in
event viewer :
"The identity of application pool 'SmartAppPool' 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."
What permission user of domain must have to start application pool?!
Thank and sorry for my English ;)
--
//David
IIS
http://blogs.msdn.com/David.Wang
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"Davide" <18277i...@mynewsgate.net> wrote in message
news:200508050...@mynewsgate.net...
--
Paul Williams
Microsoft MVP - Windows Server - Directory Services
http://www.msresource.net | http://forums.msresource.net
- Replace a Process Level Token (SeAssignPrimaryTokenPrivilege)
- Adjust Memory Quotas for a process (SeIncreaseQuotaPrivilege)
- Generate Security Audits (SeAuditPrivilege)
- Bypass Traverse Checking (SeChangeNotifyPrivilege)
- Access this computer from a network (SeNetworkLogonRight)
- Logon as a Batch Job (SeBatchLogonRight)
- Logon as a Service (SeInteractiveLogonRight)
- Allow Logon Locally (SeInteractiveLogonRight)
(those are the rights that Network Service has by default, so that should be
enough for a custom account)
Cheers
Ken
--
IIS Blog: www.adopenstatic.com/cs/blogs/ken/
Web: www.adopenstatic.com
"Paul Williams [MVP]" <ptw...@hotmail.com> wrote in message
news:exqofVam...@TK2MSFTNGP10.phx.gbl...
: Cross-posting into the IIS group for additional help...
:
:
:
:
Please ensure that your domain user's resultant privileges actually matches
the privileges for "Network Service".
Just about all of the causes of this issue that I have seen are caused by
either:
1. you have a locked-down group policy coming from somewhere in the domain
2. you tweaks privileges/local policy on the machine
--
//David
IIS
http://blogs.msdn.com/David.Wang
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"John Bailey" <JohnB...@discussions.microsoft.com> wrote in message
news:52CDF1B2-218F-4BC8...@microsoft.com...