Skip to main content

How to start SAS Deployment Agent service?

In my previous article, you might have learnt that we need to start SAS Deployment Agent service to run SAS Deployment backup and recovery tool batch commands. So in this article lets focus how exactly to start the service in Windows and Linux environment.

Note: This article is applicable only for SAS 9.4 as this backup tool is introduced in SAS 9.4 version.

Starting SAS Deployment Agent service in Windows:


  • It is easy to do this in windows since you can see all the services in Windows Services. Open Windows Services and check the status of SAS Deployment Agent. It should be either stopped or running. If it is stopped then start it.
  • If you are not sure how to launch Windows Services, then open Run -> type services.msc in the text box. This will launch you the Windows Services window.


Starting SAS Deployment Agent service in Linux:


  • In Linux you can check whether the service is running or not by giving ps -ef command. This will show the list of all running process. You can pipe it with grep command like ps -ef|grep deployment to filter the output.
  • I hope your will be using PuTTy SSH client to connect to host machine runnning SAS Platform. For starting this service you need XTerm which is also an SSH client and it shows graphical contents. Read further to discover why you need graphical contents to be displayed for starting a service.
  • To start the service you need to run the command sasdm.sh (SAS Deployment Manager). It will be located in SAS installation diretory under SASDeploymentManager subdirectory. This command opens a graphical window from where you need to start the SAS Deployment Agent service. So you need use SSH client which can show you graphical content, I use Xterm in my environment. Once the window opens, select English and click OK.
  • You will find several options related to SAS Deployment, as our goal is to start the service select Start SAS Deployment Agent Service radio button under Manage SAS Deployment Agent Service.




  • Click Start
  • Then click Finish

Comments

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 f...
2 comments
Read more

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...
2 comments
Read more

Insufficient authorization to access prgramname.lst

Issue: I had an issue with batch server. The code runs fine in SAS EG and SAS DI Studio but fails when I run with batchserver. Error seems to be ERROR: Insufficient authorization to access /opt/sasinside/Lev1/SASApp/Sas_Program.lst. NOTE: The SAS System stopped processing this step because of errors. Solution: When you execute on batch mode sas tries to save the output file (Sas_Program.lst) under /opt/sasinside/Lev1/SASApp where is no permission to write. We should add two system options to sasv9_usermods.cfg file to redirect this outputs to another directory. The options are following: -altprint <directory>  -print <directory> Where directory is a directory where you have access to write. You must provide this directory. The directory can be some shared location like: /share/sas/lst. If you decide to add this options these are the steps to follow: 1. Create or choose a driectory where your userid have write access. The userid is the ...
Post a Comment
Read more