<?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: Qlik Sense Repository service shutdown after change number of VM Cores in Management &amp; Governance</title>
    <link>https://community.qlik.com/t5/Management-Governance/Qlik-Sense-Repository-service-shutdown-after-changing-VM-Cores/m-p/32773#M617</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;This is what I was expecting, running well after restart, but it´s failing.&lt;/P&gt;&lt;P&gt;Now changed back to 4 cores and the problem is the same.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 15 Feb 2018 16:52:32 GMT</pubDate>
    <dc:creator>pablolabbe</dc:creator>
    <dc:date>2018-02-15T16:52:32Z</dc:date>
    <item>
      <title>Qlik Sense Repository service shutdown after changing VM Cores available</title>
      <link>https://community.qlik.com/t5/Management-Governance/Qlik-Sense-Repository-service-shutdown-after-changing-VM-Cores/m-p/32771#M615</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp; Have a customer running Qlik Sense November / 2017 on a Windows VM with 4 cores. After changing the number of cores to 8, the repository service doesn´t start anymore.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp; Found this message in the repository log. "Key not valid for use in specified state" and after that a "shutdown repository service" message.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp; Can the certificate and cryptographic keys used by Qlik Sense be invalidated by hardware changes l? Do I need to generate the certificates again ?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 15 Feb 2018 16:38:10 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Management-Governance/Qlik-Sense-Repository-service-shutdown-after-changing-VM-Cores/m-p/32771#M615</guid>
      <dc:creator>pablolabbe</dc:creator>
      <dc:date>2018-02-15T16:38:10Z</dc:date>
    </item>
    <item>
      <title>Re: Qlik Sense Repository service shutdown after change number of VM Cores</title>
      <link>https://community.qlik.com/t5/Management-Governance/Qlik-Sense-Repository-service-shutdown-after-changing-VM-Cores/m-p/32772#M616</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I already changed hardware (more CPU cores + RAM on VMWARE) but is was shutdown when doing this.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;everything runs well after restart..&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 15 Feb 2018 16:45:31 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Management-Governance/Qlik-Sense-Repository-service-shutdown-after-changing-VM-Cores/m-p/32772#M616</guid>
      <dc:creator>YoussefBelloum</dc:creator>
      <dc:date>2018-02-15T16:45:31Z</dc:date>
    </item>
    <item>
      <title>Re: Qlik Sense Repository service shutdown after change number of VM Cores</title>
      <link>https://community.qlik.com/t5/Management-Governance/Qlik-Sense-Repository-service-shutdown-after-changing-VM-Cores/m-p/32773#M617</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;This is what I was expecting, running well after restart, but it´s failing.&lt;/P&gt;&lt;P&gt;Now changed back to 4 cores and the problem is the same.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 15 Feb 2018 16:52:32 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Management-Governance/Qlik-Sense-Repository-service-shutdown-after-changing-VM-Cores/m-p/32773#M617</guid>
      <dc:creator>pablolabbe</dc:creator>
      <dc:date>2018-02-15T16:52:32Z</dc:date>
    </item>
    <item>
      <title>Re: Qlik Sense Repository service shutdown after change number of VM Cores</title>
      <link>https://community.qlik.com/t5/Management-Governance/Qlik-Sense-Repository-service-shutdown-after-changing-VM-Cores/m-p/32774#M618</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Can you share with us your Physical server model and hardware on which you created the VM ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;take a look at this:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.qlik.com/thread/235133"&gt;QMC QVS CPU Affinty missing cores&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 15 Feb 2018 16:57:20 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Management-Governance/Qlik-Sense-Repository-service-shutdown-after-changing-VM-Cores/m-p/32774#M618</guid>
      <dc:creator>YoussefBelloum</dc:creator>
      <dc:date>2018-02-15T16:57:20Z</dc:date>
    </item>
    <item>
      <title>Re: Qlik Sense Repository service shutdown after change number of VM Cores</title>
      <link>https://community.qlik.com/t5/Management-Governance/Qlik-Sense-Repository-service-shutdown-after-changing-VM-Cores/m-p/32775#M619</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The post is related to QlikView, not Qlik Sense.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;After all , I could recover the environment deleting the certificates (computer &amp;amp; user) and running an installation repair . After this procedure the repository services started and system is running ok.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Qlik Sense some time give us &lt;SPAN lang="en"&gt;a fright ! ugh&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you for your time !&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 15 Feb 2018 19:28:29 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Management-Governance/Qlik-Sense-Repository-service-shutdown-after-changing-VM-Cores/m-p/32775#M619</guid>
      <dc:creator>pablolabbe</dc:creator>
      <dc:date>2018-02-15T19:28:29Z</dc:date>
    </item>
  </channel>
</rss>

