<?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: QlikSense November2018 Path1 Section Access Report failed in App Development</title>
    <link>https://community.qlik.com/t5/App-Development/QlikSense-November2018-Path1-Section-Access-Report-failed/m-p/1525300#M37741</link>
    <description>&lt;P&gt;Thank you ... its helped ...&lt;/P&gt;&lt;P&gt;But want to know what this is not happened in earlier versions of Qlik&lt;/P&gt;</description>
    <pubDate>Wed, 02 Jan 2019 08:41:42 GMT</pubDate>
    <dc:creator>srinu_qliksense</dc:creator>
    <dc:date>2019-01-02T08:41:42Z</dc:date>
    <item>
      <title>QlikSense November2018 Path1 Section Access Report failed</title>
      <link>https://community.qlik.com/t5/App-Development/QlikSense-November2018-Path1-Section-Access-Report-failed/m-p/1525075#M37720</link>
      <description>&lt;P&gt;Hi ,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am&amp;nbsp; facing issue in Qlik November 2018 Patch 1, Not in Earlier Versions.&lt;/P&gt;&lt;P&gt;I&amp;nbsp; am using section access for one report.&lt;/P&gt;&lt;P&gt;I am able to load(run) the report from hub and it is successfully completed.&lt;/P&gt;&lt;P&gt;After&amp;nbsp; that&amp;nbsp; scheduled the report from TASK Manger window. The Report is failed with "Execution Failed" (log message).&lt;/P&gt;&lt;P&gt;If I Comment the section access part then the report running the successfully.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 31 Dec 2018 10:42:22 GMT</pubDate>
      <guid>https://community.qlik.com/t5/App-Development/QlikSense-November2018-Path1-Section-Access-Report-failed/m-p/1525075#M37720</guid>
      <dc:creator>srinu_qliksense</dc:creator>
      <dc:date>2018-12-31T10:42:22Z</dc:date>
    </item>
    <item>
      <title>Re: QlikSense November2018 Path1 Section Access Report failed</title>
      <link>https://community.qlik.com/t5/App-Development/QlikSense-November2018-Path1-Section-Access-Report-failed/m-p/1525115#M37721</link>
      <description>&lt;P&gt;Make sure to include the user INTERNAL\SA_SCHEDULER in the section access table with ADMIN access. Otherwise the document can not be reloaded succesfully using a reload task.&lt;/P&gt;</description>
      <pubDate>Mon, 31 Dec 2018 14:45:25 GMT</pubDate>
      <guid>https://community.qlik.com/t5/App-Development/QlikSense-November2018-Path1-Section-Access-Report-failed/m-p/1525115#M37721</guid>
      <dc:creator>Gysbert_Wassenaar</dc:creator>
      <dc:date>2018-12-31T14:45:25Z</dc:date>
    </item>
    <item>
      <title>Re: QlikSense November2018 Path1 Section Access Report failed</title>
      <link>https://community.qlik.com/t5/App-Development/QlikSense-November2018-Path1-Section-Access-Report-failed/m-p/1525300#M37741</link>
      <description>&lt;P&gt;Thank you ... its helped ...&lt;/P&gt;&lt;P&gt;But want to know what this is not happened in earlier versions of Qlik&lt;/P&gt;</description>
      <pubDate>Wed, 02 Jan 2019 08:41:42 GMT</pubDate>
      <guid>https://community.qlik.com/t5/App-Development/QlikSense-November2018-Path1-Section-Access-Report-failed/m-p/1525300#M37741</guid>
      <dc:creator>srinu_qliksense</dc:creator>
      <dc:date>2019-01-02T08:41:42Z</dc:date>
    </item>
    <item>
      <title>Re: QlikSense November2018 Path1 Section Access Report failed</title>
      <link>https://community.qlik.com/t5/App-Development/QlikSense-November2018-Path1-Section-Access-Report-failed/m-p/1528654#M37986</link>
      <description>&lt;P&gt;Hi I experienced the same issue in November 18 patch 2.&amp;nbsp;&lt;/P&gt;&lt;P&gt;My Section Access is handled in an Excel-file and I noticed that I had an whitepace in the SA_SHEDULER USERID&amp;nbsp; cell, like this: "INTERNAL\SA_SCHEDULER ", when&amp;nbsp; removed the tailing whitepace to&amp;nbsp;&lt;SPAN&gt;"INTERNAL\SA_SCHEDULER"&amp;nbsp;then&lt;/SPAN&gt; the task ran successfully.&amp;nbsp;&lt;/P&gt;&lt;P&gt;This has not caused any problem in prior to November 18, so my guess is that Qlik Sense became more sensitive to whitespaces in excel in this release.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 09 Jan 2019 23:02:33 GMT</pubDate>
      <guid>https://community.qlik.com/t5/App-Development/QlikSense-November2018-Path1-Section-Access-Report-failed/m-p/1528654#M37986</guid>
      <dc:creator>Vegar</dc:creator>
      <dc:date>2019-01-09T23:02:33Z</dc:date>
    </item>
    <item>
      <title>Re: QlikSense November2018 Path1 Section Access Report failed</title>
      <link>https://community.qlik.com/t5/App-Development/QlikSense-November2018-Path1-Section-Access-Report-failed/m-p/1528748#M38000</link>
      <description>In the QS November 2018 release a change was implemented that makes it necessary to include the internal scheduler service account in the section access table. This was not necessary previously.</description>
      <pubDate>Thu, 10 Jan 2019 06:37:55 GMT</pubDate>
      <guid>https://community.qlik.com/t5/App-Development/QlikSense-November2018-Path1-Section-Access-Report-failed/m-p/1528748#M38000</guid>
      <dc:creator>Gysbert_Wassenaar</dc:creator>
      <dc:date>2019-01-10T06:37:55Z</dc:date>
    </item>
    <item>
      <title>Re: QlikSense November2018 Path1 Section Access Report failed</title>
      <link>https://community.qlik.com/t5/App-Development/QlikSense-November2018-Path1-Section-Access-Report-failed/m-p/1540532#M38998</link>
      <description>&lt;P&gt;This means Qlik is not backward compatible. I have to go and fix all my apps now. That sucks!&lt;/P&gt;&lt;P&gt;Does anybody what is Qlik's take on backward compatibility. I am going to file a support ticket issue with them anyway.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 06 Feb 2019 20:32:54 GMT</pubDate>
      <guid>https://community.qlik.com/t5/App-Development/QlikSense-November2018-Path1-Section-Access-Report-failed/m-p/1540532#M38998</guid>
      <dc:creator>mborsadw</dc:creator>
      <dc:date>2019-02-06T20:32:54Z</dc:date>
    </item>
    <item>
      <title>Re: QlikSense November2018 Path1 Section Access Report failed</title>
      <link>https://community.qlik.com/t5/App-Development/QlikSense-November2018-Path1-Section-Access-Report-failed/m-p/1540541#M38999</link>
      <description>&lt;P&gt;It depends on how you look at it.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;If you read the help chapter for section access from version 2.0 it states that the&amp;nbsp;&lt;SPAN&gt;INTERNAL\SA_SCHEDULER shold be included for execution in the QMC. I remember I had som issues due to not including the sheduler in 3.x&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;In this later release Qlik Sense have become more strict regarding this. The good thing is that from now on you can't forget without noticing it.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 06 Feb 2019 21:04:04 GMT</pubDate>
      <guid>https://community.qlik.com/t5/App-Development/QlikSense-November2018-Path1-Section-Access-Report-failed/m-p/1540541#M38999</guid>
      <dc:creator>Vegar</dc:creator>
      <dc:date>2019-02-06T21:04:04Z</dc:date>
    </item>
    <item>
      <title>Re: QlikSense November2018 Path1 Section Access Report failed</title>
      <link>https://community.qlik.com/t5/App-Development/QlikSense-November2018-Path1-Section-Access-Report-failed/m-p/1547058#M39381</link>
      <description>Qlik should have put this CHANGE into the Nov 18 release notes.</description>
      <pubDate>Wed, 20 Feb 2019 18:01:30 GMT</pubDate>
      <guid>https://community.qlik.com/t5/App-Development/QlikSense-November2018-Path1-Section-Access-Report-failed/m-p/1547058#M39381</guid>
      <dc:creator>stvegerton</dc:creator>
      <dc:date>2019-02-20T18:01:30Z</dc:date>
    </item>
  </channel>
</rss>

