<?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: SAS server IP address change in Administration and Deployment</title>
    <link>https://communities.sas.com/t5/Administration-and-Deployment/SAS-server-IP-address-change/m-p/890463#M27165</link>
    <description>&lt;P&gt;This sounds very similar to&amp;nbsp;&lt;A href="https://communities.sas.com/t5/Administration-and-Deployment/object-spwaner-startup-issue/td-p/679118" target="_blank"&gt;Solved: object spwaner startup issue - SAS Support Communities&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;
&lt;P&gt;Compare your SAS\Config\Levx\ObjectSpawner\Objectspawner.sh&amp;nbsp; (or .bat if you are running on Windows)&lt;/P&gt;
&lt;P&gt;as well as the metadataConfig.xml file in the same directory, as well as SAS\Config\Levx\SASMeta\MetadataServer\omaconfig.xml&amp;nbsp; and verify if you have IP addresses or hostnames listed, and also verify network connectivitity via ping as expected between the metadata server and the machines where your objectspawners are intended to run.&lt;BR /&gt;&lt;BR /&gt;While it's not my area, I believe the proper way to do this sort of migration is to use the SAS Migration Utility as described in&amp;nbsp;&lt;A href="https://go.documentation.sas.com/doc/en/bicdc/9.4/bimig/titlepage.htm" target="_blank"&gt;SAS Help Center: SAS® 9.4 Intelligence Platform: Migration Guide, Second Edition&lt;/A&gt;&amp;nbsp;rather than disk cloning.&amp;nbsp;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Carl Sommer&lt;/P&gt;</description>
    <pubDate>Tue, 22 Aug 2023 19:24:46 GMT</pubDate>
    <dc:creator>carl_sommer</dc:creator>
    <dc:date>2023-08-22T19:24:46Z</dc:date>
    <item>
      <title>SAS server IP address change</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/SAS-server-IP-address-change/m-p/890453#M27164</link>
      <description>&lt;P&gt;Hi all,&lt;BR /&gt;Our SAS server was moved to a new machine with a new IP address over the weekend. And after the move, we can't connect to the server anymore from Enterprise Guide.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Out IT insists that the old server is cloned to the new server (hard disk to hard disk copy), so anything stays the same except for the server's IP address But we finds some of the services/servers was not initiated properly, e.g., SAS Environment Manager is not up, and we found Object Spawner is "stopped".&amp;nbsp;&lt;BR /&gt;Anyone has has idea what might go wrong? Thanks!&lt;/P&gt;</description>
      <pubDate>Tue, 22 Aug 2023 18:37:08 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/SAS-server-IP-address-change/m-p/890453#M27164</guid>
      <dc:creator>Dana_Wu</dc:creator>
      <dc:date>2023-08-22T18:37:08Z</dc:date>
    </item>
    <item>
      <title>Re: SAS server IP address change</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/SAS-server-IP-address-change/m-p/890463#M27165</link>
      <description>&lt;P&gt;This sounds very similar to&amp;nbsp;&lt;A href="https://communities.sas.com/t5/Administration-and-Deployment/object-spwaner-startup-issue/td-p/679118" target="_blank"&gt;Solved: object spwaner startup issue - SAS Support Communities&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;
&lt;P&gt;Compare your SAS\Config\Levx\ObjectSpawner\Objectspawner.sh&amp;nbsp; (or .bat if you are running on Windows)&lt;/P&gt;
&lt;P&gt;as well as the metadataConfig.xml file in the same directory, as well as SAS\Config\Levx\SASMeta\MetadataServer\omaconfig.xml&amp;nbsp; and verify if you have IP addresses or hostnames listed, and also verify network connectivitity via ping as expected between the metadata server and the machines where your objectspawners are intended to run.&lt;BR /&gt;&lt;BR /&gt;While it's not my area, I believe the proper way to do this sort of migration is to use the SAS Migration Utility as described in&amp;nbsp;&lt;A href="https://go.documentation.sas.com/doc/en/bicdc/9.4/bimig/titlepage.htm" target="_blank"&gt;SAS Help Center: SAS® 9.4 Intelligence Platform: Migration Guide, Second Edition&lt;/A&gt;&amp;nbsp;rather than disk cloning.&amp;nbsp;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Carl Sommer&lt;/P&gt;</description>
      <pubDate>Tue, 22 Aug 2023 19:24:46 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/SAS-server-IP-address-change/m-p/890463#M27165</guid>
      <dc:creator>carl_sommer</dc:creator>
      <dc:date>2023-08-22T19:24:46Z</dc:date>
    </item>
  </channel>
</rss>

