<?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: Error in SAS/Athena:  An error has been thrown from the AWS Athena client. No response body in SAS Data Management</title>
    <link>https://communities.sas.com/t5/SAS-Data-Management/Error-in-SAS-Athena-An-error-has-been-thrown-from-the-AWS-Athena/m-p/600474#M18319</link>
    <description>&lt;P&gt;I'm pleased to hear it!&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Happy computing,&lt;/P&gt;
&lt;P&gt;&amp;nbsp; &amp;nbsp;Tom&lt;/P&gt;</description>
    <pubDate>Wed, 30 Oct 2019 17:41:12 GMT</pubDate>
    <dc:creator>TomKari</dc:creator>
    <dc:date>2019-10-30T17:41:12Z</dc:date>
    <item>
      <title>Error in SAS/Athena:  An error has been thrown from the AWS Athena client. No response body</title>
      <link>https://communities.sas.com/t5/SAS-Data-Management/Error-in-SAS-Athena-An-error-has-been-thrown-from-the-AWS-Athena/m-p/600169#M18309</link>
      <description>&lt;P&gt;Hello everyone,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I had been using an ODBC to connect SAS to Athena for months. Now when I try to connect, it's throwing me this error:&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;ERROR: CLI open cursor error: [Simba][Athena] (1040) An error has been thrown from the AWS Athena&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;client. Athena Error No: 100, Error Message: No response body. [Execution ID:&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;edd966b7-12bc-4938-b461-276668116e36]&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;It's doing the same thing for everyone on my team. The ODBC still connects successfully and we can access the data through Python, so I'm pretty certain the problem stems from SAS.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Do you guys have any insights as to what's going on?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;</description>
      <pubDate>Tue, 29 Oct 2019 20:18:55 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Data-Management/Error-in-SAS-Athena-An-error-has-been-thrown-from-the-AWS-Athena/m-p/600169#M18309</guid>
      <dc:creator>renaudguilbert</dc:creator>
      <dc:date>2019-10-29T20:18:55Z</dc:date>
    </item>
    <item>
      <title>Re: Error in SAS/Athena:  An error has been thrown from the AWS Athena client. No response body</title>
      <link>https://communities.sas.com/t5/SAS-Data-Management/Error-in-SAS-Athena-An-error-has-been-thrown-from-the-AWS-Athena/m-p/600202#M18311</link>
      <description>&lt;P&gt;I think that's what SAS does when it catches an error from the database software, and doesn't know what else to do with it. I think the "Athena Error No: 100, Error Message: No response body." is what SAS is getting back from Athena. Can you look up that error number in the Athena documentation?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Are you sure you're successfully connecting to the database using ODBC from the same machine that's running the SAS session?&lt;/P&gt;
&lt;P&gt;If so, maybe:&lt;BR /&gt;- credential changes?&lt;BR /&gt;- firewall / network changes?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;You could take a look at the SASTRACE system option, using it might return some useful information.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Good luck!&lt;BR /&gt;Tom&lt;/P&gt;</description>
      <pubDate>Tue, 29 Oct 2019 22:36:55 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Data-Management/Error-in-SAS-Athena-An-error-has-been-thrown-from-the-AWS-Athena/m-p/600202#M18311</guid>
      <dc:creator>TomKari</dc:creator>
      <dc:date>2019-10-29T22:36:55Z</dc:date>
    </item>
    <item>
      <title>Re: Error in SAS/Athena:  An error has been thrown from the AWS Athena client. No response body</title>
      <link>https://communities.sas.com/t5/SAS-Data-Management/Error-in-SAS-Athena-An-error-has-been-thrown-from-the-AWS-Athena/m-p/600403#M18315</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;You were right, the issue was linked to a new firewall update that shut the connection down while it was being deployed. I checked with our IT department and the connection was restored when the deployment was complete.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you!&lt;/P&gt;</description>
      <pubDate>Wed, 30 Oct 2019 14:11:24 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Data-Management/Error-in-SAS-Athena-An-error-has-been-thrown-from-the-AWS-Athena/m-p/600403#M18315</guid>
      <dc:creator>renaudguilbert</dc:creator>
      <dc:date>2019-10-30T14:11:24Z</dc:date>
    </item>
    <item>
      <title>Re: Error in SAS/Athena:  An error has been thrown from the AWS Athena client. No response body</title>
      <link>https://communities.sas.com/t5/SAS-Data-Management/Error-in-SAS-Athena-An-error-has-been-thrown-from-the-AWS-Athena/m-p/600474#M18319</link>
      <description>&lt;P&gt;I'm pleased to hear it!&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Happy computing,&lt;/P&gt;
&lt;P&gt;&amp;nbsp; &amp;nbsp;Tom&lt;/P&gt;</description>
      <pubDate>Wed, 30 Oct 2019 17:41:12 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Data-Management/Error-in-SAS-Athena-An-error-has-been-thrown-from-the-AWS-Athena/m-p/600474#M18319</guid>
      <dc:creator>TomKari</dc:creator>
      <dc:date>2019-10-30T17:41:12Z</dc:date>
    </item>
  </channel>
</rss>

