Well, since w3wp.exe handles the application pool for IIS, and since you're running your server as a DC - I'd have one initial question: is this your main DC for your domain or is it just one of several. In general it's ill-advised to run IIS (at least for anything other than web-management or something interal and small) on your main Domain Controller. However, I leave that up to you (maybe you have a small infrastructure and are trying to make one machine to everything... I've been there before).
There are a huge variety of reasons that the problem could occur - but most common is either a conflict with two separate applications trying to control the same application pool. Secondarily there could simply be a serious problem with an application running - maybe you have an ASP.NET application that's doing something 'fishy'. If nothing else I'd just make sure that if you have multiple IIS sites (or a website and SharePoint, etc..) that each has a separately named application pool. This will result in multiple instances of w3wp.exe - each with a separate process ID. Once that is the case you can easily pinpoint exactly which pool is having a bucket failure.
NOTE: running multiple pools will increase the utilization of the machine - especially RAM since w3wp.exe does some resource allocation as needed. Make sure it's not just a starvation issue and that you have plenty of unallocated RAM prior to diverging your pools.
Perhaps some more information would help narrow it down. What IIS apps are you running? Is SharePoint installed? Have you installed all latest hotfixes (post SP2 fixes)? etc.. The more information the better!
Main Topics
Browse All Topics
by: MrHusyPosted on 2007-07-02 at 14:52:40ID: 19407220
Hi gawilley
I hope this helps
http://support.microsoft.c
Regards