I had the exact problem a while ago. I'm trying to recall from memory, so forgive me if it's not 100%....   Oracle introduced a change where the signing of components are more strict. So if you have a later version of JWS with a earlier version of SAS, you find that some SAS components are 'not trusted' according to Oracle. The temp fix is to relax some of these algorithms on  JWS. Unfortunately I got it from a Javaforum somewhere and I don't have the details anymore. Just Google, you'll pick it up.   However, personally, I would suggest that you look into using the SAS EMiner fat client rather. There are perceived benefits from using JWS, but my experience has always been the opposite. E.g. things like this. 'Something' changes in the world of Java, and things stop working. By using the fat clients, you know it will work since the client and server software comes packaged form the same vendor and works without fail. Just my 2 cents worth.... ... View more

For a SAS Grid environment, you can also use Grid Options Sets. See this link...   http://support.sas.com/documentation/cdl/en/gridref/67371/HTML/default/viewer.htm#n1inymfs0b7go2n147xdknz0ygpx.htm     ... View more

I echo @Kurt_Bremser's comment. Thank you for the work you've done in this field. Good job. ... View more

ESP seems to be an exception....   https://support.sas.com/en/documentation/third-party-software-reference/viya/support-for-operating-systems.html#windows ... View more

Running the below will tell you where the value was loaded from. Saves a ton of time troubleshooting...   proc options option=encoding value; run; ... View more

Awesome, exactly what I needed, thanks.   Version is 7.12...   Host: wx6 Product: msofficeint Version: 7.12 Display Name: SAS Add-in for Microsoft Office Hot Fix Entry: Hotfix Y40002 Display Version: 7.12 ... View more