<?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: Initialising the Service Architecture in Administration and Deployment</title>
    <link>https://communities.sas.com/t5/Administration-and-Deployment/Initialising-the-Service-Architecture/m-p/901903#M27483</link>
    <description>&lt;P&gt;Sadly, restarting the EV server and agents as described in the troubleshooting documentation made no difference.&lt;/P&gt;</description>
    <pubDate>Tue, 07 Nov 2023 15:46:08 GMT</pubDate>
    <dc:creator>Nigel_Pain</dc:creator>
    <dc:date>2023-11-07T15:46:08Z</dc:date>
    <item>
      <title>Initialising the Service Architecture</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/Initialising-the-Service-Architecture/m-p/901422#M27475</link>
      <description>&lt;P&gt;Windows 2019,&amp;nbsp;SAS 9.4M7,&amp;nbsp;VA 7.5&lt;/P&gt;
&lt;P&gt;We're looking to initialise the Service Architecture Framework in our environment (for some reason this wasn't done on installation), as documented here:&lt;/P&gt;
&lt;P&gt;&lt;A href="https://documentation.sas.com/doc/en/evcdc/2.5_M1/evug/n0532grdsxrb63n1429imhgv4yx1.htm" target="_blank" rel="noopener"&gt;Initializing and Enabling the Service Architecture&lt;/A&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;When running&lt;/P&gt;
&lt;P&gt;validate.bat --level 2&lt;/P&gt;
&lt;P&gt;in config/Lev1&lt;SPAN&gt;/Web/SASEnvironmentManager/emi-framework/bin I always get the response as follows:&lt;/SPAN&gt;&lt;/P&gt;
&lt;PRE&gt;Starting level 1 validation...
Level 1 validation completed with 0 error(s)
Starting extended level 2 validation (this could take a while)...

Service Architecture validation completed with 1 error(s)
Errors:
        1) The SAS Environment Manager Server is unable to process additional tasks at this time. This may be due to high change request volume. If the server has recently been (re)started, it may be synchronizing with its Agents. This process could take up to an hour.
Please try again at a later time to validate your environment.&lt;/PRE&gt;
&lt;P&gt;&lt;SPAN&gt;It doesn't matter when I try this, and how busy (or otherwise) the server is. It produces a couple of log files but there doesn't seem to be anything else useful in them (see attached). Does anyone have any insights?&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Thanks.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 03 Nov 2023 16:02:21 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/Initialising-the-Service-Architecture/m-p/901422#M27475</guid>
      <dc:creator>Nigel_Pain</dc:creator>
      <dc:date>2023-11-03T16:02:21Z</dc:date>
    </item>
    <item>
      <title>Re: Initialising the Service Architecture</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/Initialising-the-Service-Architecture/m-p/901470#M27476</link>
      <description>This means we sent an update to Environment Manager and it wasn't updated before the timeout it will stop to prevent future calls from failing. &lt;BR /&gt;The server.log file for the Environment Manager server might have more information on what's happening. I might start by stopping the Environment Manager Server and agents on all the hosts, starting back up the server and then following the steps under the section "The SAS Environment Manager agent starts, but does not send data."  in the documentation linked below to reset the agent connections to the server.&lt;BR /&gt;&lt;BR /&gt;Resolving Problems with SAS Environment Manager Agents&lt;BR /&gt;&lt;A href="https://go.documentation.sas.com/doc/en/bicdc/9.4/evug/n07iigw9mfj4eln1nyktpc3p1x3a.htm" target="_blank"&gt;https://go.documentation.sas.com/doc/en/bicdc/9.4/evug/n07iigw9mfj4eln1nyktpc3p1x3a.htm&lt;/A&gt;</description>
      <pubDate>Fri, 03 Nov 2023 19:16:48 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/Initialising-the-Service-Architecture/m-p/901470#M27476</guid>
      <dc:creator>gwootton</dc:creator>
      <dc:date>2023-11-03T19:16:48Z</dc:date>
    </item>
    <item>
      <title>Re: Initialising the Service Architecture</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/Initialising-the-Service-Architecture/m-p/901700#M27481</link>
      <description>&lt;P&gt;Thanks Greg, I'll maybe give that a go. I quite often have to follow that guidance for one of the platforms (compute) after restarting so I'm used to that one. Never have found if there's an agent.encrypt.lock file though - the service is run by the local system account so there's no C:\users\&lt;EM&gt;&lt;SPAN class="xis-userSuppliedValue"&gt;user-name&lt;/SPAN&gt;&lt;/EM&gt;&lt;SPAN&gt;\AppData\Local\Temp directory. But just removing the data directory seems to do the job.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Looking at the server.log for EV server, the validate seems to end with this warning:&lt;/SPAN&gt;&lt;/P&gt;
&lt;BLOCKQUOTE&gt;
&lt;P&gt;03-11-2023 15:42:36,142 GMT WARN [tomcat-http--17] [org.hyperic.hq.bizapp.server.session.AIBossImpl@442] toggleRuntimeScan called for non-server type=3:10559&lt;/P&gt;
&lt;/BLOCKQUOTE&gt;
&lt;P&gt;&lt;SPAN&gt;No idea what it means!&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 06 Nov 2023 11:09:57 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/Initialising-the-Service-Architecture/m-p/901700#M27481</guid>
      <dc:creator>Nigel_Pain</dc:creator>
      <dc:date>2023-11-06T11:09:57Z</dc:date>
    </item>
    <item>
      <title>Re: Initialising the Service Architecture</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/Initialising-the-Service-Architecture/m-p/901903#M27483</link>
      <description>&lt;P&gt;Sadly, restarting the EV server and agents as described in the troubleshooting documentation made no difference.&lt;/P&gt;</description>
      <pubDate>Tue, 07 Nov 2023 15:46:08 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/Initialising-the-Service-Architecture/m-p/901903#M27483</guid>
      <dc:creator>Nigel_Pain</dc:creator>
      <dc:date>2023-11-07T15:46:08Z</dc:date>
    </item>
    <item>
      <title>Re: Initialising the Service Architecture</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/Initialising-the-Service-Architecture/m-p/901904#M27484</link>
      <description>I'd engage technical support then so we can take a look at the logs from the validator and Environment Manager.</description>
      <pubDate>Tue, 07 Nov 2023 15:55:30 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/Initialising-the-Service-Architecture/m-p/901904#M27484</guid>
      <dc:creator>gwootton</dc:creator>
      <dc:date>2023-11-07T15:55:30Z</dc:date>
    </item>
    <item>
      <title>Re: Initialising the Service Architecture</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/Initialising-the-Service-Architecture/m-p/901914#M27485</link>
      <description>&lt;P&gt;Yes, that was going to be my next step. Unlikely to come to you though. Will be Marlow, initially at least.&lt;/P&gt;</description>
      <pubDate>Tue, 07 Nov 2023 16:13:50 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/Initialising-the-Service-Architecture/m-p/901914#M27485</guid>
      <dc:creator>Nigel_Pain</dc:creator>
      <dc:date>2023-11-07T16:13:50Z</dc:date>
    </item>
  </channel>
</rss>

