Codepolice.net

We have moved one of our servers to a VPS. After crash we had to restore the VPS from a backup and when the server was restored we got a couple of strange errors with our IIS server.  The server is a Windows Server 2008 R2 and some of the errors i got where.

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

–

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

–

The Windows Process Activation Service failed to generate an application pool config file for application pool ‘*’. The error type is ’0′. To resolve this issue, please ensure that the applicationhost.config file is correct and recommit the last configuration changes made. The data field contains the error number.

–

The Windows Process Activation Service service terminated with the following error:
Transaction support within the specified resource manager is not started or was shut down due to an error.

–

Not awesome errors. Of course i tried to Google for the problem and i found lots of other people with similar errors but most of them had to do with missing or corrupt config files and none of these fixes solved my problem. Then i tried to do a Windows Update and saw that i got an error there to. I googled and those errors and found this thread in one of MS forums. It was a fix for the Window Update error with the Code 80071A91.

How-to reset the File System Resource Manager if you receive error 0x80071A91

1. Click Start, click All Programs, click Accessories, right-click Command Prompt, and select Run as administrator.
2. In the Command Prompt window you will need to type the following, and press ENTER: fsutil resource setautoreset true C:\
3. Note: You will need to replace the C:\ with the drive letter that Windows Vista is installed on.
4. Restart your computer, and then attempt to install the failed update(s).

I did as described above and to my surprise the updates did work after this. And to my even greater surprise i entered the IIS Manager and (YEY!) the sites where up an running again and the Windows Process Activation Service where started and then i lived happily ever after.