WinRM hosted in IIS fails to start with error 1300 in event log

  • Article

WinRM is hosted within IIS by enabling the WinRM native module at a particular IIS site, app or a vdir. IIS sites and apps can be configured to run in a specific application pool. Each application pool runs under a specific user context. WinRM will fail to start when the user associated with the application pool does not have the required privileges.

When this happens, the following event shows up in the event log:

The WinRM service is unable to start because of a failure during initialization.

 Additional Data
The error code is 1300.

 To fix this, do the following:

  • Open secpol.msc
  • Navigate to Local Policies -- User Rights Assignment
  • Select the value "Generate Security Audits"
  • Add the user account to the list

Comments

  • Anonymous
    February 26, 2010
    Might try creating a group and adding that as this may come up for more than one user.

  • Anonymous
    March 29, 2010
    I have the following problem with WinRm on Windows 7: http://social.msdn.microsoft.com/Forums/en-US/netfxremoting/thread/ad02461a-878c-49a9-bc08-a0199d69b85c Maybe you know the reason & solution. Would be great. Thanks in advance.

  • Anonymous
    June 17, 2010
    Thanks so much, I've been struggling with this for days!  Alternatively, in a domain environment, you could create a service account, define this account for winrm in a GPO, and define this for the service in that GPO.

  • Anonymous
    August 19, 2012
    Thanks!  This worked for me.

  • Anonymous
    January 15, 2013
    Thanks that worked for me too.