Problem Notes for SAS®9 -

SAS Factory Miner projects become Read-only after failure

The increment setting on the Principal Component template is not passed to the SAS Factory Miner server during execution

In SAS Real-Time Decision Manager, the following error occurs when the file DBTMPLIB.XXXXXXXXXXXXXXXXXXXXXXX_XXX_ERR.DATA has a member name that is too long: "ERROR: The file DBTMPLIB.XXXXXXXXXXXXXXXXXXXXXXX_XXX_ERR.DATA has too long a member n

The Apache Commons Collections library, used by many SAS products, is vulnerable to remote code execution.

The 32-bit version of SAS/ACCESS Interface to ODBC under Windows might crash if you are using the Oracle version 12 client with LDAP service.

In SAS Regular Price Optimization, the optimization results might not be optimal when the current prices for plan members are really large. This issue occurs due to a precision issue that results when the current prices a

Under z/OS, SAS/CONNECT spawners, SAS servers, or SAS code might abend with a system abend 878 or a user abend 1202 due to insufficient memory. You encounter this problem when you have a memory leak. There is

A SAS session in which you use the Dynamic Data Exchange (DDE) engine to create or read a Microsoft Excel spreadsheet or Microsoft Word document can stop responding when certain applications are running in the background

Submitting SAS programs to SAS Grid Manager for Hadoop results in an abnormal termination and errors in the log file.

SAS Factory Miner returns "ERROR: value too long for type character varying(1000) ..." when displaying tree graph

If you try to score data using the Predictive Modeling Markup Language (PMML) score code that is created by SAS ® Enterprise Miner™, then scoring might fail. Errors similar to the following are display

In SAS Customer Intelligence Studio, when you apply a treatment update to a campaign, dynamic custom detail values are incorrectly not maintained for custom details that have the same name in both the old version and new v

When you use SAS Scalable Performance Data Server 5.1 to simultaneously perform multiple tasks against a single table, the following error might occur:

ERROR: Encountered error in IX-subsyste

When you are using the SAS ® Scalable Performance Data Server 5.1 plug-in that is provided with SAS 9.4 and SPD Server 5.1, connecting to an older server (such as 4.52 or 4.53) fails. The plug-in

When you allocate a temporary data set using VSAM BLSR, you get the following error:

ERROR: Insufficient authorization to access xxxxx.xxxxxx.xxxxxx .

The temporary data

SAS Visual Analytics web applications do not function properly when separate internal and external connections are configured and certain security conditions apply. The issues occur when security restrictions prohibit the

Using SAS/ACCESS Interface to Greenplum in a DBCS session, such as Simplified or Traditional Chinese, might result in data being truncated. This would become apparent when you are reading and writing data. Her

In an effort to keep current with bug fixes in the Greenplum driver, SAS has updated the current Greenplum driver to version 7.1.5. Fixes in this driver release include but are not limited to the following:

When you copy date values from Microsoft Excel and paste them into the data grid in SAS Enterprise Guide, the pasted values turn into missing values. To circumvent the problem, first import the Microsoft Excel fi

Cloudera Impala 2.0 now supports the CHAR and VARCHAR data types. SAS recommends using these data types rather than the STRING data type whenever possible. To access these data types from SAS/ACCESS Interface

Problem Notes for SAS®9 - 57296: After a report-generation failure, SAS Factory Miner projects become Read-only, and a \"project is marked as read-only ...\" error is displayed

Problem Notes for SAS®9 - 57294: During execution, the increment setting on the Principal Component template is not passed to the SAS Factory Miner server

Problem Notes for SAS®9 - 57632: An error occurs when you write contact history in SAS Real-Time Decision Manager

Problem Notes for SAS®9 - 57612: The Apache Commons Collections library is vulnerable to remote code execution

Problem Notes for SAS®9 - 57359: SAS/ACCESS Interface to ODBC stops responding when you submit a LIBNAME statement to connect to an Oracle ODBC data source

Problem Notes for SAS®9 - 57637: Optimization results might not be optimal when the current prices for plan members are really large in SAS Regular Price Optimization

Problem Notes for SAS®9 - 57627: Due to a memory leak, SAS code, SAS servers, or SAS/CONNECT spawners might abend with system abend 878 or user abend 1202

Problem Notes for SAS®9 - 57645: Your SAS session might stop responding if you use the SAS Dynamic Data Exchange (DDE) engine when certain applications are running in the background

Problem Notes for SAS®9 - 57661: SAS Grid Manager for Hadoop abnormally terminates when a SAS program is submitted

Problem Notes for SAS®9 - 57293: SAS Factory Miner returns \"ERROR: value too long for type character varying(1000) ...\" when displaying tree graph

Problem Notes for SAS®9 - 57139: Using PMML score code might generate cascading.pipe.OperatorException and cascading.flow.stream errors

Problem Notes for SAS®9 - 57511: Treatments do not maintain custom detail values when the treatment is updated in SAS Customer Intelligence Studio

Problem Notes for SAS®9 - 57658: Running concurrent tasks against SAS Scalable Performance Data Server 5.1 tables might fail and generate subsystem errors

Problem Notes for SAS®9 - 57657: When you use the SAS Management Console plug-in for SAS SPD Server 5.1 to connect to older SPD Server releases, an SPDSSERV connection error occurs

Problem Notes for SAS®9 - 57516: The error \"Insufficient authorization to access...\" occurs when you use bidirectional line switched ring (BLSR) to allocate temporary SAS data sets

Problem Notes for SAS®9 - 56876: SAS Visual Analytics web applications do not function properly when separate internal and external connections are configured

Problem Notes for SAS®9 - 57368: When you are using SAS/ACCESS Interface to Greenplum with the double-byte character set (DBCS) version of SAS , data becomes truncated

Problem Notes for SAS®9 - 57652: Updated SAS/ACCESS Interface to Greenplum ODBC Driver

Problem Notes for SAS®9 - 57689: In SAS Enterprise Guide , date values that are copied from Microsoft Excel into the data grid might be displayed as missing values

Problem Notes for SAS®9 - 56624: SAS/ACCESS Interface to Impala now supports VARCHAR and CHAR data types