<?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>Question Re: Trying to connect to PB2022.db using ODBC I get 'miss... in Technology Q&amp;A</title>
    <link>https://community.sap.com/t5/technology-q-a/trying-to-connect-to-pb2022-db-using-odbc-i-get-missing-license-file/qaa-p/14099545#M4913724</link>
    <description>&lt;P&gt;It is most likely one of the following&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;SQL Anywhere requires license files - dbeng17.lic and dbsrv17.lic depending on engine type. Those files should be in the same directory as the binary.&amp;nbsp;&lt;/LI&gt;&lt;LI&gt;SQLANY17 environment variable should be set and pointing to the directory c:\Program Files\SQL Anywhere 17 (based on the start line you screen capped)&lt;/LI&gt;&lt;LI&gt;There is a version mismatch between the binaries - specifically dbserv17.dll and dbrsa17.dll should be the same version -- but if there is a mismatch in any of the binaries, that could be problematic.&amp;nbsp;&lt;UL&gt;&lt;LI&gt;the license file is encrypted and if dbrsa17 is a mismatch to the engine dll, the license file cannot be read.&amp;nbsp;&lt;/LI&gt;&lt;LI&gt;some of the binaries are expected to differ (old unload binaries, SAP Crypto or Open SSL depending on the underlying encryption libraries)&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;If you do find mismatched binaries, you might be able to run the install and perform a repair but you may be forced to do a fresh install.&lt;/P&gt;</description>
    <pubDate>Tue, 13 May 2025 01:07:17 GMT</pubDate>
    <dc:creator>chris_keating</dc:creator>
    <dc:date>2025-05-13T01:07:17Z</dc:date>
    <item>
      <title>Trying to connect to PB2022.db using ODBC  I get 'missing license file'</title>
      <link>https://community.sap.com/t5/technology-q-a/trying-to-connect-to-pb2022-db-using-odbc-i-get-missing-license-file/qaq-p/14099376</link>
      <description>&lt;P&gt;When using ODBC to connect to Powerbuilder demo databases PB2022R3.db,&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="KT991_0-1747073965407.png" style="width: 400px;"&gt;&lt;img src="https://community.sap.com/t5/image/serverpage/image-id/260187iA457B34C7B2685A4/image-size/medium?v=v2&amp;amp;px=400" role="button" title="KT991_0-1747073965407.png" alt="KT991_0-1747073965407.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;I get&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="KT991_1-1747073992154.png" style="width: 400px;"&gt;&lt;img src="https://community.sap.com/t5/image/serverpage/image-id/260188i7441B391338F5845/image-size/medium?v=v2&amp;amp;px=400" role="button" title="KT991_1-1747073992154.png" alt="KT991_1-1747073992154.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;What license(s) I'm I missing?&lt;/P&gt;</description>
      <pubDate>Mon, 12 May 2025 18:21:50 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/trying-to-connect-to-pb2022-db-using-odbc-i-get-missing-license-file/qaq-p/14099376</guid>
      <dc:creator>KT991</dc:creator>
      <dc:date>2025-05-12T18:21:50Z</dc:date>
    </item>
    <item>
      <title>Re: Trying to connect to PB2022.db using ODBC I get 'miss...</title>
      <link>https://community.sap.com/t5/technology-q-a/trying-to-connect-to-pb2022-db-using-odbc-i-get-missing-license-file/qaa-p/14099545#M4913724</link>
      <description>&lt;P&gt;It is most likely one of the following&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;SQL Anywhere requires license files - dbeng17.lic and dbsrv17.lic depending on engine type. Those files should be in the same directory as the binary.&amp;nbsp;&lt;/LI&gt;&lt;LI&gt;SQLANY17 environment variable should be set and pointing to the directory c:\Program Files\SQL Anywhere 17 (based on the start line you screen capped)&lt;/LI&gt;&lt;LI&gt;There is a version mismatch between the binaries - specifically dbserv17.dll and dbrsa17.dll should be the same version -- but if there is a mismatch in any of the binaries, that could be problematic.&amp;nbsp;&lt;UL&gt;&lt;LI&gt;the license file is encrypted and if dbrsa17 is a mismatch to the engine dll, the license file cannot be read.&amp;nbsp;&lt;/LI&gt;&lt;LI&gt;some of the binaries are expected to differ (old unload binaries, SAP Crypto or Open SSL depending on the underlying encryption libraries)&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;If you do find mismatched binaries, you might be able to run the install and perform a repair but you may be forced to do a fresh install.&lt;/P&gt;</description>
      <pubDate>Tue, 13 May 2025 01:07:17 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/trying-to-connect-to-pb2022-db-using-odbc-i-get-missing-license-file/qaa-p/14099545#M4913724</guid>
      <dc:creator>chris_keating</dc:creator>
      <dc:date>2025-05-13T01:07:17Z</dc:date>
    </item>
  </channel>
</rss>

