Windows Process Activation Service stops running unexpectedly in Windows Server 2008

Download hotfix to resolve this issue
Click here to download Hotfix

Symptoms

Consider the following scenario:

• You have a server that is running Windows Server 2008.
• You have Internet Information Services (IIS) 7.0 installed on the server.

In this scenario, the Svchost.exe process of Windows Process Activation Service (WAS) stops running unexpectedly.

Because the World Wide Web Publishing Service (W3SVC) depends on WAS, these services and your web application stop. Additionally, the following events are logged in the Application and System event logs:

Log Name: Application
Source: Application Error

Event ID: 1000
Level: Error
Description:
Faulting application name: svchost.exe_WAS, version: 6.0.6001.18000, time stamp: 0x47919291
Faulting module name: nativerd.dll, version: 7.0.6002.18139, time stamp: 0x4af812b4
Exception code: 0xc0000005
Fault offset: 0x000000000000e49f
Faulting process id: 0xf08
Faulting application start time: 0x01cebeec8563f730
Faulting application path: %11
Faulting module path: %12
Report Id: %13Log Name: System
Source: Service Control Manager

Event ID: 7034
Level: Error
Description:
The World Wide Web Publishing Service service terminated unexpectedly. It has done this 1 time(s).

Note This problem does not occur on a server that is running Windows Server 2008 R2 and has IIS 7.5 installed.

Cause

When this problem occurs, the Windows Process Activation Service refers to the null pointer during configuration changes. This causes the Svchost.exe process to crash and the websites to restart.

 

Resolution

Hotfix information:

A supported hotfix is available from Microsoft Support. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.