SASJobExecution Logs

[devrant]

Hi,

using the SASJobExecution\Jobs interface I can usually check out the execution logs for jobs that were called from Visual Analytics. Unfortunately I've came across a situation today,  where the job execution by an other user throws an error and seemingly doesn't produce any logs. To be more specific, the same job was being called from the same VA report, however with this other user the 'show log' context menu shows an error message that the log wasn't found. When I check the job output from the same context menu for the same execution it shows the following: "Das für den Auftrag angegebene SAS-Programm stieß beim Start auf einen Fehler. The session requested is currently in a failed or stopped state.". In the Environment Manager I've fonud the following entry for the job call: "service [***] [ERROR_STARTING_JOB] Error starting compute service job *** due to exception 400 Bad Request.".

Could you please guide me why I don't get any job execution logs in this case?

Thank you!

[jimbarbour]

Probably (probably, not certainly), you're not getting an execution log because the job never got to the point of execution.  The job failed before execution.

If a job works for one person but not for another, it's often either:

1. A differences in permissions (access levels such as read vs. write or being allowed to read at all, for example).
2. A difference in environments (does the second person have the same drives mapped, for example).

My response is a little bit general, but that's where I would start looking (at the permissions and at any potential differences in the environment).

Jim

[devrant]

Hi Jim, hi Allen,

Thank you for your swift answer!

I've changed the other user's rights and user groups, so that we both have all the same Viya permission settings. Unforunately it did not solve my issue so far, therefore what I'm considering now is to either ask our server admin - as Allen suggests/suggested - to provide me with the job logs or to ask him to restart the server.

I'll get back to you with my findings next week. Have a nice weekend!

[AllanBowe]

You may see more information in the logs, eg under `/opt/sas/viya/config/var/log`

[devrant]

Hi,
I've finally figured what the issue was. I got to know, that the SASJobExecution service requires access to SASStudioV to run the SAS code part of a job definition. Although the test user had access within Viya to SASStudioV, spite the SASUSER library Studio was not able to run, thus the SAS code in the job was also not executed. I've realized that the SASUSER requires an existing home diretory on the linux filesystem. Without that SASStudioV was not able to start at all, thus the SAS code part of thejob wasn't able to run at all, therefore no job execution logs were generated.
Essentially, the dependencies of a SAS job to be executed in a job definition requires the following: SASStudioV <-- SASUSER library <-- physical home directory on the Viya servers's filesystem.

edit: typo

[AllanBowe]

Useful to know - thanks for sharing!

I do wonder if this requirement would be avoided if you configure your Job Execution context to run under a shared account (in this case the code would run under a system identity). Configuration steps here: https://sasjs.io/guide-viya/#shared-account-and-server-re-use

Anyway, glad you got it resolved.