IIS 6.0 is being ran on a Windows Server 2003 Domain Controller machine. A problem was sent my way to fix. The problem is as follows.
The w3wp.exe worker process would crash after a machine reboot. I reproduced the error (see below) 6 times. I then changed the Identity of the default application pool to Local_System from Network_Service. I then rebooted. The error did not appear. I reboot about 5 times and there was still no error appearing visually or in the event log. I then set the application pool identity back to Network_Service and rebooted. However, the error did not appear. I rebooted another 5 times and the error would still not occur, and I can't get it to reoccur. What I am wondering is did the application pool need higher privliges to do something it only had to do once? And since it was able to do it once when I gave it higher privliged identity setting it back down would not have reproduced the error? Is anyone aware of anything that it may have only had to do once?
Beyond just that, any ideas on why the described events occured the way they did?
Lastly, once the error occured it did not keep reoccuring during the same session, meaning I had no problem starting ASP.NET web applications or ASP apps, and they all ran fine. This error only occured on startup.
Oh, and at the moment I do not have the ability to install IIS Diags or IIS State.
Any ideas / help would be appreciated.
The following is the generic crash error logged in the Application Event Log:
Event Source:Application Error
Reporting queued error: faulting application w3wp.exe, version 6.0.3790.1830, faulting module unknown, version 0.0.0.0, fault address 0x001f0001.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp