Our application has an executable that runs on the server. It's on several hundred systems and works everywhere without a problem except this one place. In this one place I've had to change the defaultapppool identity from Network Service to the IWAM user. I'm wondering why? I want them to all be the same so I very much want to find out what is different with this one (Server 2003 w/iis 6). Hoping someone can give some insight.
On Feb 13, 2:02 pm, jfor...@amsworld.com wrote: > Our application has an executable that runs on the server. It's on > several hundred systems and works everywhere without a problem except > this one place. In this one place I've had to change the > defaultapppool identity from Network Service to the IWAM user. I'm > wondering why? I want them to all be the same so I very much want to > find out what is different with this one (Server 2003 w/iis 6). > Hoping someone can give some insight. This is not an issue with Application Pool Identity. Look at Global Policy restrictions on privileges held by various accounts. And compare this machine against a working machine. I bet there is some privilege missing/denied somewhere to NetworkService or is allowed to IWAM. For example, someone may have an overzealous security lockdown policy from Group Policy preventing Service logons in their domain... which inadvertently kills Network Service and IIS. Simple changes like that cause mysterious things like your situation all the time, and there is little IIS or anyone can do about it. When Domain Administrator makes a mistake in Global Policy, strange/bad things happen. //David http://w3-4u.blogspot.com http://blogs.msdn.com/David.Wang //
