Hello,
I get a log "process finished with exit code 1".
Is it my own process which fails and returns '1' or is it set by 24x7 sched ?

Daniel

It is your process that reports exit code 1.

FYI: Non-zero exit codes usually indicate some error condition that's why by default 24x7 writes a warning message to the job log. If you believe this exit code is ok, modify the job definition on the enable error condition check; list both 0 and 1 and successful exit codes.

: Hello,
: I get a log "process finished with exit code 1".
: Is it my own process which fails and returns '1' or is it set by 24x7 sched ?

: Daniel

: It is your process that reports exit code 1.

: FYI: Non-zero exit codes usually indicate some error condition that's why by
: default 24x7 writes a warning message to the job log. If you believe this
: exit code is ok, modify the job definition on the enable error condition
: check; list both 0 and 1 and successful exit codes.

Yes, I have finally found the error.
I haven't it when this is chained by a semaphore file and not by a check-cbox in the first job ; and this only in the particular situation when the first job is launched by 24x7 es.

If I launch manually the fisrt job; the second finishes well whatever the type of chain.

Daniel

Well, this looks like your process is sensitive to how it runs rather how it is chained to other jobs.

If the job is triggered from the event server or when the scheduler is run as service it also runs as a service process meaning that it inherits certain restrictions that Windows creates for service. For example if the service is not running under proper account your process may fail to access network files or send an email; or if the process features some graphical interface it may fail to run because it cannot access the user desktop.

If the problem is network related try using domain admin or other admin account with proper privileges. If the problem is desktop related either use "Bind to User Desktop" parameter in the event server or use BindDesktop utility with the scheduler (add it to the job command line) For http://www.softtreetech.com/24x7/script.htm more info

: Yes, I have finally found the error.
: I haven't it when this is chained by a semaphore file and not by a check-cbox
: in the first job ; and this only in the particular situation when the
: first job is launched by 24x7 es.

: If I launch manually the fisrt job; the second finishes well whatever the
: type of chain.

: Daniel

: If the problem is network related try using domain admin or other admin
: account with proper privileges. If the problem is desktop related either
: use "Bind to User Desktop" parameter in the event server or use
: BindDesktop utility with the scheduler (add it to the job command line)
: For http://www.softtreetech.com/24x7/script.htm more info

I believe this comes from the Desktop.

I want my job interacts with putty / pageant in order to connect to a web server via SSH.
Pageant holds the SSH key.

I don't see how to bind the job with the Desktop :

- In the 24x7es GUI there no field with Bind, at this place i have 'visible/invisible'.
I have tried in vain this feature.

- And I don't understand how to bind with the desktop in the command line.

Can you help me ?
Daniel.

It is not a job property. Basiclly you need to insert BindDesktop to the job command line.

For example, if you have a btach file called putty.bat and the current command line is c:\bin\putty.bat, you would need to change that command line to

"C:\Program Files\24x7 Automation 3\BindDesktop.exe" winsta0\default "C:\bin\putty.bat"

Alternativelly you can change your putty.bat file and insert '"C:\Program Files\24x7 Automation 3\BindDesktop.exe" winsta0\default ' in front of the line calling putty.exe

: I believe this comes from the Desktop.

: I want my job interacts with putty / pageant in order to connect to a web
: server via SSH.
: Pageant holds the SSH key.

: I don't see how to bind the job with the Desktop : - In the 24x7es GUI there
: no field with Bind, at this place i have 'visible/invisible'.
: I have tried in vain this feature.

: - And I don't understand how to bind with the desktop in the command line.

: Can you help me ?
: Daniel.