Unable to parse the name value

Unable to parse the name value - SAS EG error

Issue

While trying to login from SAS Enterprise Guide you may get following errors

Unable to connect to metadata server
Unable to parse the name value "APPLICATIONAME=SAS%20Enterprise%20Guide".
The name is not recognized option.

Solution:

Entering wrong host name
This error arise if you enter the wrong machine name. In SAS Enterprise Guide, check whether you have given correct hostname and port number. Check for spelling mistakes and leading spaces after the host name. If you are not sure what the host name is, you can get the details from your SAS Admin.

User not member in OS level

This error will also occurs if you doesn't belong to OS level. You should be a member of atleast one group to the host you are connecting.

Using EG 6.1 to connect SAS 9.2 or below environment
If the user has SAS Enterprise Guide 6.1 and trying to access SAS 9.2 environment this issue occurs. However, in SAS support it is told that SAS EG 6.1 is compatible with SAS 9.2 but I was not able to connect from EG 6.1 to SAS 9.2.

Comments

Insufficient authorization to access PIPE error in SAS EG

Issue: When I tried to run SAS code in SAS Enterprise Guide it throws following errors: ERROR: Insufficient authorization to access PIPE. ERROR: Error in the FILENAME statement. Screenshot of error: Solution: This error occurs when you try to run OS commands in SAS code. To run the OS commands in SAS code you need to enable XCMD option. You check it in SAS Management Console by following below steps. Open SMC -> Expand Servers -> Expand In SASApp , expand Logical Workspace Server -> right click on Workspace Server. Click properties -> option tab -> advanced options -> launch properties. Check whether Allow XCMD is checked. The issue arises if the Allow XCMD is not checked. In above image, Allow XCMD option is not checked. It should be checked to run OS commands from SAS code. In Unix /Linux machines, this XCMD option can be enabled by using system option XCMD in sasv9 config file or workspaceserver.sh script f...

The authentication server is not SETUID ROOT error in SAS

Question: When validating the SAS Server from SAS Management Console, I received the following error: The authentication server is not SETUID ROOT. So, I ran the setuid.sh utility and restarted the services many times. I just checked the elssrv sasauth sasperm setuid bit. There were no error in sasauth-debug.log, sasauth-access.log, sasauth-error.log. Any suggestions? Answer: Please do the following: 1) Run /<SASConfig>/Lev<X>/ObjectSpawner/ObjectSpawner.sh stop 2) Edit /<SASConfig>/Lev<X>/ObjectSpawner/ObjectSpawner.sh and add the code shown below right after SCRIPT=`basename $0`: if [ -n ""$TKPATH"" ]; then unset TKPATH fi if [ -n ""$TK_PATHLIST"" ]; then unset TK_PATHLIST fi 3) Run /<SASConfig>/Lev<X>/ObjectSpawner/ObjectSpawner.sh start The above code change in ObjectSpawner.sh should fix the issue.

SAS - CLI error trying to establish connection

Issue: User asked me to make a database connectivity to SQL Server. They provided following details SQL server hostname and ip address Database/DSN name Username Password I made entry in ODBC.ini file. You know, SQL Server entries were made in ODBC.ini and Oracle entries were made in TNS.ora file. Everything went fine, took back up of odbc.ini, made entry and saved the file. So to test this connection I ran the libname statement in SAS Enterprise Guide 6.1. It throwed following error. Error Message: My DB team showed that they are able to login 14 GOPTIONS ACCESSIBLE; 15 LIBNAME test ODBC DATASRC=SGE_DS SCHEMA=VST USER=sales PASSWORD=XXXXXXXXX; ERROR: CLI error trying to establish connection: [SAS/ACCESS to SQL Server][ODBC SQL Server Legacy Driver][SQL Server]Login failed for user 'sales'. Solution: First I suspected that Login failed for user 'sales' meant the password provided by DB team was wrong. They responded that they were able to login wi...

SAS Platform Admin Blog

Search This Blog