I have opened this bug report on Connect and am curious as to if anyone else has run into this issue as well. If you have, please vote it up – it appears there isn’t much about this issue that I can find online. Some users report a fault in a .NET module while others, like me, notice the behavior below. Text of bug report follows.
When attempting to use “Run Program” against Windows 2003 Server the run book immediately fails.
From the Runbook Tester, you’ll receive an immediate error of “Could not start the Orchastrator Run Program Service service on <server> – The service did not respond to to the start or control request in a timely fashion”From the side of the server, event viewer states that “Timeout (30000 milliseconds) waiting for the Orchestrator Run Program Service service to connect”
Based on those errors, and the additional information obtained from http://social.technet.microsoft.com/Forums/en-US/scogeneral/thread/0a120a12-8514-44cf-991a-cd6d86da28a9
and
http://social.technet.microsoft.com/Forums/en-US/scogeneral/thread/ebf059ac-44cc-43b7-82d1-fbc03b063e7eAdditionally, slightly before that event, this occurred for the same user:
Description:
Windows saved user <DOMAIN\SCORCHACCT> registry while an application or service was still using the registry during log off. The memory used by the user’s registry has not been freed. The registry will be unloaded when it is no longer in use.
This is often caused by services running as a user account, try configuring the services to run in either the LocalService or NetworkService account.and this is from the Audit log when the SCO account attempted to access the remote server
Special privileges assigned to new logon:
User Name: uname
Domain: dom
Logon ID: (0×0,0xC4FE95)
Privileges: SeSecurityPrivilege
SeBackupPrivilege
SeRestorePrivilege
SeTakeOwnershipPrivilege
SeSystemEnvironmentPrivilege
SeLoadDriverPrivilege
SeImpersonatePrivilegeIt appears that the application seems to be faulting with the communication with the server somewhere along the line. The above forum posts list a possible, fault, but I am unable to even get it that far.
This has been tested on both Windows 2003 Enterprise Server (32-bit) and Windows 2003 Standard Server (64bit) and the exact same issues appear for both.