<?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 June 2017 upgrade problems in Management &amp; Governance</title>
    <link>https://community.qlik.com/t5/Management-Governance/Qlik-June-2017-upgrade-problems/m-p/1350584#M10115</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We didn't. Service cluster settings were not editable so we did a fresh install to set up the root folder. Fresh install was quite painful so I hope someone from Qlik or community can come up with a workaround and provide explanation for anyone else having this kind of issue.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 28 Jul 2017 07:06:39 GMT</pubDate>
    <dc:creator>ahorvat</dc:creator>
    <dc:date>2017-07-28T07:06:39Z</dc:date>
    <item>
      <title>Qlik June 2017 upgrade problems</title>
      <link>https://community.qlik.com/t5/Management-Governance/Qlik-June-2017-upgrade-problems/m-p/1350582#M10113</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;We're experiencing several problems after June 2017 upgrade:&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;&lt;SPAN style="font-size: 10pt;"&gt;&lt;STRONG&gt;The app you specified could not be found&lt;/STRONG&gt;&lt;BR /&gt;&lt;IMG alt="App not found.png" class="jive-image image-1" src="/legacyfs/online/170975_App not found.png" style="height: auto;" /&gt;&lt;BR /&gt;Previously we changed default app directory to "D:\QS_Apps" by editing settings.ini file with new row DocumentDirectory=D:\QS_Apps ([Settings 7] above and blank row below are present, it all worked before June 2017 upgrade).&lt;BR /&gt;After the upgrade it's like settings.ini file is completely ignored. We tried deleting that file, letting QS create new one and then editing it again. No change - existing apps in non-default location are not found and new applications are created in the default location instead of the one in settings.ini file&lt;BR /&gt;&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN style="font-size: 10pt;"&gt;&lt;STRONG&gt;QMC -&amp;gt; Engines is not editable anymore&lt;/STRONG&gt;. Whatever setting we try changing "Apply" button is grayed out. Help page states that "Apply" button will not be available until all mandatory fields are filled however all fields that we see are filled.&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN style="font-size: 10pt;"&gt;&lt;STRONG&gt;App storage directory field is not visible&lt;/STRONG&gt; even though it's mentioned in the &lt;A href="http://help.qlik.com/en-US/sense/June2017/Subsystems/ManagementConsole/Content/edit-engine.htm"&gt;documentation&lt;/A&gt;&lt;/SPAN&gt;&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What else we tried:&lt;/P&gt;&lt;P&gt;- restart of all Qlik services&lt;/P&gt;&lt;P&gt;- restart of the server&lt;/P&gt;&lt;P&gt;- moving settings.ini file away and then back&lt;/P&gt;&lt;P&gt;- repair of the intallation (both initial upgrade and repair were completed successfully)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Note: Standard mode is disabled in the Engine if that might be connected somehow to this situation&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 21 Jul 2017 08:53:20 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Management-Governance/Qlik-June-2017-upgrade-problems/m-p/1350582#M10113</guid>
      <dc:creator>ahorvat</dc:creator>
      <dc:date>2017-07-21T08:53:20Z</dc:date>
    </item>
    <item>
      <title>Re: Qlik June 2017 upgrade problems</title>
      <link>https://community.qlik.com/t5/Management-Governance/Qlik-June-2017-upgrade-problems/m-p/1350583#M10114</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I had the same issue last week.&amp;nbsp; I had to restore a snapshot of the previous version.&amp;nbsp; Did you find a solution?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 27 Jul 2017 18:09:43 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Management-Governance/Qlik-June-2017-upgrade-problems/m-p/1350583#M10114</guid>
      <dc:creator>pat_buchanan</dc:creator>
      <dc:date>2017-07-27T18:09:43Z</dc:date>
    </item>
    <item>
      <title>Re: Qlik June 2017 upgrade problems</title>
      <link>https://community.qlik.com/t5/Management-Governance/Qlik-June-2017-upgrade-problems/m-p/1350584#M10115</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We didn't. Service cluster settings were not editable so we did a fresh install to set up the root folder. Fresh install was quite painful so I hope someone from Qlik or community can come up with a workaround and provide explanation for anyone else having this kind of issue.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 28 Jul 2017 07:06:39 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Management-Governance/Qlik-June-2017-upgrade-problems/m-p/1350584#M10115</guid>
      <dc:creator>ahorvat</dc:creator>
      <dc:date>2017-07-28T07:06:39Z</dc:date>
    </item>
    <item>
      <title>Re: Qlik June 2017 upgrade problems</title>
      <link>https://community.qlik.com/t5/Management-Governance/Qlik-June-2017-upgrade-problems/m-p/1350585#M10116</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Have you tried changing the path&amp;nbsp; in the settings.ini from D:\QS_Apps to the UNC path (\\server\d$\QS_apps)&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 28 Jul 2017 12:43:01 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Management-Governance/Qlik-June-2017-upgrade-problems/m-p/1350585#M10116</guid>
      <dc:creator>image242</dc:creator>
      <dc:date>2017-07-28T12:43:01Z</dc:date>
    </item>
  </channel>
</rss>

