Skip to main content

Getting error in SAS MID Tier Services script

Question:
We are getting below error while executing the SAS Mid tier services script while starting.

Starting SAS Web App Server: SASServer11_1
(this can take a while)
/sas/config/mid/Lev1/sas.servers.mid: line 192: [: users: integer expression expected
waiting 30 ...
/sas/config/mid/Lev1/sas.servers.mid: line 192: [: users: integer expression expected
waiting 30 ...
/sas/config/mid/Lev1/sas.servers.mid: line 192: [: users: integer expression expected
waiting 30 ...
/sas/config/mid/Lev1/sas.servers.mid: line 192: [: users: integer expression expected
waiting 30 ...
/sas/config/mid/Lev1/sas.servers.mid: line 192: [: users: integer expression expected
waiting 60 ...
/sas/config/mid/Lev1/sas.servers.mid: line 192: [: users: integer expression expected

We open the script using VIM editor and checked in the line 192 ,there is only a if then statement which an we believe it is a valid one.   

ROLLCHK=`ls -l $SASWEBAPPSRV_DIR/$SASWEBAPPINSTANCE/logs/server.log`
# clear leading blanks, then strip trailing filename
ROLLCHK=`echo $ROLLCHK | tr -s ' ' | cut -d ' ' -f 5`
if [ $ROLLCHK -lt $ROLLMARK ];
then
{
echo "Note: $SASWEBAPPINSTANCE server.log rolled over during startup."
MYMARK=1
}
fi

Though the services status is showing as UP but we are not able to open any Mid Tier application.

Answer:
Modify lines 152 and 188 of sas.servers.mid to use "ls -n" instead of "ls -l" when querying the server.log file to get around this problem:
 
From
ROLLMARK=`ls -l $SASWEBAPPSRV_DIR/$SASWEBAPPINSTANCE/logs/server.log`
ROLLCHK=`ls -l $SASWEBAPPSRV_DIR/$SASWEBAPPINSTANCE/logs/server.log`

To
ROLLMARK=`ls -n $SASWEBAPPSRV_DIR/$SASWEBAPPINSTANCE/logs/server.log`
ROLLCHK=`ls -n $SASWEBAPPSRV_DIR/$SASWEBAPPINSTANCE/logs/server.log`

It looks like either user or group names contain spaces.

Comments

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

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

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.