1 - 10 of top 500 results
Previous   |    1 , 2, 3 ... Last   |    Next >
Sort by:
Date | Relevance


54374 - Secure Sockets Layer (SSL) capability in SASŪ Foundation products is susceptible to the POODLE security vulnerability- Problem Note

The Secure Sockets Layer (SSL) capability in SAS Foundation products supports SSL 3.0. As a result, it is susceptible to the POODLE vulnerability that is described in the following documents: https://www.us-cert.gov/ ...

http://support.sas.com/kb/54/374.html, 37KB


54637 - Unintentionally translated keywords might affect scenarios in SASŪ Anti-Money Laundering- Installation Note

In SAS Anti-Money Laundering, some keywords were unintentionally translated. As a result, the Scenarios part of the application is affected. Potentially, this can cause problems with data on the display, in the SASŪ ...

http://support.sas.com/kb/54/637.html, 31KB


54631 - Some SASŪ Data Management products might fail to migrate in SASŪ 9.4- Problem Note

When you perform a SAS 9.4 to SAS 9.4 migration, some SAS Data Management products are not migrated due to an architecture change. Check the version analysis section of the migration AnalysisReport.html to determine ...

http://support.sas.com/kb/54/631.html, 31KB


54358 - Incorrect score chi-square values with SELECTION=SCORE and extremely ill conditioned data- Problem Note

When using the best subset selection method (SELECTION=SCORE option) in PROC LOGISTIC, if the data in the candidate predictors are extremely ill-conditioned then the score chi-square statistics reported in the

http://support.sas.com/kb/54/358.html, 33KB


54123 - SQL queries against a DB2 database fail in SASŪ Anti-Money Laundering- Problem Note

A reference to a non-existing FSK_USER table in sasaml.db2 is causing the failure.

http://support.sas.com/kb/54/123.html, 31KB


11460 - Incorrect results or an abend might occur when bulk loading to an existing DB2 table- Problem Note

In SASŪ 9.1, using BULKLOAD=yes to insert new rows into an existing DB2 table might lead to unexpected results or to an S0C4 abend. Unexpected or Incorrect Results Occur Unexpected results occur when the input data set ...

http://support.sas.com/kb/11/460.html, 30KB


54019 - Avast! antivirus software quarantines modules that are required by the SQL procedure in Windows operating environments- Usage Note

PROC SQL terminates when required modules have been quarantined by avast! antivirus software in Windows environments. When avast! antivirus software quarantines modules that PROC SQL relies on, it removes them from the ...

http://support.sas.com/kb/54/019.html, 29KB


53896 - The Interactive Grouping node Count and Non Event Count values might be incorrect when a Special Codes Data Set is specified- Problem Note

The Interactive Grouping node in SASŪ Enterprise Miner? has a Special Codes Data Set property. The property enables you to specify the name of the data set that is used to map values to the corresponding special ...

http://support.sas.com/kb/53/896.html, 31KB


53732 - A PROC SQL query might return incorrect results in dynamic locking domain in SASŪ Scalable Performance Data Server- Problem Note

If you are running more than one client session where one session is querying a table while another is performing UPDATE or APPEND operations, you might see incorrect results.

http://support.sas.com/kb/53/732.html, 28KB


53937 - Smoothing parameter might be incorrect when BY statement is specified in PROC LOESS- Problem Note

When using a BY statement in PROC LOESS if any BY group has a constant response (and thereby S=1) the smoothing parameter (S) is set to one (1) in the all subsequent BY groups regardless of what the correct value should ...

http://support.sas.com/kb/53/937.html, 36KB

1 - 10 of top 500 results
Previous   |    1 , 2, 3 ... Last   |    Next >