Windows Process Activation Service error 5 – Access Denied

解决办法:C:\INETPUB\HISTORY. Under here you will see several folders with a prefix of CFGHISTORY. The folder with the highest revision number will be your latest backup. Copy this file and overwrite the existing file at C:\WINDOWS\SYSTEM32\INETSRV\CONFIG.

I ran into a strange error recently on an Exchange 2013 server. The WWW Publishing Service was stopped. When I tried to start the service it failed on a dependency. A quick check revealed the Windows Process Activation Service (WAS) was stopped. When I tried to start WAS, I received the following error.

Windows could not start the Windows Process Activation Service service on Local Computer Error 13 The data is invalid

Windows could not start the Windows Process Activation Service service on Local Computer. Error 13: The data is invalid.

The Event Viewer was littered with equally cryptic Event IDs, such as WAS 5005 and WAS 5036.

Not the first time

I’ve actually encountered an error like this before. I am not sure what causes it. But evidently, something in Internet Information Services (IIS) becomes corrupt. Thankfully this blog from GrinGod jogged my memory. It all came flooding back.

The applicationHost.config file was messed up. For me, the file was completely empty. Not a line of code to be found.

Luckily IIS takes backups that can be found in C:\INETPUB\HISTORY. Under here you will see several folders with a prefix of CFGHISTORY. The folder with the highest revision number will be your latest backup. Copy this file and overwrite the existing file at C:\WINDOWS\SYSTEM32\INETSRV\CONFIG.

applicationHost.config

Once the file has been replaced start the WAS service.

Windows Process Activation Service (WAS)

If WAS starts successfully then you should be able to start the WWW Publishing Service. If that starts successfully, then you can restore all Exchange Web Services.

I’ve got Server 2012 R2 running in Hyper-V with Exchange 2013 installed. It’s not a critical system – I’m using it to learn Exchange administration.

I went to log into the server tonight after several months of not touching it, to discover that four services are consistently failing to start no matter what I do. The World Wide Web Publishing Service error seems to be commonly caused by a the AppPools folder missing from C:\inetpub\temp\, but that is not the case for me – I’ve already checked twice.

The services are:

  • Net.Tcp Listener Adapter
  • World Wide Web Publishing Service
  • Net.Msmq Listener Adapter
  • Net.Pipe Listener Adapter

In the event log are the same four errors over and over:

Windows Process Activation Service 服务因下列错误而停止:
拒绝访问。

Windows Process Activation Service (WAS)因为遇到错误而正在停止。数据字段包含错误号。

Event ID 5036, Source WAS

The configuration manager for Windows Process Activation Service (WAS) did not initialize. The data field contains the error number.

The error number listed is 0D000780.


Event ID 5005, Source WAS

Windows Process Activation Service (WAS) is stopping because it encountered an error. The data field contains the error number.

The error number listed is 0D000780.


Event ID 7023, Source Service Control Manager

The Windows Process Activation Service service terminated with the following error:
The data is invalid.


Event ID 7001, Source Service Control Manager

The World Wide Web Publishing Service service depends on the Windows Process Activation Service service which failed to start because of the following error:
The data is invalid.

发表评论