SUPPORT / SAMPLES & SAS NOTES
 

Support

Problem Note 61845: Errors occur and the emi_init.sh/emi_init.bat files fail when you initialize the SAS® Environment Manager Enablement Kit Server Service Architecture

DetailsHotfixAboutRate It

When you initialize the SAS Environment Manager Enablement Kit Server Service Architecture, the emi_init.sh or emi_init.bat files might fail and generate the following message:

SAS execution returning result 253.

Similar errors might occur when executing validate.sh or validate.bat. If the SAS Environment Manager Enablement Kit Server Service Architecture is already initialized, similar errors might occur when you run certain reports.

When this problem occurs, log files that reside in the SAS-configuration-directory/Lev1/Web/SASEnvironmentManager/emi-framework/Logs directory might also display the following message"

NOTE: 401 Unauthorized.

Additional messages, similar to those shown below, are displayed in the emilnit_datetime.log, generateHTTPChecksJSON.sas.log, and get_STP_URL_datetime.log files.

In the emiInit_datetime.log file:

2018-02-12 11:14:16,755 ERROR [main] [createHTTPChecks] - SAS execution of [generateHTTPChecksJSON.sas] failed with rc 253
2018-02-12 11:14:16,755 DEBUG [main] [createHTTPChecks] - SAS execution returning result 253
2018-02-12 11:14:16,755 ERROR [main] [createHTTPChecks] - Command failed with RC 253
2018-02-12 11:14:16,757 ERROR [main] [emiInit] - There was a problem creating HTTP checks (rc [2]). Check the log file.
2018-02-12 11:14:16,757 DEBUG [main] [emiInit] - emiInit is exiting with return code 2

In the generateHTTPChecksJSON.sas.log file:

****************************************************
* (loadappcfg) ...loading configuration properties *
****************************************************
NOTE: URL for WIP Configuration Service extracted from SAS Metadata Server; URL=
http://hostname.example.com:80/SASWIPClientAccess/rest/applications
NOTE: DATA statement used (Total process time):
      real time           0.07 seconds
      cpu time            0.01 seconds
NOTE: PROCEDURE HTTP used (Total process time):
      real time           0.02 seconds
      cpu time            0.00 seconds
NOTE: 401 Unauthorized

In the get_STP_URL_datetime.log file:

****************************************************
* (loadappcfg) ...loading configuration properties *
****************************************************
NOTE: URL for WIP Configuration Service extracted from SAS Metadata Server; URL=
http://hostname.example.com:80/SASWIPClientAccess/rest/applications
NOTE: DATA statement used (Total process time):
      real time           0.08 seconds
      cpu time            0.03 seconds
NOTE: PROCEDURE HTTP used (Total process time):
      real time           0.03 seconds
      cpu time            0.00 seconds
NOTE: 401 Unauthorized

Click the Hot Fix tab in this note to access the hot fix for this issue.

Install the hot fix and follow the post-installation instructions to copy the relevant files from the SASHome directory to SAS-configuration-directory.

To verify whether this hot fix is already installed, see SAS KB0036131, "Using the ViewRegistry Report and other methods to determine the SAS® 9.2 and later software releases and hot fixes that are installed." If the hot fix is already installed but the problem still occurs, be sure to follow the post-installation instructions to copy the relevant files from the SASHome directory to SAS-configuration-directory. Then execute the appropriate file (either emi_init.sh or emi_init.bat) or if the SAS Environment Manager Service Architecture is already initialized, no further action is required.



Operating System and Release Information

Product FamilyProductSystemProduct ReleaseSAS Release
ReportedFixed*ReportedFixed*
SAS SystemSAS Environment Manager Enablement Kit ServerLinux for x642.19.4 TS1M2
Solaris for x642.19.4 TS1M2
64-bit Enabled Solaris2.19.4 TS1M2
HP-UX IPF2.19.4 TS1M2
64-bit Enabled AIX2.19.4 TS1M2
Microsoft® Windows® for x642.19.4 TS1M2
* 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.