Hi, Did you get this resolved? Thanks. ... View more

Hi Jaap, Sorry if I have confused you. We don't use internal accounts. I only created an internal account for me to test. A user is created in the SAS Management Console based off their details in AD. A local account for this user is also created on the AIX servers where they are added to a generic SAS group, as well as a specific Business Unit group/s. So for example, I would be created in SAS MC as vellis. A local account of vellis would also be created on the server, and added to a group called SAS_UNIX_Primary with all other SAS Users. I hope that helps. Thanks, VInnie ... View more

Hi, This afternoon I have been able to run the following successfully in production. It prompts me for server details etc, username and password, then allows me to connect to server and lists the available libraries. However in test I get the following error... OPTIONS COMAMID=TCP; FILENAME RLINK 'C:\Program Files\SASHome\SASFoundation\9.3\connect\saslink\tcpunix.scr'; signon server="SASApp - Connect Server"; 1    OPTIONS COMAMID=TCP; 2    FILENAME RLINK 'C:\Program Files\SASHome\SASFoundation\9.3\connect\saslink\tcpunix.scr'; 3    signon server="SASApp - Connect Server"; ERROR: Unsuccessful connect to the SAS Metadata Server. ERROR: Unable to retrieve the SAS/CONNECT server definition "SASAPP - CONNECT SERVER". ERROR: Remote signon to SASAPP - CONNECT SERVER canceled. Thanks, Vinnie ... View more

Hi Jaap, Thanks for replying. Yes, my personal account is vellis. These are also my AD credentials. An account exists in Metadata which uses a Back-End configuration to authenticate with LDAP. I have also created internal accounts in both environments for myself, and have tried running the autoexec in prod, which runs successfully, but fails in test. Prod: Test: 10   /*password = _Prompt_;*/ 11   options metaserver="saststmds.moh.govt.nz" /*10.130.21.141*/ 12 13       metaport=8562 14       metarepository=Foundation 15       metauser="Vinnie Ellis@saspw" 16       metapass=XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX 17 18          ; 19    signon server="SASApp - Connect Server"; ERROR: ERROR: No logins found. ERROR: Retrieving login information based on AuthenticationDomain from the SAS Metadata Server        failed. ERROR: Unable to retrieve the SAS/CONNECT server definition "SASAPP - CONNECT SERVER". ERROR: Remote signon to SASAPP - CONNECT SERVER canceled. 20   /*password = _Prompt_;*/ This is what I see in the ConnectSpawner_saststcts.log. I am pretty sure I have checked this previously but haven't seen these Permission Denied error which are concerning. I have checked the internet and forums but haven't been able to find anything useful regarding this error. 08.45.58.99: Copyright (C) 2002-2011, SAS Institute Inc., Cary, NC, USA. All Rights Reserved. 08.45.58.99: SAS Job Spawner for Open Systems version 9.3 08.46.00.79: ERROR: The tcpSockWrite call failed. The system error is 'Broken pipe'. 08.46.00.82: ERROR: The tcpSockWrite call failed. The system error is 'Broken pipe'. 09.59.47.42: ERROR: Launch Failed. Cannot execute program "/opt/sas/sas93/config/Lev2/SASApp/ConnectServer/ConnectServer.sh", error = 13 (Permission denied). 09.59.47.42: ERROR: Search permission is denied for a directory or file is not an executable file 09.59.47.42: Error spawning child process, use -logfile option to capture details. 10.21.44.62: ERROR: Launch Failed. Cannot execute program "/opt/sas/sas93/config/Lev2/SASApp/ConnectServer/ConnectServer.sh", error = 13 (Permission denied). 10.21.44.62: ERROR: Search permission is denied for a directory or file is not an executable file 10.21.44.62: Error spawning child process, use -logfile option to capture details. 08.45.45.41: ERROR: Launch Failed. Cannot execute program "/opt/sas/sas93/config/Lev2/SASApp/ConnectServer/ConnectServer.sh", error = 13 (Permission denied). 08.45.45.41: ERROR: Search permission is denied for a directory or file is not an executable file 08.45.45.41: Error spawning child process, use -logfile option to capture details. I have tried running the signon command in the classic approach but get the following errors for both environments... 4    OPTIONS COMAMID=TCP; 5    %LET MYNODE=saspd1mds.moh.govt.nz 7551; 6    SIGNON MYNODE; NOTE: Remote signon to MYNODE commencing (SAS Release 9.03.01M1P110211). ERROR: A communication subsystem partner link setup request failure has occurred. ERROR: The connection was refused. ERROR: Remote signon to MYNODE canceled. 7    OPTIONS COMAMID=TCP; 8    %LET MYNODE=saststmds.moh.govt.nz 7552; 9    SIGNON MYNODE; NOTE: Remote signon to MYNODE commencing (SAS Release 9.03.01M1P110211). ERROR: A communication subsystem partner link setup request failure has occurred. ERROR: The connection was refused. ERROR: Remote signon to MYNODE canceled. I'm not the best with SAS code so am a little unsure how to use serverv with the classic signon command with serverv. I did try it using my autoexec and got the following... 50   options metaserver="saststmds.moh.govt.nz" /*10.130.21.141*/ 51 52       metaport=8562 53       metarepository=Foundation 54       metauser="Vinnie Ellis@saspw" 55       metapass=XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX 56 57          ; 58    signon serverv="SASApp - Connect Server"; NOTE: Server=                SASApp - Connect Server       Remote Session ID=     local       ServerComponentID=     A5586FBU.AV00000E       Remote Host=           saststcts.moh.govt.nz       Communication Protocol=TCP       Port=                  7552       Prompt= No       SpawnerCommand= /opt/sas/sas93/config/Lev2/SASApp/ConnectServer/ConnectServer.sh       AuthDomain= DefaultAuth       LoginName= Login.sasdemo.77       Wait= Yes       SignonWait= Yes       Status= Yes       Notify= No 59   /*password = _Prompt_;*/ I will have a read of the link you sent regarding the security configuration for UNIX environments now, to see if that may help. Thanks again, Vinnie ... View more

Hi Jaap, Thanks again for all your help so far. The Connect Spawner Port is configured for 7552 in our Test Environment. I have tried checking the processes running on our Production server before and after starting the autoexec and the only entries that are different are the following: vellis 18481230 25821360 0 15:11:36 - 0:00 sasels 12 9 13 2 12a37e vellis 19071220 5439520 1 15:11:37 pts/1 0:00 ps –ef vellis 25821360 5701760 16 15:11:36 - 0:00 /opt/sas/sas93/sw/SASFoundation/9.3/sasexe/sas -dmr -noterminal –nosyn I have also been checking the metadata logs in both environments, and from comparing them both, it looks like the connection for SASTestConnectUser is being accepted. Prod: SASConnectUser@saspw. Encryption level is Credentials using encryption algorithm SASPROPRIETARY. Peer IP address and port are [::ffff:10.64.7.110]:49170 for APPNAME=SAS. 2014-04-09T09:10:40,919 INFO  [07234153] 134718:sas - Client connection 134718 for user SASConnectUser@saspw closed. 2014-04-09T09:10:52,276 INFO  [07234155] :SASConnectUser@saspw - New client connection (142042) accepted from server port 8561 for user SASConnectUser@saspw. Encryption level is Credentials using encryption algorithm SASPROPRIETARY. Peer IP address and port are [::ffff:10.64.7.110]:49173 for APPNAME=SAS. Test: 2014-04-09T09:59:44,674 INFO  [00002437] :SASTestConnectUser@saspw - New client connection (118) accepted from server port 8562 for user SASTestConnectUser@saspw. Encryption level is Credentials using encryption algorithm SASPROPRIETARY. Peer IP address and port are [::ffff:10.64.4.140]:56108 for APPNAME=SAS. 2014-04-09T09:59:45,023 INFO  [00002448] 118:sas - Client connection 118 for user SASTestConnectUser@saspw closed. The local sas account is running the Connect Spawner: Prod: bash-4.2$ ps -ef | grep Connect      sas  5636288        1   0   25 May      -  0:00 /bin/sh -p /opt/sas/sas93/config/Lev1/ConnectSpawner/ConnectSpawner.sh start2_tag      sas  6881508  5636288   0   25 May      -  0:45 /opt/sas/sas93/sw/SASFoundation/9.3/utilities/bin/sastcpd -service 7551 -shell -netencralg SASPROPRIETARY -xmlconfigfile /opt/sas/sas93/config/Lev1/ConnectSpawner/metadataConfig.xml -logconfigloc /opt/sas/sas93/config/Lev1/ConnectSpawner/logconfig.xml -sasspawnercn Connect Spawner - SASApp -logfile /opt/sas/sas93/config/Lev1/Logs/ConnectSpawner_saspd1cts.log bash-4.2$ Test: $ ps -ef | grep Connect      sas 11337962        1   0   09 Apr  pts/1  0:00 /bin/sh -p /opt/sas/sas93/config/Lev2/ConnectSpawner/ConnectSpawner.sh start2_tag      sas 12517574 11337962   0   09 Apr      -  0:00 /opt/sas/sas93/sw/SASFoundation/9.3/utilities/bin/sastcpd -service 7552 -netencralg SASPROPRIETARY -xmlconfigfile /opt/sas/sas93/config/Lev2/ConnectSpawner/metadataConfig.xml -logconfigloc /opt/sas/sas93/config/Lev2/ConnectSpawner/logconfig.xml -sasspawnercn Connect Spawner - SASApp -logfile /opt/sas/sas93/config/Lev2/Logs/ConnectSpawner_saststcts.log [2014-04-10 14:50:08 sas@alsasts2] ~ I have then tried logging in as this user and starting the ConnectServer.sh and get the following... $ cd SASApp $ ls appserver_autoexec.sas            SASEnvironment appserver_autoexec_usermods.sas   sas.sh appservercontext_env.sh           sasv9.cfg appservercontext_env.sh.Original  sasv9_usermods.cfg BatchServer                       sasv9_usermods.cfg.old ConnectServer                     sasv9_usermods.cfg.older Data                              StoredProcessServer PooledWorkspaceServer             WorkspaceServer Reports $ cd ConnectServer $ ls autoexec.sas               logconfig.apm.xml autoexec_usermods.sas      logconfig.trace.xml ConnectServer.sh           logconfig.xml ConnectServer.sh.older     sasv9.cfg ConnectServer.sh.today     sasv9_usermods.cfg ConnectServer_usermods.sh $ ConnectServer.sh SAS(R) TCPIP REMOTE LINK PORT=43967    SESSION ESTABLISHED.^C$ I'm not sure if it is related, but I also found the following SAS Note: 18527 - "ERROR: Cannot start remote process." We also get the following errors in the Connect Spawner Console log: ERROR: (SASXKINI): PHASE 3 KERNEL INITIALIZATION FAILED. ERROR: Unable to initialize the SAS kernel. Then if I look in the sav9_usermods.cfg, on Test (/opt/sas/sas93/config/Lev2/SASApp) there appears to be an entry for SASUSER (-SASUSER /sasdata/sasuser ) /* * sasv9_usermods.cfg * *   This config file extends options set in sasv9.cfg.  Place your site-specific *   options in this file.  Any options included in this file are common across *   all server components in this application server. * *   Do NOT modify the sasv9.cfg file. * */ -WORK /saswork -UTILLOC /sasutil -SASUSER /sasdata/sasuser -VALIDVARNAME any -BUFSIZE = 64k -UBUFSIZE = 64k -IBUFSIZE = 32767 -BUFNO = 10 -UBUFNO = 10 -IBUFNO = 10 -ALIGNSASIOFILES -MEMSIZE = 512M -SORTSIZE = 256M The thing I don't understand is why this entry is not in our production environment. The file in prod is very similar except for that entry (not sure why it is not on the next line, but I have also tried dropping the entry to the next line). In Test, we have a directory called sasdata/sasuser but can't see this in Prod. I can see a sasusers directory in both environments, but only the directory in production has user profiles. I hope this all makes sense. Look forward to hearing from you. Thanks, Vinnie ... View more

Thank you Jaap for all your suggestions. I will try these today and let you know how I get on. Thanks, Vinnie ... View more

Thanks for replying Jaap. To answer some of your questions: 1. saspd1mds is our production metadata server. saststmds is our test metadata server. So basically the autoexec runs successfully in production using the SASConnectUser@saspw account. Therefore I have created a new account in test called SASTestConnectUser@saspw, encoded the password and updated the autoexec with the test server details. 2. I have also tried using the fully qualified name but I get the same error in test 3. Yes we are connecting to the default SAS-App server 4. We have a very basic set-up here, but I have mirrored the access in test off production 5. Yes,  SASTestConnectUser@saspw has read metadata permissions (I have based this off SASConnectUser@saspw in prod) 6. We had an external  SAS consultant create the original autoexec and SASConnectUser for production, when we upgraded our environment last year. However they didn't document the process. Like I said I have tried to base this test account from the production account but obviously something is not right. I'm just wondering if they made a change to a config file on the server as well? 7. I have tried updating the autoexec with my credentials and other local sas accounts but get the same error. I have also compared the OS permissions between environments, but have had no luck. Thanks, Vinnie ... View more

Thanks for replying SASKiwi. I have asked someone else to test and they get the same error. I thought it may have been something with the SAS Test Connect User I have created as well, but I have been able to successfully create a Connection Profile for this user in SAS MC. I actually have had a track open with SAS Support for the last couple of weeks, but they haven't been able to sort it yet, so that's why I have put something up on this forum. Thanks, Vinnie ... View more

Thanks Scott. I did find this SAS Note earlier and is something I have already checked. ... View more