topic Re: Stored Process fails when scheduled, but runs fine when run on-demand in SAS Web Report Studio

Stored Process fails when scheduled, but runs fine when run on-demand

sustagens — Fri, 27 Sep 2019 09:07:52 GMT

I have a stored process that runs perfectly when opened in WRS through File>Open.

When I schedule the exact same stored process though, it shows a Failed status. I am stuck trying to decipher why and where it failed, when it runs fine when it is run manually in WRS. There were also no errors whatsoever during debugging in EG.

It is impossible to determine without any link to the log in the Status, it just says Failed point blank. How can I see the SAS log from the Stored Process that the schedule ran?

Re: Stored Process fails when scheduled, but runs fine when run on-demand

AnandVyas — Fri, 27 Sep 2019 09:23:23 GMT

Hi @sustagens

It could be due scheduling issues and not STP code. How are you scheduling STP, using SMC?

Thanks!

Re: Stored Process fails when scheduled, but runs fine when run on-demand

sustagens — Fri, 27 Sep 2019 09:40:03 GMT

I just do it in Web Report Studio, I schedule the report that is the output of the STP. Within my code I also update tables stored in permanent libraries. Is the answer to my problem in SMC?

Re: Stored Process fails when scheduled, but runs fine when run on-demand

AnandVyas — Fri, 27 Sep 2019 10:57:44 GMT

There are few Roles and Capabilities that are required in order to schedule reports. Please check if the ID you are using have these roles. If not, you will have to check with your site administrator to help you grant these permissions.

Thanks!

Re: Stored Process fails when scheduled, but runs fine when run on-demand

Madelyn_SAS — Fri, 27 Sep 2019 13:55:59 GMT

This is likely related to the server that you have selected to execute the stored process. Please see this SAS Note:

http://support.sas.com/kb/41/751.html

Re: Stored Process fails when scheduled, but runs fine when run on-demand

sustagens — Mon, 30 Sep 2019 03:08:34 GMT

Thank you Madelyn_SAS, you are right - it looks like it's because I have set up the stored process to run using the Workspace server.

Upon changing it to run using the Stored Process server though, it error'ed when I ran it in EG - due to not having "appropriate authorisation" to the permanent libraries. It turns out:
"The SAS Stored Process Server is launched using the multi-user credentials account defined in the properties of the server (by default, the SAS General Servers group login account, sassrv, is used)."

So it looks like the default sassrv doesn't have access to the permanent libraries. I have asked for access to SAS Management Console so I can set up multi-user credentials and try to schedule it again. Thanks for your help.