Orchestrator Run Program activity returns "Process creation failed" "The system cannot find the file specified" error

Article ID: 2748718 - View products that this article applies to.
Expand all | Collapse all

Symptoms

Executing the Run Program activity from either System Center Orchestrator results in the activity returning a failed status and the Error Summary Text Published Data contains the following error:

"Process creation failed on <computer> - The system cannot find the file specified. (code 2)"

This error will be returned even if the path to the program being executed has been confirmed to be valid on the target computer and the user account configured for the Orchestrator Runbook Service, or directly in the Security tab of the Run Program activity has been verified as a member of the local Administrators group on the target computer.

Cause

The Orchestrator Run Program Service (orunprogram) on the target computer, used to execute the configured program or command, does not have sufficient privilege to create the process in the manner required for the Run Program activity. This is typically a result of the service on the target computer that creates the process not using the LocalSystem user account.

Resolution

The service that creates the process on the target computer, Orchestrator Run Program Service (orunprogram), by default is configured to use "LocalSystem" as the logon credentials. LocalSystem has a special user right that even members of the local Administrators do not have by default, which is "Act as part of the operating system". This user right allows the user to create a process using the credentials of another user which is required for the Run Program activity to succeed.

Act as part of the operating system
http://technet.microsoft.com/en-us/library/cc976442.aspx

There are three resolution options available:


Resolution #1

Stop and delete the Orchestrator Run Program Service (orunprogram) from the target computer allowing System Center 2012 Orchestrator to reinstall the service automatically using the default LocalSystem user account at next execution of the Run Program activity.

Execute the following commands using an elevated Command Prompt on the computer that is the target of the Run Program activity to stop and delete the Orchestrator Run Program (orunprogram) service:

sc stop orunprogram
sc delete orunprogram

Resolution #2

Stop the Orchestrator Run Program Service (orunprogram) on the target computer and configure the service to use the LocalSystem account to logon, then restart it.

Execute the following commands using an elevated Command Prompt on the computer that is the target of the Run Program activity to stop the Orchestrator Run Program (orunprogram) service, change the user account to LocalSystem and then restart it:

sc stop orunprogram
sc config orunprogram obj= LocalSystem type= interact type= own
sc start orunprogram

Resolution #3 (Not Recommended for security reasons)

Grant the user account that is specified as the logon user for the Orchestrator Run Program Service (orunprogram) the "Act as part of the operating system" user right.


Note This is a "FAST PUBLISH" article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use for other considerations.

Properties

Article ID: 2748718 - Last Review: August 27, 2012 - Revision: 3.0
Applies to
  • Microsoft System Center 2012 Orchestrator
Keywords: 
KB2748718

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com