IIS services fail to start: "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" when WAS service is started


You may see that IIS related services fail to start and receive “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” error message when you try to start the WAS (Windows Process Activation Service) service. This issue may occur if the file system transaction log is corrupted somehow. In this case run the following command in the command prompt:

fsutil resource setautoreset true c:\

PS: This assumes that the system drive is C:

Reboot is required after running the command.

Applies To:

Windows Server 2008
Windows Server 2008 R2


AMB

Comments (23)

  1. Stephen says:

    Is there any risk with this command being ran on a windows 2011 server.

  2. Hans says:

    Worked for me!

  3. Raju M says:

    Hi,

    I ran the same command in windows 7 and rebooted the machine.

    however still i am not able to run the service dinwos process activation.

    please help.

  4. Not-required says:

    Create a temp folder name "appPools" under C:/inetpub/temp

    It will start working and all required services and application pool will start.

  5. Aegis CSS says:

    This worked for me on SBS 2011. Thanks very much.

    Would be nice to know what caused it…

  6. Earl says:

    Worked for me also!! Thank you!!

  7. JWil says:

    Worked for me

    Exchange 2007/Win2k8R2

  8. Venky says:

    The command executed successfully, but still the same problem.

    Please help

  9. Kurt says:

    SBS 2011 is running again. THX for this blog.

  10. Sam says:

    Ran command on Windows 7 machine, didn't work. Didn't notice Ahmet said to restart… should have known. Worked once machine rebooted.

  11. The CodeMaster says:

    This script worked very well for me.

    Migration to virtual environment had caused it.

    Thank you very much.

  12. Jack says:

    Fixed my problem. However it ran a chkdsk that took about 30 minutes and found/fixed a lot of errors.

  13. Mercman says:

    Awesome!! Fixed my problem

  14. Flavio says:

    I did all that and a pending disk check, then it was solved.

  15. Sergey says:

    Fix my problem, but only after chkdsk was ran

  16. rock says:

    Didn't work for me

  17. Cristian Avanade says:

    Thank you so much it works for me.

  18. venky says:

    Worked for me Thanks:)

  19. I LOVE YOU says:

    THIS WORKED THANK YOU PRAISE THE LORD

  20. Ketan says:

    Thank you so much,it works for me

  21. Neha says:

    Works for me. Thanks 🙂

  22. hms1 says:

    Thanks this worked for me 🙂

    Having spent days looking for a solution I was about to give up and restore from a backup, thanks again.

  23. Ravimohan says:

    Its worked for me, Thanks A LOT 🙂