SUPPORT / SAMPLES & SAS NOTES
 

Support

Problem Note 65853: SAS® Enterprise Miner™ nodes are executed on a local machine instead of the grid

DetailsHotfixAboutRate It

If you run nodes (a flow) in SAS Enterprise Miner, and Integrated Windows Authentication (IWA) is enabled on a grid environment, then the run should go to the grid for execution as a grid job.  However, the run is executed on the local machine, and fails to go to the grid.  This failure occurs because SAS Enterprise Miner passes an unnecessary metadata-connection-option with a one-time password (OTP) for the workspace server.

An "options" message with the OTP that is passed is displayed in the workspace-server log:

  2019-12-13T14:36:38,942 INFO  [00000011] :sasdemo - 1 options 
  metaport=8561 metauser="sasdemo@!*(generatedpassworddomain)*!"
  metaserver="<server name>"


  2019-12-13T14:36:38,942 INFO  [00000011] :sasdemo - 1 !  
  metapass=XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX metaprotocol=Bridge
  metarepository="Foundation"; %let
  2019-12-13T14:36:38,942 INFO  [00000011] :sasdemo - 1!
  EM_SERVER_CONTEXT=SASApp;  %let EM_GRID_OPTIONS=;

Further down in the log, "invalid credentials" and "access denied" errors are displayed.  A "server not found" note is displayed.  These entries in the log indicate that the run was executed on the local machine, instead of on the grid: 

  2020-04-07T09:29:45,872 INFO  [00000012] :bikara - 17151 %let grid_numnodes=%sysfunc(grdsvc_nnodes("server=SASApp"));
  2020-04-07T09:29:45,872 INFO  [00000012] :bikara - NOTE: Connecting to SAS Metadata Server produced: ERROR: Invalid credentials
  2020-04-07T09:29:45,872 INFO  [00000012] :bikara - NOTE: Connecting to SAS Metadata Server produced: ERROR: Access denied.
  2020-04-07T09:29:45,872 INFO  [00000012] :bikara - NOTE: SAS application server not found; the local machine will be used.

 

Use one of the following two workarounds to circumvent this problem, and then rerun your flow or node:

  • Log on to SAS Enterprise Miner without IWA (by entering your credentials manually on the logon page).
  • Enter the following OPTIONS statement in your Enterprise Miner project start code:

options metauser="" metapass="";

 


Operating System and Release Information

Product FamilyProductSystemProduct ReleaseSAS Release
ReportedFixed*ReportedFixed*
SAS SystemSAS Enterprise MinerMicrosoft® Windows® for x6415.19.4 TS1M6
Microsoft Windows 8 Enterprise 32-bit15.19.4 TS1M6
Microsoft Windows 8 Enterprise x6415.19.4 TS1M6
Microsoft Windows 8 Pro 32-bit15.19.4 TS1M6
Microsoft Windows 8 Pro x6415.19.4 TS1M6
Microsoft Windows 8.1 Enterprise 32-bit15.19.4 TS1M6
Microsoft Windows 8.1 Enterprise x6415.19.4 TS1M6
Microsoft Windows 8.1 Pro 32-bit15.19.4 TS1M6
Microsoft Windows 8.1 Pro x6415.19.4 TS1M6
Microsoft Windows 1015.19.4 TS1M6
Microsoft Windows Server 2012 Datacenter15.19.4 TS1M6
Microsoft Windows Server 2012 R2 Datacenter15.19.4 TS1M6
Microsoft Windows Server 2012 R2 Std15.19.4 TS1M6
Microsoft Windows Server 2012 Std15.19.4 TS1M6
Microsoft Windows Server 201615.19.4 TS1M6
Microsoft Windows Server 201915.19.4 TS1M6
Windows 7 Enterprise 32 bit15.19.4 TS1M6
Windows 7 Enterprise x6415.19.4 TS1M6
Windows 7 Home Premium 32 bit15.19.4 TS1M6
Windows 7 Home Premium x6415.19.4 TS1M6
Windows 7 Professional 32 bit15.19.4 TS1M6
Windows 7 Professional x6415.19.4 TS1M6
Windows 7 Ultimate 32 bit15.19.4 TS1M6
Windows 7 Ultimate x6415.19.4 TS1M6
64-bit Enabled AIX15.19.4 TS1M6
64-bit Enabled Solaris15.19.4 TS1M6
HP-UX IPF15.19.4 TS1M6
Linux for x6415.19.4 TS1M6
Solaris for x6415.19.4 TS1M6
* For software releases that are not yet generally available, the Fixed Release is the software release in which the problem is planned to be fixed.