Skip to main content

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 with same the user id and password that they provided to us. Also, they gave as a hint to check whether the driver is installed properly.

After verifying with previous working entry, I found that I have give wrong driver path in odbc.ini file. After modifying the entry, the library assigned successfully.

Sample ODBC entry in odbc.ini file

[SALES]
Driver=/datbase/sqlserver/DDODBC/lib/S0msss26.so
Description=DataDirect 7.1 SQL Server Wire Protocol
Address=267.222.111.555,2343
AnsiNPW=Yes
Database=SALES
Username=
Password=
QuotedId=No
EnableProcessLicensing=1

Sample Libname statement:

LIBNAME test SQLSVR datasrc=SALES USER=farustrix  PASSWORD='1234' ;

Comments

  1. Hi,

    I love this page. It has helped me a lot.
    I have few questions.

    We are facing similar issue with SQL library .But our path for odbc is correct in sasenv_local. what else can be done?

    ODBCHOME=/sas1/sashome/AccessClients/9.4/SQLServer
    export ODBCHOME
    ODBCINI=$ODBCHOME/odbc.ini
    export ODBCINI
    ODBCINSTINI=$ODBCHOME/odbcinst.ini
    export ODBCINSTINI

    ReplyDelete
  2. also what is this .so file? S0msss26.so

    ReplyDelete
  3. Facing a SAS - CLI error when trying to establish a connection can be frustrating. Hosting Spell provides dependable hosting services that ensure stable and secure connections for seamless SAS integration and smooth data processing!

    ReplyDelete

Post a Comment

Popular posts from this blog

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 file. Us

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.