Insufficient authorization to access PIPE

[imdickson]

Dear all, I come across a script here and it is prompting me the error :

Insufficient authorization to access PIPE

I did searched for awhile in this forum and read a few threads with the same error. Most of the threads suggested to "Allow XCMD" in Logical Workspace Server option. I ticked it. However, I am still getting the same exact error.

ERROR: Insufficient authorization to access PIPE.
ERROR: Error in the FILENAME statement.

I am not posting the code for now as i truly suspect this has something to do with some sorts of configurations. However, if required, please suggest and I will post the code here.

Please also refer to my screenshot below:

As you can see, XCMD has been enabled and I even did a full services restart. What else is missing? Need advice from members here.

Thanks in advanced everyone.

[RW9]

What software is this?  Where is it installed?  Do you have access to the area?  Can you launch the cmd program or related program?

[imdickson]

This is in SAS Data  Integration Studio. It is installed in Server.

I am currently in the server remote session and cmd program is accessible as I am the Admin.

[RW9]

Ok, sorry, never used that.  Maybe someone in the DM forum has.

[Kurt_Bremser]

Did you fully restart the object spawner after ticking XCMD? The object spawner reads the metadata at initialization, and is the process responsible for adding or not adding the -noxcmd commandline option.

At least connect to it from SMC and have it re-read all server configurations.

[imdickson]

I just did a full restart services which includes Object Spawner. It is still the same. Any other possible area?

You mentioned 'have it re-read all server configurations." Can I know more on this?

[Kurt_Bremser]

Try to use the same workspace server from Enterprise Guide. It might be that DI Studio somehow enforces the noxcmd on its own (although I don't know how it could do that).

A (case-insensitive) search for the string "xcmd" in my whole configuration tree found only one occurence in SASApp/BatchServer/sasbatch.sh. So it seems clear that for workspace servers it is exclusively controlled by metadata.

Unless a similar search in your configuration tree turns up other places where xcmd is set.

[Kurt_Bremser]

If you completely stopped the spawner (no SAS process active at the time), then it had to re-read the configuration.

The less "brutal" option is to log on to the metadata as sasadm@saspw, connect to the spawner and refresh it.