Hi,   When I login to Linux i see this PATH:   [EUROPE\bart.heinsius-b@zew-v-0a2f0b04 ~]$ echo $PATH /apps/sas/thirdparty/pm/9.1/bin:/apps/sas/thirdparty/pm/9.1/linux2.6-glibc2.3-x86_64/bin:/apps/sas/thirdparty/lsf/9.1/linux2.6-glibc2.3-x86_64/etc:/apps/sas/thirdparty/lsf/9.1/linux2.6-glibc2.3-x86_64/bin:/usr/lib64/qt-3.3/bin:/usr/local/bin:/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/sbin:/bin:/usr/bin:/home/bart.heinsius-b/bin [EUROPE\bart.heinsius-b@zew-v-0a2f0b04 ~]$   When I submit x 'echo $PATH > /tmp/path.txt' from a SAS session running as me I see this PATH:   [EUROPE\bart.heinsius-b@zew-v-0a2f0b04 ~]$ cat /tmp/path.txt /oracle/oracle-client/11.2.0.3/client/bin:/oracle/oracle-client/11.2.0.3/client/bin:/usr/bin:/bin [EUROPE\bart.heinsius-b@zew-v-0a2f0b04 ~]$   Why are they different?   Regards, Bart ... View more

Hi,   I have a SAS 9.4M5 web environment on http://server1.internal:7980/. I want to make it possible to run SAS Stored Processes on this server from the internet on https://mysite.example.com/ through a reverse proxy on a separate Apache instance.   I got a part working with this in the Apache instance:   <location /SASStoredProcess/> ProxyPass http://server1.internal:7980/SASStoredProcess/ ProxyPassReverse http://server1.internal:7980/SASStoredProcess/ SetEnv force-proxy-request-1.0 1 SetEnv proxy-nokeepalive 1 </Location>   <location /SASLogon/> ProxyPass http://server1.internal:7980/SASLogon/ ProxyPassReverse http://server1.internal:7980/SASLogon/ SetEnv force-proxy-request-1.0 1 SetEnv proxy-nokeepalive 1 </Location>     in combination with changing the External Connections of these applications in SAS Management Console to:   Communication Protocol: HTTPS Host Name: mysite.example.com Port Number: 443 Service: /SASStoredProcess   resp.    Communication Protocol: HTTPS Host Name: mysite.example.com Port Number: 443 Service: /SASLogon   When navigating to https://mysite.example.com/SASStoredProcess/ I am redirected to https://mysite.example.com/SASLogon so that looks to be working ok. But after entering my credentials I get:   HTTP Status 401 – Unauthorized   Am I doing this right? Is there documentation on how to do this?   Bart ... View more

Hi,   My customer wants to update the name of his metadata user. In the user properties in SAS Management Console, this field is grayed out:     Customer found that when he requests properties of the user from the metadata folder /System/Security/Users, he *can* modify the name:   Can he do this? Will it mess things up?   Bart     ... View more

Hi,   This is 94M3 on Linux.   I can run this command from the linux bash shell, it runs fine:   /apps/sas/SASConfig/Lev3/SASApp/WorkspaceServer/WorkspaceServer.sh -sysin /tmp/mySasProgram.sas   Now I run this command from a SAS Enterprise Guide-started Workspace Server session from an X command with this code:   x '/apps/sas/SASConfig/Lev3/WorkspaceServer/WorkspaceServer.sh -sysin /tmp/mySasProgram.sas';   It does not run fine. The Workspace Server session is started but metadata libraries are not assigned. The log shows: 2017-08-03T17:56:06,321 ERROR [00000006] :bart.heinsius - ERROR: Invalid credentials 2017-08-03T17:56:06,321 ERROR [00000006] :bart.heinsius - ERROR: Access denied.   The metadata server log shows (don't mind the time stamps): 2017-08-02T18:36:01,320 WARN  [01144984] : SYSTEM@MUNTSE-S-10161 - SAS token not found from bart.heinsius. 2017-08-02T18:36:01,320 WARN  [01144984] : SYSTEM@MUNTSE-S-10161 - New client connection (36753) rejected from server port 38561 for user bart.heinsius@!*(generatedpassworddomain)*!. Peer IP address and port are [::ffff:144.209.58.209]:38902 for APPNAME=SAS. 2017-08-02T18:36:01,320 INFO  [01144984] : SYSTEM@MUNTSE-S-10161 - Client connection 36753 closed.   It seems that the shell spawned by the xcmd is not the same as my normal login shell.   Why is this? What can I do to fix it?   Bart ... View more