<?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: SAS Viya CAS Errors in SAS Viya</title>
    <link>https://communities.sas.com/t5/SAS-Viya/SAS-Viya-CAS-Errors/m-p/806781#M1384</link>
    <description>Yes, to prevent the message you would need to track down the connection attempt. The CAS log (/opt/sas/viya/config/var/log/cas/default/cas_date_hostname_pid.log) might have some additional information on where this request is coming from.</description>
    <pubDate>Fri, 08 Apr 2022 14:04:57 GMT</pubDate>
    <dc:creator>gwootton</dc:creator>
    <dc:date>2022-04-08T14:04:57Z</dc:date>
    <item>
      <title>SAS Viya CAS Errors</title>
      <link>https://communities.sas.com/t5/SAS-Viya/SAS-Viya-CAS-Errors/m-p/806683#M1381</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I have been getting the following CAS errors, continuously for a very long time. My logs in Environment Manager were not displaying any data. I corrected the issue, so now I am seeing a lot errors (probably from day one).&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;MAIN NoUser MAIN [httpscomm.c:598] - Encryption run-time execution error&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;MAIN NoUser MAIN [httpscomm.c:597] - Error reading HTTP header from client.&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The configuration of port 5570 seems to be OK.&lt;/P&gt;&lt;P&gt;Anyone have any suggestions on what I can try?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;</description>
      <pubDate>Fri, 08 Apr 2022 02:09:14 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Viya/SAS-Viya-CAS-Errors/m-p/806683#M1381</guid>
      <dc:creator>ebonystinger</dc:creator>
      <dc:date>2022-04-08T02:09:14Z</dc:date>
    </item>
    <item>
      <title>Re: SAS Viya CAS Errors</title>
      <link>https://communities.sas.com/t5/SAS-Viya/SAS-Viya-CAS-Errors/m-p/806761#M1382</link>
      <description>Note that HTTP connections should go to port 8777 not 5570. This message is probably from a client trying to establish an insecure connection (i.e. no TLS) to the HTTP port, so the connection is failing. It's not a problem on the CAS side.</description>
      <pubDate>Fri, 08 Apr 2022 13:22:18 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Viya/SAS-Viya-CAS-Errors/m-p/806761#M1382</guid>
      <dc:creator>gwootton</dc:creator>
      <dc:date>2022-04-08T13:22:18Z</dc:date>
    </item>
    <item>
      <title>Re: SAS Viya CAS Errors</title>
      <link>https://communities.sas.com/t5/SAS-Viya/SAS-Viya-CAS-Errors/m-p/806769#M1383</link>
      <description>&lt;P&gt;So what do you suggest that I do to correct the issue? Find where the calls are being made from the client and change ‘http’ to ‘https’ or vise-versa?&lt;/P&gt;</description>
      <pubDate>Fri, 08 Apr 2022 13:45:52 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Viya/SAS-Viya-CAS-Errors/m-p/806769#M1383</guid>
      <dc:creator>ebonystinger</dc:creator>
      <dc:date>2022-04-08T13:45:52Z</dc:date>
    </item>
    <item>
      <title>Re: SAS Viya CAS Errors</title>
      <link>https://communities.sas.com/t5/SAS-Viya/SAS-Viya-CAS-Errors/m-p/806781#M1384</link>
      <description>Yes, to prevent the message you would need to track down the connection attempt. The CAS log (/opt/sas/viya/config/var/log/cas/default/cas_date_hostname_pid.log) might have some additional information on where this request is coming from.</description>
      <pubDate>Fri, 08 Apr 2022 14:04:57 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Viya/SAS-Viya-CAS-Errors/m-p/806781#M1384</guid>
      <dc:creator>gwootton</dc:creator>
      <dc:date>2022-04-08T14:04:57Z</dc:date>
    </item>
  </channel>
</rss>

