<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Environment Manager Service Architecure / APM Initialization Issue for SAS 9.4 M3 in Administration and Deployment</title>
    <link>https://communities.sas.com/t5/Administration-and-Deployment/Environment-Manager-Service-Architecure-APM-Initialization-Issue/m-p/516464#M15095</link>
    <description>&lt;P&gt;You can try running emi_init.sh with the "-v" [verbose] option which should produce some more logging info.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If you happen to have one or more Windows Explorer windows up and viewing this directory structure at the time you run emi_init.sh, there have been reports of Windows Explorer getting in the way of the script's ability to manage these directories.&amp;nbsp; However, I'm doubting that's your issue since it appears you have two distinct directories giving you trouble.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If you've double-checked that the directories exist and are accessible, have rerun the command with no Windows Explorer windows up, and the -v option doesn't yield something obvious to correct, then you'll want to open up a track with Tech Support.&lt;/P&gt;</description>
    <pubDate>Tue, 27 Nov 2018 19:35:59 GMT</pubDate>
    <dc:creator>Mark_sas</dc:creator>
    <dc:date>2018-11-27T19:35:59Z</dc:date>
    <item>
      <title>Environment Manager Service Architecure / APM Initialization Issue for SAS 9.4 M3</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/Environment-Manager-Service-Architecure-APM-Initialization-Issue/m-p/516016#M15079</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Hi Guys,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Would like to check if anyone has encountered this issue in initializing Environment Manager Service Architecture (SAS 9.4M3)&lt;/P&gt;&lt;P&gt;This is a multi machine setup (Metadata, AML Compute (where emi-framework is), VA Compute, Mid-Tier)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We have&amp;nbsp; done ./validate.sh –level 2 successfully however for the next step, it is failing&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;./emi_init.sh -i&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;emiInit_20181126_174219.log&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;2018-11-26 17:44:55,633 ERROR [main] [evKitInstaller] - SAS execution of [verifyProperties.sas] failed with rc 252&lt;/P&gt;&lt;P&gt;2018-11-26 17:44:55,633 ERROR [main] [evKitInstaller] - verifyProperties.sas failed with return code [252]. Check verifyProperties_20181126_174446.sas.log for details.&lt;/P&gt;&lt;P&gt;2018-11-26 17:44:55,634 INFO&amp;nbsp; [main] [evKitInstaller] - Level 2 validation completed with 1 error(s) in 8.838 sec&lt;/P&gt;&lt;P&gt;2018-11-26 17:44:55,634 ERROR [main] [evKitInstaller] - Service Architecture validation failed. ev_kit_installer cannot continue. Errors are:&lt;/P&gt;&lt;P&gt;2018-11-26 17:44:55,635 ERROR [main] [evKitInstaller] - &amp;nbsp;&amp;nbsp;&amp;nbsp; verifyProperties.sas failed with return code [252]. Check verifyProperties_20181126_174446.sas.log for details.&lt;/P&gt;&lt;P&gt;2018-11-26 17:44:55,635 ERROR [main] [evKitInstaller] - Stopping execution&lt;/P&gt;&lt;P&gt;2018-11-26 17:44:55,636 ERROR [main] [emiInit] - Error rc = [2] running evKitInstaller [[-k, ALL, -x, -q, -f]], check log. May need to rerun with -f&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Upon checking the logs we have found this lines which could be the issue:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;verifyProperties_20181126_174446.lst&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Directory Exists?&amp;nbsp; FAILED&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; /sasconf/AML63/Config/Lev1/Web/SASEnvironmentMa...&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; ERR:Specified Directory NOT a directory.&amp;nbsp; File Name/Path (Last 200 Chars):/sasconf/AML63/Config/Lev1/Web/SASEnvironmentManager/emi-framework/Datamart/evdmTemp/&lt;/P&gt;&lt;P&gt;Directory Exists?&amp;nbsp; FAILED&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; /sasconf/AML63/Config/Lev1/Web/SASEnvironmentMa...&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; ERR:Specified Directory NOT a directory.&amp;nbsp; File Name/Path (Last 200 Chars):/sasconf/AML63/Config/Lev1/Web/SASEnvironmentManager/emi-framework/LandingZone&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We have checked and verified that above 2 folders are existing (actual folders and not symlinks and with correct permission in the emi-framework) but seems the script emi_init.sh &amp;nbsp;could not find it.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Any suggestion what I can check?&lt;/P&gt;&lt;P&gt;Thanks in advance,&lt;/P&gt;</description>
      <pubDate>Mon, 26 Nov 2018 15:30:22 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/Environment-Manager-Service-Architecure-APM-Initialization-Issue/m-p/516016#M15079</guid>
      <dc:creator>tlorel</dc:creator>
      <dc:date>2018-11-26T15:30:22Z</dc:date>
    </item>
    <item>
      <title>Re: Environment Manager Service Architecure / APM Initialization Issue for SAS 9.4 M3</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/Environment-Manager-Service-Architecure-APM-Initialization-Issue/m-p/516464#M15095</link>
      <description>&lt;P&gt;You can try running emi_init.sh with the "-v" [verbose] option which should produce some more logging info.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If you happen to have one or more Windows Explorer windows up and viewing this directory structure at the time you run emi_init.sh, there have been reports of Windows Explorer getting in the way of the script's ability to manage these directories.&amp;nbsp; However, I'm doubting that's your issue since it appears you have two distinct directories giving you trouble.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If you've double-checked that the directories exist and are accessible, have rerun the command with no Windows Explorer windows up, and the -v option doesn't yield something obvious to correct, then you'll want to open up a track with Tech Support.&lt;/P&gt;</description>
      <pubDate>Tue, 27 Nov 2018 19:35:59 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/Environment-Manager-Service-Architecure-APM-Initialization-Issue/m-p/516464#M15095</guid>
      <dc:creator>Mark_sas</dc:creator>
      <dc:date>2018-11-27T19:35:59Z</dc:date>
    </item>
  </channel>
</rss>

