Hi ,
I am trying to Initializing SAS Environment Manager Service Architecture Framework.
Though I didnt receive any errors when running "/sascommon/SAS/SASConfig/grid1/Lev1/Web/SASEnvironmentManager/emi-framework/bin/validate.sh --level 2", I got the following error when ran the below command:"./emi_init.sh -i"
========================================================================================
[sas@sesklsasgrndev01 bin]$ ./emi_init.sh -i
Service Architecture Initialization Utility - Wed May 16 18:52:24 CEST 2018
Validating environment...
Validating external connections...
Starting initialization...
Importing SPK package(s) to SAS Metadata server...
Unable to set the URL of the Stored Process web application (RC=253)
Service Architecture HTTP Platform Service Utility - Wed May 16 18:53:40 CEST 2018
Command failed with RC 253
There was a problem creating HTTP checks (rc [2]). Check the log file.
================================================================================
Please help me to resolve the issue.
Thanks
Menaka B
Hi. Please see if this SAS Note helps you, http://support.sas.com/kb/61/845.html. If it does not help you resolve your issue, I'd suggest opening a ticket with SAS Technical Support.
Hi,
Thankyou for your reply.
Following the hotfix installation(C1N001), I can get past through the step "./emi_init.sh -i" without any errors.
But now receiving a different error when Initializing the APM. Attached the apminit log (Error: Error: Could not find or load main class groovy.lang.GroovyShell) for reference.
[sas@sesklsasgrndev01 bin]$ ./apm_init.sh
Service Architecture APM Initialization - Fri May 18 15:17:34 CEST 2018
Validating environment...
Initializing APM...
Initializing sesklsasgrndev01.emea.astrazeneca.net...
Initialize failed for sesklsasgrndev01.emea.astrazeneca.net
Initializing sesklsasmetdev01.emea.astrazeneca.net...
Initialize failed for sesklsasmetdev01.emea.astrazeneca.net
Initializing sesklsasmiddev01.emea.astrazeneca.net...
Initialize failed for sesklsasmiddev01.emea.astrazeneca.net
Initializing sesklsasmiddev02.emea.astrazeneca.net...
Initialize failed for sesklsasmiddev02.emea.astrazeneca.net
Initializing sesksasgcdev01.emea.astrazeneca.net...
Initialize failed for sesksasgcdev01.emea.astrazeneca.net
APM was initialized with [5] warning(s). Check apmInit_20180518_151733.log for details
Any idea on how to resolve this.
Thanks
Menaka
Did you perform the post installation steps in the hot fix? If so, what goovy do you have listed when you run ls -la on Lev1/Web/Scripts/AppServer/lib?
Yes,I ran the post installation scripts as well. Following is the list of files under "/sascommon/SAS/SASConfig/grid1/Lev1/Web/Scripts/AppServer/lib"
[sas@sesklsasgrndev01 lib]$ ls -la
total 25040
drwxr-xr-x. 2 sas sas 4096 Feb 27 17:55 .
drwxr-xr-x. 8 sas sas 4096 Feb 27 17:55 ..
-rw-r--r--. 1 sas sas 1289806 Jun 9 2011 ant.jar
-rw-r--r--. 1 sas sas 11734 Jun 9 2011 ant-launcher.jar
-rw-r--r--. 1 sas sas 4467 Jun 9 2011 aopalliance.jar
-rw-r--r--. 1 sas sas 41123 Jul 15 2011 commons-cli.jar
-rw-r--r--. 1 sas sas 588337 Oct 11 2017 commons-collections.jar
-rw-r--r--. 1 sas sas 109043 Jun 9 2011 commons-io.jar
-rw-r--r--. 1 sas sas 207723 Oct 11 2017 commons-lang.jar
-rw-r--r--. 1 sas sas 60841 Jun 9 2011 commons-logging.jar
-rw-r--r--. 1 sas sas 2783145 Jun 9 2011 groovy-all.jar
-rw-r--r--. 1 sas sas 352254 Mar 2 2012 httpclient-4.1.2.jar
-rw-r--r--. 1 sas sas 181201 Mar 2 2012 httpcore-4.1.3.jar
-rw-r--r--. 1 sas sas 358085 Jun 9 2011 log4j.jar
-rw-r--r--. 1 sas sas 20639 Jun 12 2012 log4j.over.slf4j_1.6.4.jar
-rw-r--r--. 1 sas sas 449472 Feb 27 17:55 sas.antlr.jar
-rw-r--r--. 1 sas sas 1748782 Oct 11 2017 sas.appserver.config.jar
-rw-r--r--. 1 sas sas 993535 Oct 11 2017 sas.core.jar
-rw-r--r--. 1 sas sas 105134 Feb 27 17:55 sas.entities.jar
-rw-r--r--. 1 sas sas 82569 Feb 27 17:55 sas.framework.core.jar
-rw-r--r--. 1 sas sas 214649 Sep 4 2012 sas.launcher.jar
-rw-r--r--. 1 sas sas 7189380 Oct 11 2017 sas.oma.joma.rmt.jar
-rw-r--r--. 1 sas sas 386264 Oct 11 2017 sas.oma.omi.jar
-rw-r--r--. 1 sas sas 6588 Oct 11 2017 sas.security.sspi.jar
-rw-r--r--. 1 sas sas 31250 Feb 27 17:55 sas.svc.cache.jar
-rw-r--r--. 1 sas sas 2286471 Oct 11 2017 sas.svc.connection.jar
-rw-r--r--. 1 sas sas 4660107 Feb 27 17:55 sas.svc.core.jar
-rw-r--r--. 1 sas sas 51536 Feb 27 17:55 sas.svc.sec.login.jar
-rw-r--r--. 1 sas sas 479286 Feb 27 17:55 sas.svc.storedprocess.jar
-rw-r--r--. 1 sas sas 281482 Feb 27 17:55 sas.svc.webdav.jar
-rw-r--r--. 1 sas sas 25962 Jun 12 2012 slf4j.api_1.6.4.jar
-rw-r--r--. 1 sas sas 392124 Oct 11 2017 velocity.jar
The SAS Users Group for Administrators (SUGA) is open to all SAS administrators and architects who install, update, manage or maintain a SAS deployment.