Skip to main content

SAS Management Console job scheduling plugin file event shows greyed out browse button

Issue:

SAS Management Console job scheduling plugin file event shows greyed out browse button.  This is a Linux server tier with SAS 9.4 M2 and Platform Process Manager 9.1 as scheduler. SMC Job Scheduling plugin does not show 'Browse' button enabled on New File Event dialog as attached in screenshot.

Screenshot:





Solution:





The Platform Process Manager was not associated to the same machine as the WorkSpace server (the SAS Application Server).  Using metabrowse edit mode metadata was updated for PM so it would have same machine name as WS. 



   











The SAS Application Server is what is used to browse the file system.  If the AppServer cannot be connected to then it will not be able to use the remote browse dialog. There should be a workspace server running on the machine where PM is defined and running.  You can check this in metadata by opening an interactive SAS session and running the METABROWSE command in the command box.  If your SAS session does not have all the proper META* options set, you will be prompted to enter them;  once you have done so, you will see a metadata browser window.  Starting from the Foundation icon, expand the tree and look at the following items.  The point is that both the Platform Process Manager server and a Workspace Server should be defined on the same AssociatedMachine object, and you should be able to see the same machine under both of these, and should be able to see the servers under the Machine's DeployedComponents. 



   



   Foundation -> ServerComponent -> Platform Process Manager -> AssociatedMachine 



   Foundation -> ServerComponent -> SASApp - Workspace Server -> AssociatedMachine 



   Foundation -> Machine -> <target host> -> DeployedComponents 

















































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




























 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.    




















1 comment









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




















3 comments









Read more