<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Insufficient authorization to access PIPE in SAS Data Management</title>
    <link>https://communities.sas.com/t5/SAS-Data-Management/Insufficient-authorization-to-access-PIPE/m-p/492220#M15297</link>
    <description>&lt;P&gt;I just did a full restart services which includes Object Spawner. It is still the same. Any other possible area?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;You mentioned 'have it re-read all server configurations." Can I know more on this?&lt;/P&gt;</description>
    <pubDate>Tue, 04 Sep 2018 08:12:53 GMT</pubDate>
    <dc:creator>imdickson</dc:creator>
    <dc:date>2018-09-04T08:12:53Z</dc:date>
    <item>
      <title>Insufficient authorization to access PIPE</title>
      <link>https://communities.sas.com/t5/SAS-Data-Management/Insufficient-authorization-to-access-PIPE/m-p/491993#M15285</link>
      <description>&lt;P&gt;Dear all, I come across a script here and it is prompting me the error :&lt;/P&gt;&lt;P&gt;Insufficient authorization to access PIPE&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;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.&lt;/P&gt;&lt;P&gt;ERROR: Insufficient authorization to access PIPE.&lt;BR /&gt;ERROR: Error in the FILENAME statement.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;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.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Please also refer to my screenshot below:&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Workspace server XCMD options.PNG" style="width: 421px;"&gt;&lt;img src="https://communities.sas.com/t5/image/serverpage/image-id/22951i8E1EE1968FA105F3/image-size/large?v=v2&amp;amp;px=999" role="button" title="Workspace server XCMD options.PNG" alt="Workspace server XCMD options.PNG" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;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.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks in advanced everyone.&lt;/P&gt;</description>
      <pubDate>Mon, 03 Sep 2018 07:22:39 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Data-Management/Insufficient-authorization-to-access-PIPE/m-p/491993#M15285</guid>
      <dc:creator>imdickson</dc:creator>
      <dc:date>2018-09-03T07:22:39Z</dc:date>
    </item>
    <item>
      <title>Re: Insufficient authorization to access PIPE</title>
      <link>https://communities.sas.com/t5/SAS-Data-Management/Insufficient-authorization-to-access-PIPE/m-p/491996#M15286</link>
      <description>&lt;P&gt;What software is this?&amp;nbsp; Where is it installed?&amp;nbsp; Do you have access to the area?&amp;nbsp; Can you launch the cmd program or related program?&lt;/P&gt;</description>
      <pubDate>Mon, 03 Sep 2018 07:39:57 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Data-Management/Insufficient-authorization-to-access-PIPE/m-p/491996#M15286</guid>
      <dc:creator>RW9</dc:creator>
      <dc:date>2018-09-03T07:39:57Z</dc:date>
    </item>
    <item>
      <title>Re: Insufficient authorization to access PIPE</title>
      <link>https://communities.sas.com/t5/SAS-Data-Management/Insufficient-authorization-to-access-PIPE/m-p/492000#M15287</link>
      <description>&lt;P&gt;This is in SAS Data&amp;nbsp; Integration Studio. It is installed in Server.&lt;/P&gt;&lt;P&gt;I am currently in the server remote session and cmd program is accessible as I am the Admin.&lt;/P&gt;</description>
      <pubDate>Mon, 03 Sep 2018 07:45:36 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Data-Management/Insufficient-authorization-to-access-PIPE/m-p/492000#M15287</guid>
      <dc:creator>imdickson</dc:creator>
      <dc:date>2018-09-03T07:45:36Z</dc:date>
    </item>
    <item>
      <title>Re: Insufficient authorization to access PIPE</title>
      <link>https://communities.sas.com/t5/SAS-Data-Management/Insufficient-authorization-to-access-PIPE/m-p/492001#M15288</link>
      <description>&lt;P&gt;Ok, sorry, never used that.&amp;nbsp; Maybe someone in the DM forum has.&lt;/P&gt;</description>
      <pubDate>Mon, 03 Sep 2018 07:47:30 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Data-Management/Insufficient-authorization-to-access-PIPE/m-p/492001#M15288</guid>
      <dc:creator>RW9</dc:creator>
      <dc:date>2018-09-03T07:47:30Z</dc:date>
    </item>
    <item>
      <title>Re: Insufficient authorization to access PIPE</title>
      <link>https://communities.sas.com/t5/SAS-Data-Management/Insufficient-authorization-to-access-PIPE/m-p/492004#M15289</link>
      <description>&lt;P&gt;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.&lt;/P&gt;
&lt;P&gt;At least connect to it from SMC and have it re-read all server configurations.&lt;/P&gt;</description>
      <pubDate>Mon, 03 Sep 2018 07:56:16 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Data-Management/Insufficient-authorization-to-access-PIPE/m-p/492004#M15289</guid>
      <dc:creator>Kurt_Bremser</dc:creator>
      <dc:date>2018-09-03T07:56:16Z</dc:date>
    </item>
    <item>
      <title>Re: Insufficient authorization to access PIPE</title>
      <link>https://communities.sas.com/t5/SAS-Data-Management/Insufficient-authorization-to-access-PIPE/m-p/492220#M15297</link>
      <description>&lt;P&gt;I just did a full restart services which includes Object Spawner. It is still the same. Any other possible area?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;You mentioned 'have it re-read all server configurations." Can I know more on this?&lt;/P&gt;</description>
      <pubDate>Tue, 04 Sep 2018 08:12:53 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Data-Management/Insufficient-authorization-to-access-PIPE/m-p/492220#M15297</guid>
      <dc:creator>imdickson</dc:creator>
      <dc:date>2018-09-04T08:12:53Z</dc:date>
    </item>
    <item>
      <title>Re: Insufficient authorization to access PIPE</title>
      <link>https://communities.sas.com/t5/SAS-Data-Management/Insufficient-authorization-to-access-PIPE/m-p/492550#M15334</link>
      <description>&lt;P&gt;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).&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;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.&lt;/P&gt;
&lt;P&gt;Unless a similar search in your configuration tree turns up other places where xcmd is set.&lt;/P&gt;</description>
      <pubDate>Wed, 05 Sep 2018 07:28:43 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Data-Management/Insufficient-authorization-to-access-PIPE/m-p/492550#M15334</guid>
      <dc:creator>Kurt_Bremser</dc:creator>
      <dc:date>2018-09-05T07:28:43Z</dc:date>
    </item>
    <item>
      <title>Re: Insufficient authorization to access PIPE</title>
      <link>https://communities.sas.com/t5/SAS-Data-Management/Insufficient-authorization-to-access-PIPE/m-p/492551#M15335</link>
      <description>&lt;P&gt;If you completely stopped the spawner (no SAS process active at the time), then it &lt;EM&gt;had&lt;/EM&gt; to re-read the configuration.&lt;/P&gt;
&lt;P&gt;The less "brutal" option is to log on to the metadata as sasadm@saspw, connect to the spawner and refresh it.&lt;/P&gt;</description>
      <pubDate>Wed, 05 Sep 2018 07:32:56 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Data-Management/Insufficient-authorization-to-access-PIPE/m-p/492551#M15335</guid>
      <dc:creator>Kurt_Bremser</dc:creator>
      <dc:date>2018-09-05T07:32:56Z</dc:date>
    </item>
  </channel>
</rss>

