<?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: SAP Connector fails with Unicode ERROR max no of 200 conversations exceeded after upgrading in Connectivity &amp; Data Prep</title>
    <link>https://community.qlik.com/t5/Connectivity-Data-Prep/SAP-Connector-fails-with-Unicode-ERROR-max-no-of-200/m-p/1680771#M8048</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;This problem should have been solved in release 7.0.3. The SAP connector team at Qlik R&amp;amp;D will investigate why it is not working.&lt;/P&gt;&lt;P&gt;Having fewer select statements per connection execution should be a workaround (using DISCONNECT/CONNECT in the script to control number of selects per connection execution). RFC connections should be closed when connector process exits.&lt;/P&gt;&lt;P&gt;Regards,&lt;BR /&gt;Håkan&lt;/P&gt;</description>
    <pubDate>Mon, 02 Mar 2020 07:37:22 GMT</pubDate>
    <dc:creator>Hakan_Ronningberg</dc:creator>
    <dc:date>2020-03-02T07:37:22Z</dc:date>
    <item>
      <title>SAP Connector fails with Unicode ERROR max no of 200 conversations exceeded after upgrading</title>
      <link>https://community.qlik.com/t5/Connectivity-Data-Prep/SAP-Connector-fails-with-Unicode-ERROR-max-no-of-200/m-p/1680451#M8047</link>
      <description>&lt;P&gt;After we upgraded the Qlik SAP connector 7.0.0 to 7.0.3 (we also upgraded the transports) our extraction shows the following error;&amp;nbsp;&lt;/P&gt;&lt;DIV&gt;&lt;SPAN&gt;The following error occurred:&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;Connector reply error: LOCATION CPIC (TCP/IP) on local host with Unicode ERROR max no of 200 conversations exceeded TIME Tue Feb 11 11:43:40 2020 RELEASE 721 COMPONENT CPIC (TCP/IP) with Unicode VERSION 3 RC 466 MODULE r3cpic.c LINE 14632 COUNTER 71&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;Is there a way to remove this limit?&amp;nbsp;&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;our SAP is SAP Basis System 7.4 SP08&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="unnamed (1) (1).png" style="width: 508px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/29331i41F581A3C586C884/image-size/large?v=v2&amp;amp;px=999" role="button" title="unnamed (1) (1).png" alt="unnamed (1) (1).png" /&gt;&lt;/span&gt;&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;Thanks for your help&lt;/SPAN&gt;&lt;/DIV&gt;</description>
      <pubDate>Fri, 10 Dec 2021 21:27:33 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Connectivity-Data-Prep/SAP-Connector-fails-with-Unicode-ERROR-max-no-of-200/m-p/1680451#M8047</guid>
      <dc:creator>Juliancrg95</dc:creator>
      <dc:date>2021-12-10T21:27:33Z</dc:date>
    </item>
    <item>
      <title>Re: SAP Connector fails with Unicode ERROR max no of 200 conversations exceeded after upgrading</title>
      <link>https://community.qlik.com/t5/Connectivity-Data-Prep/SAP-Connector-fails-with-Unicode-ERROR-max-no-of-200/m-p/1680771#M8048</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;This problem should have been solved in release 7.0.3. The SAP connector team at Qlik R&amp;amp;D will investigate why it is not working.&lt;/P&gt;&lt;P&gt;Having fewer select statements per connection execution should be a workaround (using DISCONNECT/CONNECT in the script to control number of selects per connection execution). RFC connections should be closed when connector process exits.&lt;/P&gt;&lt;P&gt;Regards,&lt;BR /&gt;Håkan&lt;/P&gt;</description>
      <pubDate>Mon, 02 Mar 2020 07:37:22 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Connectivity-Data-Prep/SAP-Connector-fails-with-Unicode-ERROR-max-no-of-200/m-p/1680771#M8048</guid>
      <dc:creator>Hakan_Ronningberg</dc:creator>
      <dc:date>2020-03-02T07:37:22Z</dc:date>
    </item>
  </channel>
</rss>

