<?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 data connection sometimes fails in Connectivity &amp; Data Prep</title>
    <link>https://community.qlik.com/t5/Connectivity-Data-Prep/Qlik-Sense-data-connection-sometimes-fails/m-p/1622213#M4374</link>
    <description>&lt;P&gt;Here is one example of data connection code which threw error: LIB CONNECT TO '&amp;lt;ODBC DSN name&amp;gt;'&lt;/P&gt;</description>
    <pubDate>Tue, 10 Sep 2019 15:30:08 GMT</pubDate>
    <dc:creator>Jeffrey_Li</dc:creator>
    <dc:date>2019-09-10T15:30:08Z</dc:date>
    <item>
      <title>Qlik Sense data connection sometimes fails</title>
      <link>https://community.qlik.com/t5/Connectivity-Data-Prep/Qlik-Sense-data-connection-sometimes-fails/m-p/1622163#M4373</link>
      <description>&lt;P&gt;Some of our Qlik Sense tasks sometimes failed for the same type of error: Error: Connector connect error: SQL##f - SqlState: IM002, ErrorCode: 0, ErrorMsg: [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified.&lt;/P&gt;&lt;P&gt;And data connection to a folder (on Qlik sense server) sometimes failed too with error: Cannot open file: 'lib://&amp;lt;folder_name&amp;gt;/qvdname.qvd'&lt;/P&gt;&lt;P&gt;Each time when it happens, we need to restart Qlik Sense Scheduler service. The task worked well after restarting. However, it happens again next run and we have to do another server restart. What might cause this and how to solve it?&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Bo&lt;/P&gt;</description>
      <pubDate>Tue, 10 Sep 2019 14:00:18 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Connectivity-Data-Prep/Qlik-Sense-data-connection-sometimes-fails/m-p/1622163#M4373</guid>
      <dc:creator>Jeffrey_Li</dc:creator>
      <dc:date>2019-09-10T14:00:18Z</dc:date>
    </item>
    <item>
      <title>Re: Qlik Sense data connection sometimes fails</title>
      <link>https://community.qlik.com/t5/Connectivity-Data-Prep/Qlik-Sense-data-connection-sometimes-fails/m-p/1622213#M4374</link>
      <description>&lt;P&gt;Here is one example of data connection code which threw error: LIB CONNECT TO '&amp;lt;ODBC DSN name&amp;gt;'&lt;/P&gt;</description>
      <pubDate>Tue, 10 Sep 2019 15:30:08 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Connectivity-Data-Prep/Qlik-Sense-data-connection-sometimes-fails/m-p/1622213#M4374</guid>
      <dc:creator>Jeffrey_Li</dc:creator>
      <dc:date>2019-09-10T15:30:08Z</dc:date>
    </item>
    <item>
      <title>Re: Qlik Sense data connection sometimes fails</title>
      <link>https://community.qlik.com/t5/Connectivity-Data-Prep/Qlik-Sense-data-connection-sometimes-fails/m-p/1622223#M4375</link>
      <description>&lt;P&gt;ODBC DSN which threw errors are for SQL Server and Netezza. So far DSNs for other database types (Oracle, My SQL etc) works well.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 10 Sep 2019 16:00:12 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Connectivity-Data-Prep/Qlik-Sense-data-connection-sometimes-fails/m-p/1622223#M4375</guid>
      <dc:creator>Jeffrey_Li</dc:creator>
      <dc:date>2019-09-10T16:00:12Z</dc:date>
    </item>
    <item>
      <title>Re: Qlik Sense data connection sometimes fails</title>
      <link>https://community.qlik.com/t5/Connectivity-Data-Prep/Qlik-Sense-data-connection-sometimes-fails/m-p/1624376#M4391</link>
      <description>&lt;P&gt;We have two nodes in Qlik Sense cluster. I re-installed the ODBC driver on node #2 and the issue was solved.&lt;/P&gt;</description>
      <pubDate>Mon, 16 Sep 2019 19:32:40 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Connectivity-Data-Prep/Qlik-Sense-data-connection-sometimes-fails/m-p/1624376#M4391</guid>
      <dc:creator>Jeffrey_Li</dc:creator>
      <dc:date>2019-09-16T19:32:40Z</dc:date>
    </item>
  </channel>
</rss>

