Using FSUtil to fix a failed SharePoint 2010 upgrade – Windows Process Activation Service Error – and the Blue Comet

Etracted from the original post

We recently had to rescue a stalled SharePoint upgrade that went awry after a partial disk rebuild. During the upgrade, Central Administration refused to start, reporting the error:

Windows could not start the Windows Process Activation Service - Error 6801: Transaction support within the specified resource manager is not started or was shut down due to an error.

We traced this to the local file system journals being out of sync due to the partial restore. As result, IIS itself refused to start after reboot because the WAS wouldn’t start – and the WAS acts as the ignition for other processes, like IIS. In part, this is done to protect the data in case the file system has become corrupted. However, there’s also a simple fix. At a command line, run:

fsutil resource setautoreset true c:\

assuming the system drive is C. After a reboot, you will able to start IIS and continue with the upgrade.

For complete post click here