<?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 REST API works in QS Desktop but fails in QS Server in Integration, Extension &amp; APIs</title>
    <link>https://community.qlik.com/t5/Integration-Extension-APIs/REST-API-works-in-QS-Desktop-but-fails-in-QS-Server/m-p/1404248#M8564</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;A href="https://community.qlik.com/space/2157"&gt;Qlik Sense - Data Connectivity&lt;/A&gt;‌&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have a REST API data connection configured that works fine in the QS Desktop version.&lt;/P&gt;&lt;P&gt;However, the same REST API, configured the same way, fails on QS Server (Sept 2017 release) during the data connection creation process (TEST CONNECTION) with error:&lt;/P&gt;&lt;P&gt;&lt;IMG class="jive-image image-1" src="https://community.qlik.com/legacyfs/online/181919_pastedImage_10.png" style="max-height: 900px; max-width: 1200px;" /&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #ff0000; font-size: 12pt;"&gt;Should a REST API data connection that works on QS Desktop work the same on QS Server?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;IMG class="jive-image image-2" src="https://community.qlik.com/legacyfs/online/181920_pastedImage_11.png" style="max-height: 900px; max-width: 1200px;" /&gt;&lt;IMG class="jive-image image-3" src="https://community.qlik.com/legacyfs/online/181921_pastedImage_12.png" style="max-height: 900px; max-width: 1200px;" /&gt;&lt;IMG class="jive-image image-4" src="https://community.qlik.com/legacyfs/online/181922_pastedImage_13.png" style="max-height: 900px; max-width: 1200px;" /&gt;&lt;IMG class="image-5 jive-image" src="https://community.qlik.com/legacyfs/online/181923_pastedImage_14.png" style="max-height: 900px; max-width: 1200px;" /&gt;&lt;IMG class="jive-image image-6" src="https://community.qlik.com/legacyfs/online/181925_pastedImage_16.png" style="max-height: 900px; max-width: 1200px;" /&gt;&lt;IMG class="jive-image image-7" src="https://community.qlik.com/legacyfs/online/181926_pastedImage_17.png" style="max-height: 900px; max-width: 1200px;" /&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 02 Nov 2017 20:45:00 GMT</pubDate>
    <dc:creator>bobbiros</dc:creator>
    <dc:date>2017-11-02T20:45:00Z</dc:date>
    <item>
      <title>REST API works in QS Desktop but fails in QS Server</title>
      <link>https://community.qlik.com/t5/Integration-Extension-APIs/REST-API-works-in-QS-Desktop-but-fails-in-QS-Server/m-p/1404248#M8564</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;A href="https://community.qlik.com/space/2157"&gt;Qlik Sense - Data Connectivity&lt;/A&gt;‌&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have a REST API data connection configured that works fine in the QS Desktop version.&lt;/P&gt;&lt;P&gt;However, the same REST API, configured the same way, fails on QS Server (Sept 2017 release) during the data connection creation process (TEST CONNECTION) with error:&lt;/P&gt;&lt;P&gt;&lt;IMG class="jive-image image-1" src="https://community.qlik.com/legacyfs/online/181919_pastedImage_10.png" style="max-height: 900px; max-width: 1200px;" /&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #ff0000; font-size: 12pt;"&gt;Should a REST API data connection that works on QS Desktop work the same on QS Server?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;IMG class="jive-image image-2" src="https://community.qlik.com/legacyfs/online/181920_pastedImage_11.png" style="max-height: 900px; max-width: 1200px;" /&gt;&lt;IMG class="jive-image image-3" src="https://community.qlik.com/legacyfs/online/181921_pastedImage_12.png" style="max-height: 900px; max-width: 1200px;" /&gt;&lt;IMG class="jive-image image-4" src="https://community.qlik.com/legacyfs/online/181922_pastedImage_13.png" style="max-height: 900px; max-width: 1200px;" /&gt;&lt;IMG class="image-5 jive-image" src="https://community.qlik.com/legacyfs/online/181923_pastedImage_14.png" style="max-height: 900px; max-width: 1200px;" /&gt;&lt;IMG class="jive-image image-6" src="https://community.qlik.com/legacyfs/online/181925_pastedImage_16.png" style="max-height: 900px; max-width: 1200px;" /&gt;&lt;IMG class="jive-image image-7" src="https://community.qlik.com/legacyfs/online/181926_pastedImage_17.png" style="max-height: 900px; max-width: 1200px;" /&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 02 Nov 2017 20:45:00 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Integration-Extension-APIs/REST-API-works-in-QS-Desktop-but-fails-in-QS-Server/m-p/1404248#M8564</guid>
      <dc:creator>bobbiros</dc:creator>
      <dc:date>2017-11-02T20:45:00Z</dc:date>
    </item>
    <item>
      <title>Re: REST API works in QS Desktop but fails in QS Server</title>
      <link>https://community.qlik.com/t5/Integration-Extension-APIs/REST-API-works-in-QS-Desktop-but-fails-in-QS-Server/m-p/1404249#M8565</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We were able to get this diagnosed and resolved through the assistance of Qlik Support.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The Internet Explorer browser settings on the Qlik Privileged Service Account had never be setup.&lt;/P&gt;&lt;P&gt;I remote connected to the Qlik Server as the Service Account.&lt;BR /&gt;Accessing IE for the first time setup/configured some corporate LAN/Configuration script settings.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Now the REST connection works from my QS Server.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 09 Nov 2017 21:04:16 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Integration-Extension-APIs/REST-API-works-in-QS-Desktop-but-fails-in-QS-Server/m-p/1404249#M8565</guid>
      <dc:creator>bobbiros</dc:creator>
      <dc:date>2017-11-09T21:04:16Z</dc:date>
    </item>
  </channel>
</rss>

