topic Re: Scheduling SAS Jobs - Driving me nuts in Administration and Deployment

Scheduling SAS Jobs - Driving me nuts

Lenvdb — Wed, 28 Sep 2016 13:47:42 GMT

We use SAS 9.4TS1M2.

We have our compute servers on Win 2012 R2.

As a SAS Administrator I have the capability to Schedule Jobs, Deploy Jobs etc in Management Console to run on our Compute Server.

We have 2 teams in our estate who also require Job Scheduling capabilities.

At some point they actually had this capability, but about 3 months ago, lost it for no apparent reason.

What we find is that when they open MC, expand the Scheduler, and find a job to schedule, and when they do a Right Click to Open the Pop up Menu. When they click on "Schedule Flow" the screen freezes.

I can only exit out of MC by killing the SAS Process Tree in the Task Manager on my local machine where MC is running.

At this point I have set these users up into 2 SAS Metadata User Groups with the following Capabilities in roles:

Job Execution: Job Administrator
Job Execution: Job Scheduler
Management Console: Content Management
Management Console: Advanced
Metadata Server: Operation

I cannot imagine any other roles they would need.

So far I gave these groups permissions for WMM on the folders in MC where they would store their Jobs.

Please can someone enlighten me as to what other steps I am missing in this process.

What else do I need to do to get them to schedule a SAS Job in MC?

As I said: I myself as Platform Administrator have no issues scheduling a Job.

When non SAS Admins try to schedule a job MC just freezes and becomes unresponsive.

I would really appreciate some help with this.

Kindest regards

Len

Re: Scheduling SAS Jobs - Driving me nuts

Kurt_Bremser — Wed, 28 Sep 2016 13:33:24 GMT

"Freezing" for me indicates a more technical problem that should be put to SAS Technical Support. Doing something invalid/illegal/illogical should always illicit a sensible response from a program.

Re: Scheduling SAS Jobs - Driving me nuts

LinusH — Wed, 28 Sep 2016 13:53:58 GMT

Also, check any log files that could be relevant, like the Metadata server and Windows events.

Re: Scheduling SAS Jobs - Driving me nuts

anja — Wed, 28 Sep 2016 14:28:54 GMT

Hi,

am not quite sure a frozen SASMC is caused by permission settings.

Do they have access/permissions to look at other plug-ins, lets say User Manager, and if so, can they look at

the properties of the objects or does it freeze as well?

As mentioned earlier, Metadata Server log, Object Spawner log, even batch server log might give you hints of what

is going on.

Situations I saw where SASMC froze was related to insufficient permissions to actually write to a log file.

Do you see any errors in the logs?

Thanks

Anja

Re: Scheduling SAS Jobs - Driving me nuts

Lenvdb — Wed, 28 Sep 2016 14:48:21 GMT

Hi all

This seems to be the error in the Log:

Wed Sep 28 15:29:47 2016
INFO: Launcher::Run::start::classpath=-cp "C:\Program Files\SASHome\SASVersionedJarRepository\eclipse\plugins\sas.launcher.jar"
Wed Sep 28 15:29:47 2016
INFO: Launcher::Run::start::mainclass=com.sas.console.visuals.MainConsole
Wed Sep 28 15:29:47 2016
ERROR: ExeProc::ExeandDisplay::GetStdHandle::NULL=203
Wed Sep 28 15:29:47 2016
INFO: ExeProc::ReadFromPipe=Standard output

Re: Scheduling SAS Jobs - Driving me nuts

anja — Thu, 29 Sep 2016 17:32:11 GMT

Hi,

has a new license been installed recently, or, any maintenance releases/hot fixes implemented?

Any software changes on the other persons' desktop lately?

A 203 error message usually indicates either a file system issue, or, a java issue.

Tech Sup can help you to further troubleshoot

Alternatively, SASMC could be re-installed on the 2 machines.

This is a long shot, but pls try the following:

Go to C:\Program Files\SASHome\SASManagementConsole\9.4

and take a look at the sasmc.ini file, lines

JavaArgs_1=-Xmx1024m (this is my modified custom setting).
JavaArgs_2=-XX:MaxPermSize=128m

Compare your settings with the SASMC settings on the other admins' pcs.

OR, are you using SASMC differently and it is not locall installed on the individual pcs?

Thanks

Anja

Re: Scheduling SAS Jobs - Driving me nuts

Lenvdb — Tue, 04 Oct 2016 12:57:06 GMT

HI Anja

We finally fixed it. It was a Permissions issue on Windows AD.

Once the correct permissions were applied, they could access the scheduler.

Thank you everyone for your help with this.

Len