Share via

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

  • 06/21/2011

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

  • Anonymous
    December 29, 2011
    Is there any risk with this command being ran on a windows 2011 server.

  • Anonymous
    January 01, 2012
    Worked for me!

  • Anonymous
    April 13, 2012
    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.

  • Anonymous
    October 14, 2013
    Create a temp folder name "appPools" under C:/inetpub/tempIt will start working and all required services and application pool will start.

  • Anonymous
    October 29, 2013
    This worked for me on SBS 2011. Thanks very much.Would be nice to know what caused it...

  • Anonymous
    December 04, 2013
    Worked for me also!! Thank you!!

  • Anonymous
    February 14, 2014
    Worked for meExchange 2007/Win2k8R2

  • Anonymous
    May 12, 2014
    The command executed successfully, but still the same problem.Please help

  • Anonymous
    July 08, 2014
    SBS 2011 is running again. THX for this blog.

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

  • Anonymous
    October 31, 2014
    This script worked very well for me.Migration to virtual environment had caused it.Thank you very much.

  • Anonymous
    November 12, 2014
    Fixed my problem. However it ran a chkdsk that took about 30 minutes and found/fixed a lot of errors.

  • Anonymous
    June 18, 2015
    Awesome!! Fixed my problem

  • Anonymous
    June 30, 2015
    I did all that and a pending disk check, then it was solved.

  • Anonymous
    July 08, 2015
    Fix my problem, but only after chkdsk was ran

  • Anonymous
    August 06, 2015
    Didn't work for me

  • Anonymous
    September 10, 2015
    Thank you so much it works for me.

  • Anonymous
    September 22, 2015
    Worked for me Thanks:)

  • Anonymous
    September 27, 2015
    THIS WORKED THANK YOU PRAISE THE LORD

  • Anonymous
    October 26, 2015
    Thank you so much,it works for me

  • Anonymous
    December 01, 2015
    Works for me. Thanks :)

  • Anonymous
    January 28, 2016
    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.

  • Anonymous
    February 19, 2016
    Its worked for me, Thanks A LOT :)

  • Anonymous
    September 18, 2016
    solved the issue in a second, thanks a lot

  • Anonymous
    December 13, 2016
    Thanks a ton...Could be great learning if someone could share what is the root cause...

  • Anonymous
    April 25, 2017
    Great.. Its working for me also.

  • Anonymous
    June 21, 2017
    The comment has been removed

    • Anonymous
      June 22, 2017
      @Toufeeq: Hello, is there any error or warning logged in System Event logs?

  • Anonymous
    August 03, 2017
    Work for me.Many thanks.