SAS EG 6.1 installation stalls at SAS Intergration Technologies Client

Many users reported that while installing SAS Enterprise Guide 6.1, the installation gets hangs while installing SAS Intergration Technologies Client. It doesn't progress to next step even though if we wait for 1 hour. Below is the screenshot.

In above figure, SAS deployment wizard used to install SAS EG client software. It freezes while installing SAS Intergration technologies client step for almost an hour.

Errors:

Install failed and rollback was not successful, exiting with error code 4

Solution:

To avoid this, close all the background application. There should not be any background application running during installation. Applications like Outlook, Communicator, web browser ect should be closed.

While re-installing, first un-install any components related to SAS 9.4. Go to control panel, Add/Remove program and un-install anything related to SAS. After un-installation is done, go to C drive -> program files and delete SASHome directory.

After completing above steps, start new installation process.

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

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