Error running local jobs as if remote agent

Any luck?

You mean finding the place where it could be changed? No I didn't find it, I can send it back to development. in mean time I suggest using the workaround described in the previous message.

The workaround? You mean not using the web console to modify?

Hmm... I don't see one of the posting made yesterday.

Here is the workaround I was talking about.

1. in the console directory find file jobWizard/saveJob.jsp and open it in notepad
2. Search for text "// fix shared properties sensitive to schedule type". Insert the following text above this line

	Code:
	if ("LOCAL".equals(attrs.getHOST()) attrs.setHOST("");

3. Save changes

Ok, so the area now reads

String ChangeFolderErrorStr = "";
String jobID = new String(attrs.getID());
try
{
if ("LOCAL".equals(attrs.getHOST())
attrs.setHOST("");
// fix shared properties sensitive to schedule type
String recursionType = new String();
String scheduleType = new String(attrs.getSCHEDULE_TYPE());
String valueList = new String();
if ("T".equals(scheduleType))

When I try to save the offending job in the web console, i get the attached message, I can't resize the window or select the text so thats all I can see

Closing parenthesis is missing in the first line, there should 3 at the end of the line.

	Code:
	if ("LOCAL".equals(attrs.getHOST()))

Ok, adding the bracket makes it compile ok but that doesn't change the behaviour of the job. It still fails on run with
26/07/2007 12:13:56 2 222 0 Run log parser Failed to execute remote job. Agent LOCAL connection refused.

I've restarted the service, changed the job in the web console to least busy and back to local.

Please try changing this line to

	Code:
	if ("LOCAL".equalsIgnoreCase(attrs.getHOST()))

This should always convert LOCAL to an empty string including cases when "local" is not yet in converted to upper case.

You don't need to restart any service after this change, just edit the job using web console and save changes. On every save it will now check for all versions of LOCAL value and substitute it with an empty string.

Ok, that gets past the host error. Now I get

26/07/2007 14:32:51 2 222 0 Run log parser Logon failed. Return code: 1326 - Logon failure: unknown user name or bad password.

Is this possibly related to the multiplatform version using only OS security (we're using the windows version)? The account I'm logged into the web console works fine, it's a 24x7 account that doesn't exist as a windows account.

Works fine apart from this error should I say

The console always sets the jobs to run under specific user account. For the account, by default it enters the logon name that you specify on the console's logon page. You can override this account using Run As button in the wizard.

To avoid changing the account properties manually, setup and use accounts in 24x7 whose names match your domain accounts or local accounts, for example MyDomain\MyName or .\MyName

Please make sure the used accounts have "Logon as a batch job" system privilege and the 24x7 service account has "run as part of operation system" privilege.

What about script jobs? They don't have a runas button; what is the difference in what context they run in?

In Windows version script jobs always run under the service account. To run them under another user account you can start them from command line or from another job using RunAsUser with a command line like 24x7 /JOB. You can also use RunAs.exe command line utility with 24x7 /JOB command.

In the Multi-platform version the scheduler can run job of any type using different user account, e.g. the Run AS button and functionality is available for all job types.