Create process failed. Return code: 1314

I have 24x7 running as a Windows Service. There are instances when I need to manually run jobs using the Run Now command, but it has never worked. These jobs are created via the Job Properties Wizard.

Typically, the Run Now feature is disabled when 24x7 is running as a Window Service. In order to use it, I need to disable the Windows Service first. Upon disabling it, I launch the 24x7 Windows console and select the job I want run manually. I hit Run Now and a dialog titled, Run Now appears. I press the Normal button and a dialog with rotating cogwheels appears indicating to me that the job is running. However, there were no results afterward.

On the next attempt, I try the Test Mode. An error dialog appears with the following text:

An error occurred while executing ""(application path)"" Continue testing this job?

I press Yes. Again, there were no results produced by the application.

As the error message does not provide me with adequate information to resolve the issue, I reviewed the 24x7 Log Viewer which has a more elaborate explanation:

"Create process failed. Return code: 1314 - A required privilege is not held by the client"

It appears to be a COM-related error, but it would be useful to know what privileges are required by 24x7 to run jobs manually. I am running 24x7 using an account with Administrative privileges.

Has anyone encountered this error? Is there a systematic way to determine which privilege is required?

Thank you in advance.

	Code:
	the Run Now feature is disabled when 24x7 is running as a Window Service

This is not the case. Think of the following analogy.. you open a file in Notepad (that Notepad is run as a service and counted as instance 1), then you open another Notepad instance and want to use it to edit the same file that you have already opened in the Notepad service instance, and you want your changes in the second Notepad instance to be live in the first instance. Obviously, it is not going to work this way. Each Notepad instance is independent process. Same story is with 24x7. When you have it run as a service (instance 1) and then you open another instance in GUI mode (instance 2), you cannot have that second instance to run jobs or make changes in the service.

There are 2 solutions for this situation.
1. Run 24x7 Scheduler (service) in server mode and use 24x7 Remote Control (this is a remote client) to remotely connect to the scheduler service, and manage and run jobs as required. In this case the 24x7 Remote Console behaves like a fat database client, stuff that you see on your screen in 24x7 Remote Control is actually changed and executed on the server.
2. You can also use the 24x7 Web-based Management Console. Same thing here, this provides thin client, you only need a web browser to connect to 24x7 server via a web server and manage and run jobs.

More info on both interfaces is available in the documentation installed with the software.

Hope this helps.

Thank you for the explanation. It's obvious when I observe the 24x7 processes under Process Explorer. When 24x7 is running as a service, the job execution engine is running under 24x7srv.exe in the System userspace. In contrast, the GUI instance is running independently under my userspace. Therefore, it doesn't have access to the job execution engine. So, Run Now isn't technically disabled but irrelevant.

I'm trying out the 24x7 Remote Control client, but I'm having issues with it.

Here is my procedure:

On the Remote Host
1. Configure the 24x7's Service mode to "Remote Agent"
2. Restart Windows

On the Client
1. Launch 24x7 Scheduler (Remote Control)
2. Create a new profile to point to the server (Async Operations and Trace Enabled are not checked)
3. Attach to Remote Host
4. Authenticate with admin privileges
5. Nothing appears

Agent is not what you want. Agent is used for running remote jobs.

Here is what you need:
1. On the server, start 24x7 in GUI mode, make sure the service is not running. Click Tools/Options menu; Network tab on the Options dialog. "Distributed server mode "option enabled. Restart the scheduler as service (or in GUI mode, this doesn't actually matter)
2. On your workstation, start 24x7 Remote Control. When prompted for the connection, select an existing profile or click New and add a new profile for the server.
3. Click Connect. That's it. The rest should be more or less obvious.

Just in case, the server and remote control must be installed using different license keys or using a site license.

Last edited by SysOp on Wed Nov 05, 2008 11:20 pm; edited 1 time in total

Thank you very much! It works like a charm.

You are welcome

Just out of curiosity...

I have been using Remote Control on my local client, but I also have Remote Control installed on the server.

Would it be possible to use Remote Control on the server to Run Jobs via the 24x7 job engine instance running beneath the Windows Service?

I am thinking of creating a profile configured with the hostname, "localhost"

This is technically possible, but not recommended. Running the console on the same machine where you got the server may cause them to interfere with each other because they would be using shared files and because of potential job anomalies when running/debugging them locally in the console. In case you want to manage everything on the server, please consider using the 24x7 Web-based management console, instead of the GUI (e.g. 24x7 Remote Control running on the same system).