David
Tue Mar 18 01:10:10 CDT 2008
On Mar 16, 7:00=A0pm, "Ken Schaefer" <kenREM...@THISadOpenStatic.com>
wrote:
> Hi,
>
> Assuming that your changes were propogated to the metabase (i.e. committed=
> to the on-disk copy of the metabase) then these app pools are not being
> recreated by IIS when you restart the machine - something else is recreati=
ng
> them. You can use Metabase Auditing to try to work out what.
http://www.ado=
penstatic.com/faq/IISMetabaseAuditing.aspx
>
> Cheers
> Ken
>
> "Sigitas Skublickas" <SigitasSkublic...@discussions.microsoft.com> wrote i=
n
> messagenews:3484F7DC-BCF4-45A8-9F2B-97D47AE53FA7@microsoft.com...
>
>
>
> > Hello,
>
> > I have four stale APP pools on my IIS on 2003 server. I used those pools=
> > for
> > SharePoint testing and deleted after I was done with my testing. SQL
> > Database
> > and Web Sites got deleted automatically but the app pools not. I can
> > delete
> > those pools manually, but if I reboot the server they get recreated. All=
> > pools are empty and no content is associated with any of them.
>
> > Any ideas how can I delete them for good ?
>
> > Thanks!
> > Sigitas- Hide quoted text -
>
> - Show quoted text -
After deleting the Application Pools, select "Save Configuration to
Disk..." from the IIS Manager UI at the computer node. This ensures
that the changes in memory are flushed to disk.
If after you do this, and you STILL see the Application Pools reappear
after reboot, then there is some other external process recreating
them. IIS does not have code nor the ability to modify its
configuration by default. As mentioned by Ken, Metabase Auditing can
help figure out the rogue identity.
//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//