Stored Process runs in Ent. Guide but not Web Report Studio

[deleted_user]

I recently finished creating a stored process that runs well in Enterprise Guide, but does not run in Web Repport Studio. Has anyone else encountered this problem? If you did, what did you do to resolve it?

Thanks so much, in advance!

[Cynthia_sas]

In order for Stored Processes to execute from Web Report Studio, they must be stored in a special location in the metadata known as the "BIP Tree" folder.

Looking at the SAS Log might help, if you are getting a SAS Log. If you are not getting a SAS Log, but are getting Java error messages, then you might consult the Platform Administrator documentation for help. Otherwise, there are other possibilities that might be involved, but your best bet for a quick response to this issue is to contact Tech Support.

cynthia

[deleted_user]

Hi, Cynthia,

What had happended was that I had an extraneous quit; at the end of my code, right before my %stpend; line. When I removed the quit; statement, my stored process worked correctly. I had already placed my process into the "BIP Tree" folder.

Thans for replying! I appreciate it.

[deleted_user]

I need to clarify this for myself Cynthia.

Have you any idea why an extra Quit; statement would cause this problem? From a foundation SAS viewpoint, an extra run, quit or semicolon is usually benign.

Why would this cause a problem for a stored process?

Kind regards

David

[Cynthia_sas]

David:
Without actually seeing ALL the code and the WRS log where it did NOT work, I'm not sure what was going on. SAS Web Report Studio uses SASReport XML by default. EG uses HTML by default as the result type. Removing an extra quit doesn't seem like it would have an effect for either result type creation -- UNLESS it was enclosed somehow in a nested macro call and abnormally ended -- a situation which EG might recover from more gracefully than WRS.

This is one reason why I recommend having a working SAS program to start (which only would have had 1 quit in the right place) and then when the code was "macro-ized" there would have been less of a chance to introduce an error.

cynthia