IIS problems on MP

[the_player12345]

Has anybody come across the problem on a MP where the IIS Services
under the application pool keep stopping? Specifically the CCM
Framework Pool and the SMS Management Point pool. The Secondary site
is running on a DC...

When I check the event log these are both relating to an invalid
identity error. I have ensured that the IWAM account is present in the
IIS_WPG domain group and have reset the password in AD users and
computers and within the IIS UI but to no avail?

Anybody any ideas ?

Thanks

Ben.

[Travis Sweat (MSFT)]

Do you have a group policy that may be changing the passwords?

Also can you check to see the logon hours for the IWAM account. In the past
people have reported that IWAM is set to never for its hours allowed to
logon. This can cause problems too

--
Travis Sweat <MSFT>
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
"the_player12345" <ben....@ntlworld.com> wrote in message
news:1116674152....@z14g2000cwz.googlegroups.com...

[Sheldon]

I've also been experiencing this for a while now and I've been able to fix it
on 2 of the 4 servers that are experiencing the issues. If the SMS Primary
Site Server is NOT a DC you'll need to make sure the IWAM account for the
secondary site is a member of the Primary's IIS_WPG. Also make sure the
Secondary server has the correct permissions on the various IIS related
folders - there is a KB on this that I don't have on hand (I'm at home). The
folders include "C:\WINDOWS\system32\inetsrv\ASP Compiled Templates",
"C:\WINDOWS\Help\iisHelp\common" and "C:\WINDOWS\IIS Temporary Compressed
Files".

Once the permissions have been set and the IISAdmin service has been
restarted (possibly restart SMS Agent Host) the problem *should* go away.

Another temporary solution until I can find more info on why I still can't
fix two DCs that are built from the same image and have the same problem is
to run IIS6 in "IIS 5 Isolation Mode".

I hope that helps as an interim fix - I'm still searching for a real solution.

None of the IWAM accounts have group policy applied to them (they're in an
OU with "block inheritance"). Passwords have been synced using adsutil.vbs
and synciwam.vbs.

- Sheldon.