<?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 RIM Node Connectivity Issue in Management &amp; Governance</title>
    <link>https://community.qlik.com/t5/Management-Governance/RIM-Node-Connectivity-Issue/m-p/108676#M1744</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Techie,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have upgraded Qlik site from April 2018 to June 2018, after that my reloads are getting failed scheduler node. I am writing down my inputs which can help to find the root cause:&lt;/P&gt;&lt;P&gt;1. firewall is down on central node and rim node.&lt;/P&gt;&lt;P&gt;2. Symantec anti virus is installed on same day of upgrade.&lt;/P&gt;&lt;P&gt;On scheduler node,logs states below error:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Exception encountered when fetching app migration hash, still trying. Failed attempts: 64130 No connection could be made because the target machine actively refused it 10.XX.XX.XX:4545↵↓Unable to connect to the remote server &lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&lt;BR /&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;I have checked on rim node, port 4545 is getting utilized by node.exe service which we installed to host web page.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If I make central node a master and slave my reloads work fine and when I make it Master only all task get failed.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please help to find out the root cause.&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Rohit&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sat, 08 Sep 2018 17:09:02 GMT</pubDate>
    <dc:creator>rohitk1609</dc:creator>
    <dc:date>2018-09-08T17:09:02Z</dc:date>
    <item>
      <title>RIM Node Connectivity Issue</title>
      <link>https://community.qlik.com/t5/Management-Governance/RIM-Node-Connectivity-Issue/m-p/108676#M1744</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Techie,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have upgraded Qlik site from April 2018 to June 2018, after that my reloads are getting failed scheduler node. I am writing down my inputs which can help to find the root cause:&lt;/P&gt;&lt;P&gt;1. firewall is down on central node and rim node.&lt;/P&gt;&lt;P&gt;2. Symantec anti virus is installed on same day of upgrade.&lt;/P&gt;&lt;P&gt;On scheduler node,logs states below error:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Exception encountered when fetching app migration hash, still trying. Failed attempts: 64130 No connection could be made because the target machine actively refused it 10.XX.XX.XX:4545↵↓Unable to connect to the remote server &lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&lt;BR /&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;I have checked on rim node, port 4545 is getting utilized by node.exe service which we installed to host web page.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If I make central node a master and slave my reloads work fine and when I make it Master only all task get failed.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please help to find out the root cause.&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Rohit&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 08 Sep 2018 17:09:02 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Management-Governance/RIM-Node-Connectivity-Issue/m-p/108676#M1744</guid>
      <dc:creator>rohitk1609</dc:creator>
      <dc:date>2018-09-08T17:09:02Z</dc:date>
    </item>
    <item>
      <title>Re: RIM Node Connectivity Issue</title>
      <link>https://community.qlik.com/t5/Management-Governance/RIM-Node-Connectivity-Issue/m-p/1547731#M12670</link>
      <description>&lt;P&gt;I think you mean June 18&amp;nbsp; to&amp;nbsp; Abril 18? Or you downgraded? Anyways, I guess that error you got it from the repository logs, that normally means that something is wrong with the engine or the migration service, I would try to restart the engine and dispatcher service, and see if that error gets clear. Without engine, the scheduler won't be able to execute/reload tasks.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;BR&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Gio&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 21 Feb 2019 20:38:08 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Management-Governance/RIM-Node-Connectivity-Issue/m-p/1547731#M12670</guid>
      <dc:creator>Giuseppe_Novello</dc:creator>
      <dc:date>2019-02-21T20:38:08Z</dc:date>
    </item>
    <item>
      <title>Re: RIM Node Connectivity Issue</title>
      <link>https://community.qlik.com/t5/Management-Governance/RIM-Node-Connectivity-Issue/m-p/1576041#M13464</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.qlik.com/t5/user/viewprofilepage/user-id/16339"&gt;@rohitk1609&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Did you ever find a solution to this? Encountering same issue&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks,&lt;BR /&gt;Mark&lt;/P&gt;</description>
      <pubDate>Thu, 02 May 2019 16:29:22 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Management-Governance/RIM-Node-Connectivity-Issue/m-p/1576041#M13464</guid>
      <dc:creator>mjperreault</dc:creator>
      <dc:date>2019-05-02T16:29:22Z</dc:date>
    </item>
    <item>
      <title>Re: RIM Node Connectivity Issue</title>
      <link>https://community.qlik.com/t5/Management-Governance/RIM-Node-Connectivity-Issue/m-p/1576049#M13465</link>
      <description>I fixed it. I reinstalled Qlik Sense on Rim node and then it worked fine.</description>
      <pubDate>Thu, 02 May 2019 16:45:18 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Management-Governance/RIM-Node-Connectivity-Issue/m-p/1576049#M13465</guid>
      <dc:creator>rohitk1609</dc:creator>
      <dc:date>2019-05-02T16:45:18Z</dc:date>
    </item>
  </channel>
</rss>

