<?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 Fixing SQLite3 Connection Failures in Digital Exchange</title>
    <link>https://community.blueprism.com/t5/Digital-Exchange/Fixing-SQLite3-Connection-Failures/m-p/55667#M1177</link>
    <description>&lt;P&gt;Hello,&lt;BR /&gt;&lt;BR /&gt;This is a generic post on how you might fix connection failure issues if you are a using the latest SQLite 3 database. You will need the &lt;CODE&gt;F&lt;SPAN data-ng-bind-html="vm.solution.title" class="ng-binding"&gt;unction for Data - SQLite&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/CODE&gt;&lt;SPAN data-ng-if="vm.solution.semanticVersion.computed !== ''" class="ng-binding ng-scope"&gt;&lt;CODE&gt;- 1.0.1 VBO&lt;/CODE&gt; &lt;A href="https://digitalexchange.blueprism.com/dx/entry/9648/solution/data---sqlite" target="_blank" rel="noopener"&gt;available here&lt;/A&gt; on the Digital Exchange to work with your SQLite 3 database.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;&lt;STRONG&gt;NOTE and DISCLAIMER&lt;BR /&gt;&lt;/STRONG&gt;&lt;BR /&gt;The VBO works for 32-bit versions of SQLite, but version 3 requires modifications. &lt;SPAN style="text-decoration: underline;"&gt;Therefore, there is nothing wrong with the VBO&lt;/SPAN&gt;. But if you are like me and in a hurry to make progress, then you may find the steps in this post helpful. &lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN data-ng-if="vm.solution.semanticVersion.computed !== ''" class="ng-binding ng-scope"&gt;This post assumes that you have already setup this VBO to work with your Blue Prism Studio environment.&lt;BR /&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN data-ng-if="vm.solution.semanticVersion.computed !== ''" class="ng-binding ng-scope"&gt;&lt;STRONG&gt;Issue(s):&amp;nbsp;&lt;BR /&gt;&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;SPAN data-ng-if="vm.solution.semanticVersion.computed !== ''" class="ng-binding ng-scope"&gt;&lt;BR /&gt;Using the Set Connection Details action does not result in any errors&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN data-ng-if="vm.solution.semanticVersion.computed !== ''" class="ng-binding ng-scope"&gt;However, when the Open action is called, the output message returned in the Error output parameter will look something like this:&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN data-ng-if="vm.solution.semanticVersion.computed !== ''" class="ng-binding ng-scope" style="color: rgb(224, 62, 45);"&gt;an attempt was made to load a program with an incorrect format&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN data-ng-if="vm.solution.semanticVersion.computed !== ''" class="ng-binding ng-scope"&gt;&lt;STRONG&gt;Reason:&lt;/STRONG&gt; This is typical of a 32-bit vs. 64-bit mismatch.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN data-ng-if="vm.solution.semanticVersion.computed !== ''" class="ng-binding ng-scope"&gt;&lt;STRONG&gt;Solution: &lt;/STRONG&gt;We will need to replace the DLLs that accompany the above VBO with those that can work with a 64-bit version of SQLite database.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;&lt;SPAN data-ng-if="vm.solution.semanticVersion.computed !== ''" class="ng-binding ng-scope"&gt;Based on the version of .NET installed on my machine, I downloaded this zip file:&lt;/SPAN&gt;
&lt;UL&gt;
&lt;LI&gt;&lt;SPAN data-ng-if="vm.solution.semanticVersion.computed !== ''" class="ng-binding ng-scope"&gt;&lt;A href="https://system.data.sqlite.org/downloads/1.0.118.0/sqlite-" target="test_blank"&gt;https://system.data.sqlite.org/downloads/1.0.118.0/sqlite-&lt;/A&gt;&lt;SPAN style="color: rgb(224, 62, 45);"&gt;netFx40&lt;/SPAN&gt;-binary-&lt;SPAN style="color: rgb(224, 62, 45);"&gt;x64&lt;/SPAN&gt;-2010-1.0.118.0.zip&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN data-ng-if="vm.solution.semanticVersion.computed !== ''" class="ng-binding ng-scope"&gt;&lt;SPAN style="background-color: rgb(251, 238, 184);"&gt;That said, you may want to go to&amp;nbsp;&lt;A href="https://system.data.sqlite.org/index.html/doc/trunk/www/downloads.wiki" target="_blank" rel="noopener" style="background-color: rgb(251, 238, 184);"&gt;this page here&lt;/A&gt; to download the right zip for your situation!&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN data-ng-if="vm.solution.semanticVersion.computed !== ''" class="ng-binding ng-scope"&gt;Unzip this file to a suitable location on your machine&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&lt;STRONG&gt;&lt;BR /&gt;Checking if the DLLs will work with your SQLite 3 Database&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;Before you proceed with additional steps, it would be worthwhile to see if the DLLs in the file that you just downloaded work with your SQLite database to begin with.&amp;nbsp; To do that, follow these steps:&lt;/P&gt;
&lt;OL&gt;
&lt;LI&gt;Run the &lt;CODE&gt;test.exe&lt;/CODE&gt; utility inside the folder that you unzipped in the preceding steps&lt;/LI&gt;
&lt;LI&gt;Update the connection string to include the full path to your database.&lt;/LI&gt;
&lt;LI&gt;In this case I'm using the sample chinook.db database downloaded from the SQLite web page and the connection string would look like this following the update to the database path&lt;BR /&gt;&lt;BR /&gt;&lt;CODE&gt;Data Source=C:\Users\Public\Documents\DATABASE\sqlite3\db\chinook.db;Pooling=true;FailIfMissing=false&lt;/CODE&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/LI&gt;
&lt;LI&gt;Hit the Run button to test&lt;/LI&gt;
&lt;LI&gt;Should the DLLs line up with your version of SQLite 3, then you must see along list of test results marked &lt;SPAN style="color: rgb(22, 145, 121);"&gt;&lt;STRONG&gt;Succeeded&lt;/STRONG&gt;&lt;/SPAN&gt; as shown below (&lt;EM&gt;that also displays the exact version of SQLite 3 Engine&lt;/EM&gt;)&lt;/LI&gt;
&lt;LI&gt;Copy the full connection string from the test.exe Connection String field as you will need it for testing further down below&lt;/LI&gt;
&lt;/OL&gt;
&lt;P&gt;&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="7154.png"&gt;&lt;img src="https://community.blueprism.com/t5/image/serverpage/image-id/7329i745625D3B199C644/image-size/large?v=v2&amp;amp;px=999" role="button" title="7154.png" alt="7154.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="7156.png"&gt;&lt;img src="https://community.blueprism.com/t5/image/serverpage/image-id/7333i05C28C9C89F94CC7/image-size/large?v=v2&amp;amp;px=999" role="button" title="7156.png" alt="7156.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;&lt;STRONG&gt;&lt;BR /&gt;Replacing the DLL Files in the \Blue Prism Automate Folder&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;If you have already setup the VBO in your environment previously, then you know that two DLL assets specified in the VBO documentation (&lt;SPAN style="color: rgb(53, 152, 219);"&gt;&lt;STRONG&gt;SQLite.Interop.dll&lt;/STRONG&gt;&lt;/SPAN&gt; &amp;amp; &lt;SPAN style="color: rgb(53, 152, 219);"&gt;&lt;STRONG&gt;System.Data.SQLite.dll&lt;/STRONG&gt;&lt;/SPAN&gt; shown below) will need to be dropped into the Blue Prism Automate folder that is normally located here:&lt;/P&gt;
&lt;P&gt;C:\Program Files\Blue Prism Limited\Blue Prism Automate&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="7157.png"&gt;&lt;img src="https://community.blueprism.com/t5/image/serverpage/image-id/7331iF36C516532C0827E/image-size/large?v=v2&amp;amp;px=999" role="button" title="7157.png" alt="7157.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN style="color: rgb(224, 62, 45);"&gt;Before proceeding, make sure to close the test.exe as it would be latched on to the System.Data.SQLite.dll file. In addition backup the current versions of the DLLs you are going to be replacing.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;The two DLLs will be present in the folder alongside the test.exe utility. To replace them, simply copy the two DLL files from this folder, and drop them into the \Blue Prism Automate folder.&lt;BR /&gt;&lt;BR /&gt;You will be prompted with file replacement warning. And if you compare the files note that the new files on the left are different in size when compared to what's currently being used by the VBO.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Complete the file replacement. You will likely require to approve the Administrator permissions dialog if it pops us when the replacement is in progress for each of the files.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;&lt;BR /&gt;Testing the Solution from Blue Prism Object Studio&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;Here is the simple VBO that I created to test the impact of the solution. I used the &lt;CODE&gt;Connection String&lt;/CODE&gt; option when connecting to the chinook database.&amp;nbsp; The connection string you copied from test.exe will come in handy here.&lt;/P&gt;
&lt;P&gt;As seen from the Collection, 275 records were returned from the artists table&amp;nbsp;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="7158.png"&gt;&lt;img src="https://community.blueprism.com/t5/image/serverpage/image-id/7332iB78EB51F2FC6032F/image-size/large?v=v2&amp;amp;px=999" role="button" title="7158.png" alt="7158.png" /&gt;&lt;/span&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="7159.png"&gt;&lt;img src="https://community.blueprism.com/t5/image/serverpage/image-id/7342iA52756833C6AC958/image-size/large?v=v2&amp;amp;px=999" role="button" title="7159.png" alt="7159.png" /&gt;&lt;/span&gt;&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="7160.png"&gt;&lt;img src="https://community.blueprism.com/t5/image/serverpage/image-id/7337i8BB4219557E61205/image-size/large?v=v2&amp;amp;px=999" role="button" title="7160.png" alt="7160.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN data-ng-if="vm.solution.semanticVersion.computed !== ''" class="ng-binding ng-scope"&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN data-ng-if="vm.solution.semanticVersion.computed !== ''" class="ng-binding ng-scope"&gt;Thanks and I hope this helps you in working with the most latest version of SQLite 3 databases.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;------------------------------&lt;BR /&gt;Prashanth (Andy) Menon&lt;BR /&gt;------------------------------&lt;/P&gt;</description>
    <pubDate>Thu, 12 Oct 2023 21:50:00 GMT</pubDate>
    <dc:creator>andymenon</dc:creator>
    <dc:date>2023-10-12T21:50:00Z</dc:date>
    <item>
      <title>Fixing SQLite3 Connection Failures</title>
      <link>https://community.blueprism.com/t5/Digital-Exchange/Fixing-SQLite3-Connection-Failures/m-p/55667#M1177</link>
      <description>&lt;P&gt;Hello,&lt;BR /&gt;&lt;BR /&gt;This is a generic post on how you might fix connection failure issues if you are a using the latest SQLite 3 database. You will need the &lt;CODE&gt;F&lt;SPAN data-ng-bind-html="vm.solution.title" class="ng-binding"&gt;unction for Data - SQLite&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/CODE&gt;&lt;SPAN data-ng-if="vm.solution.semanticVersion.computed !== ''" class="ng-binding ng-scope"&gt;&lt;CODE&gt;- 1.0.1 VBO&lt;/CODE&gt; &lt;A href="https://digitalexchange.blueprism.com/dx/entry/9648/solution/data---sqlite" target="_blank" rel="noopener"&gt;available here&lt;/A&gt; on the Digital Exchange to work with your SQLite 3 database.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;&lt;STRONG&gt;NOTE and DISCLAIMER&lt;BR /&gt;&lt;/STRONG&gt;&lt;BR /&gt;The VBO works for 32-bit versions of SQLite, but version 3 requires modifications. &lt;SPAN style="text-decoration: underline;"&gt;Therefore, there is nothing wrong with the VBO&lt;/SPAN&gt;. But if you are like me and in a hurry to make progress, then you may find the steps in this post helpful. &lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN data-ng-if="vm.solution.semanticVersion.computed !== ''" class="ng-binding ng-scope"&gt;This post assumes that you have already setup this VBO to work with your Blue Prism Studio environment.&lt;BR /&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN data-ng-if="vm.solution.semanticVersion.computed !== ''" class="ng-binding ng-scope"&gt;&lt;STRONG&gt;Issue(s):&amp;nbsp;&lt;BR /&gt;&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;SPAN data-ng-if="vm.solution.semanticVersion.computed !== ''" class="ng-binding ng-scope"&gt;&lt;BR /&gt;Using the Set Connection Details action does not result in any errors&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN data-ng-if="vm.solution.semanticVersion.computed !== ''" class="ng-binding ng-scope"&gt;However, when the Open action is called, the output message returned in the Error output parameter will look something like this:&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN data-ng-if="vm.solution.semanticVersion.computed !== ''" class="ng-binding ng-scope" style="color: rgb(224, 62, 45);"&gt;an attempt was made to load a program with an incorrect format&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN data-ng-if="vm.solution.semanticVersion.computed !== ''" class="ng-binding ng-scope"&gt;&lt;STRONG&gt;Reason:&lt;/STRONG&gt; This is typical of a 32-bit vs. 64-bit mismatch.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN data-ng-if="vm.solution.semanticVersion.computed !== ''" class="ng-binding ng-scope"&gt;&lt;STRONG&gt;Solution: &lt;/STRONG&gt;We will need to replace the DLLs that accompany the above VBO with those that can work with a 64-bit version of SQLite database.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;&lt;SPAN data-ng-if="vm.solution.semanticVersion.computed !== ''" class="ng-binding ng-scope"&gt;Based on the version of .NET installed on my machine, I downloaded this zip file:&lt;/SPAN&gt;
&lt;UL&gt;
&lt;LI&gt;&lt;SPAN data-ng-if="vm.solution.semanticVersion.computed !== ''" class="ng-binding ng-scope"&gt;&lt;A href="https://system.data.sqlite.org/downloads/1.0.118.0/sqlite-" target="test_blank"&gt;https://system.data.sqlite.org/downloads/1.0.118.0/sqlite-&lt;/A&gt;&lt;SPAN style="color: rgb(224, 62, 45);"&gt;netFx40&lt;/SPAN&gt;-binary-&lt;SPAN style="color: rgb(224, 62, 45);"&gt;x64&lt;/SPAN&gt;-2010-1.0.118.0.zip&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN data-ng-if="vm.solution.semanticVersion.computed !== ''" class="ng-binding ng-scope"&gt;&lt;SPAN style="background-color: rgb(251, 238, 184);"&gt;That said, you may want to go to&amp;nbsp;&lt;A href="https://system.data.sqlite.org/index.html/doc/trunk/www/downloads.wiki" target="_blank" rel="noopener" style="background-color: rgb(251, 238, 184);"&gt;this page here&lt;/A&gt; to download the right zip for your situation!&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN data-ng-if="vm.solution.semanticVersion.computed !== ''" class="ng-binding ng-scope"&gt;Unzip this file to a suitable location on your machine&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&lt;STRONG&gt;&lt;BR /&gt;Checking if the DLLs will work with your SQLite 3 Database&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;Before you proceed with additional steps, it would be worthwhile to see if the DLLs in the file that you just downloaded work with your SQLite database to begin with.&amp;nbsp; To do that, follow these steps:&lt;/P&gt;
&lt;OL&gt;
&lt;LI&gt;Run the &lt;CODE&gt;test.exe&lt;/CODE&gt; utility inside the folder that you unzipped in the preceding steps&lt;/LI&gt;
&lt;LI&gt;Update the connection string to include the full path to your database.&lt;/LI&gt;
&lt;LI&gt;In this case I'm using the sample chinook.db database downloaded from the SQLite web page and the connection string would look like this following the update to the database path&lt;BR /&gt;&lt;BR /&gt;&lt;CODE&gt;Data Source=C:\Users\Public\Documents\DATABASE\sqlite3\db\chinook.db;Pooling=true;FailIfMissing=false&lt;/CODE&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/LI&gt;
&lt;LI&gt;Hit the Run button to test&lt;/LI&gt;
&lt;LI&gt;Should the DLLs line up with your version of SQLite 3, then you must see along list of test results marked &lt;SPAN style="color: rgb(22, 145, 121);"&gt;&lt;STRONG&gt;Succeeded&lt;/STRONG&gt;&lt;/SPAN&gt; as shown below (&lt;EM&gt;that also displays the exact version of SQLite 3 Engine&lt;/EM&gt;)&lt;/LI&gt;
&lt;LI&gt;Copy the full connection string from the test.exe Connection String field as you will need it for testing further down below&lt;/LI&gt;
&lt;/OL&gt;
&lt;P&gt;&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="7154.png"&gt;&lt;img src="https://community.blueprism.com/t5/image/serverpage/image-id/7329i745625D3B199C644/image-size/large?v=v2&amp;amp;px=999" role="button" title="7154.png" alt="7154.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="7156.png"&gt;&lt;img src="https://community.blueprism.com/t5/image/serverpage/image-id/7333i05C28C9C89F94CC7/image-size/large?v=v2&amp;amp;px=999" role="button" title="7156.png" alt="7156.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;&lt;STRONG&gt;&lt;BR /&gt;Replacing the DLL Files in the \Blue Prism Automate Folder&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;If you have already setup the VBO in your environment previously, then you know that two DLL assets specified in the VBO documentation (&lt;SPAN style="color: rgb(53, 152, 219);"&gt;&lt;STRONG&gt;SQLite.Interop.dll&lt;/STRONG&gt;&lt;/SPAN&gt; &amp;amp; &lt;SPAN style="color: rgb(53, 152, 219);"&gt;&lt;STRONG&gt;System.Data.SQLite.dll&lt;/STRONG&gt;&lt;/SPAN&gt; shown below) will need to be dropped into the Blue Prism Automate folder that is normally located here:&lt;/P&gt;
&lt;P&gt;C:\Program Files\Blue Prism Limited\Blue Prism Automate&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="7157.png"&gt;&lt;img src="https://community.blueprism.com/t5/image/serverpage/image-id/7331iF36C516532C0827E/image-size/large?v=v2&amp;amp;px=999" role="button" title="7157.png" alt="7157.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN style="color: rgb(224, 62, 45);"&gt;Before proceeding, make sure to close the test.exe as it would be latched on to the System.Data.SQLite.dll file. In addition backup the current versions of the DLLs you are going to be replacing.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;The two DLLs will be present in the folder alongside the test.exe utility. To replace them, simply copy the two DLL files from this folder, and drop them into the \Blue Prism Automate folder.&lt;BR /&gt;&lt;BR /&gt;You will be prompted with file replacement warning. And if you compare the files note that the new files on the left are different in size when compared to what's currently being used by the VBO.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Complete the file replacement. You will likely require to approve the Administrator permissions dialog if it pops us when the replacement is in progress for each of the files.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;&lt;BR /&gt;Testing the Solution from Blue Prism Object Studio&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;Here is the simple VBO that I created to test the impact of the solution. I used the &lt;CODE&gt;Connection String&lt;/CODE&gt; option when connecting to the chinook database.&amp;nbsp; The connection string you copied from test.exe will come in handy here.&lt;/P&gt;
&lt;P&gt;As seen from the Collection, 275 records were returned from the artists table&amp;nbsp;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="7158.png"&gt;&lt;img src="https://community.blueprism.com/t5/image/serverpage/image-id/7332iB78EB51F2FC6032F/image-size/large?v=v2&amp;amp;px=999" role="button" title="7158.png" alt="7158.png" /&gt;&lt;/span&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="7159.png"&gt;&lt;img src="https://community.blueprism.com/t5/image/serverpage/image-id/7342iA52756833C6AC958/image-size/large?v=v2&amp;amp;px=999" role="button" title="7159.png" alt="7159.png" /&gt;&lt;/span&gt;&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="7160.png"&gt;&lt;img src="https://community.blueprism.com/t5/image/serverpage/image-id/7337i8BB4219557E61205/image-size/large?v=v2&amp;amp;px=999" role="button" title="7160.png" alt="7160.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN data-ng-if="vm.solution.semanticVersion.computed !== ''" class="ng-binding ng-scope"&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN data-ng-if="vm.solution.semanticVersion.computed !== ''" class="ng-binding ng-scope"&gt;Thanks and I hope this helps you in working with the most latest version of SQLite 3 databases.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;------------------------------&lt;BR /&gt;Prashanth (Andy) Menon&lt;BR /&gt;------------------------------&lt;/P&gt;</description>
      <pubDate>Thu, 12 Oct 2023 21:50:00 GMT</pubDate>
      <guid>https://community.blueprism.com/t5/Digital-Exchange/Fixing-SQLite3-Connection-Failures/m-p/55667#M1177</guid>
      <dc:creator>andymenon</dc:creator>
      <dc:date>2023-10-12T21:50:00Z</dc:date>
    </item>
  </channel>
</rss>

