Problem Notes for SAS®9 -

"ERROR: A Property Set registered in metadata matching the LIBNAME ';VALIBLA'; could not be located" occurs when you register SAS High-Performance Risk output as a SAS LASR Analytics table

During an upgrade of SAS Environment Manager, the Agent-Collected Metric (ACM) extract, transform, and load (ETL) script might fail after you enable the SAS Environment Manager Service Architecture and the ACM. The master

If the comment is omitted or made a PL/I style comment, then the syntax error does not occur.

An incomplete CASE expression might be submitted to a database when the query contains a CASE expression in the WHERE clause and the query contains one or more of the following: DISTINCT operator

After you create a brush interaction, SAS Visual Analytics might display the following error when you attempt to save the report.

An error occurred. Please contact your system administr

In SAS ® Enterprise Miner™ Help, the Score Code Export Node chapter contains a section called SAS Enterprise Miner Tools Production of Score Code. However, the table in that section contains incorrect

In SAS ® Pack Optimization, the status of a purchase order plan might incorrectly be displayed with the status of the previous optimization or disaggregation when the plan is optimizing or disaggregating. In

If you attempt to create a cluster table with member tables from SAS Scalable Performance Data Server (SPD Server) 5.2 and an earlier release, the step might fail and return this error:

ERR

When you attempt to rename a SAS Visual Analytics Report, the following error might occur:

Caused by: com.sas.report.repository.RepositoryException: 403 (Forbidden) during MOVE n /SASCont

The ActiveMQ JAR file bundle that is included with SAS ® software has known security vulnerabilities. For Common Vulnerabilities and Exposures (CVE) details, see either of the following CVE documents:

When edited, the variance KPI might display special characters.

In SAS Visual Analytics reports, data items that use string functions, such as Parse, might be evaluated many times instead of just once. These additional evaluations can adversely affect report performance. For example, S

When you run the %INDHN_RUN_MODEL macro against an SPS10 database in SAP HANA, this error might occur:

ERROR: CLI execute error: [SAP AG][LIBODBCHDB DLL][HDBODBC] Syntax error or access

The LOGISTIC procedure outputs incorrect results in the "Association of Predicted Probabilities and Observed Responses" table when the WEIGHT statement and the ROCOPTIONS(WEIGHTED) option are specified.

SAS Digital Marketing email directives that are added to the broadcast HTML fail when multiple directives are present. For example, using the following email directives might result in only the first directive being exec

Hot Fix P83005 provides resolutions for the following SAS Strategy Management 5.6_M1 deployment issues:

When you perform an out-of-the-box SAS ® 9.4_M3 installation and configuration, SAS

Attempting to open a database table from SAS Enterprise Guide might result in the following error: "Open data operation failed [ERROR] No terminal connected to the SAS session when opening a DBMS table from SAS Enterprise Guide"

The macro variables SYSRC, SYSERR, and SQLRC are not being set when "Error on server LIBNAME socket" occurs. The example code below shows both the error in the SAS log and the macro variables SYSRC, SYSERR, and SQL

A segmentation violation or a Read access violation error can occur when the following is true:

If you deploy SAS ® Visual Analytics or SAS ® Visual Analytics Administration and Reporting with a Solution on a Windows machine with SAS Workspace Server, but the SAS LASR Analytic Server is in

Problem Notes for SAS®9 - 57002: Registering SAS High-Performance Risk output to SAS LASR fails and returns an error stating that the registered property set could not be located

Problem Notes for SAS®9 - 55865: An upgrade of SAS Environment Manager fails and returns the error \"ACM could NOT be enabled\"

Problem Notes for SAS®9 - 57023: Statement-style comments can cause syntax errors in PROC FORMAT

Problem Notes for SAS®9 - 56977: An incorrect query might be passed to a database when a CASE expression is used in a WHERE clause

Problem Notes for SAS®9 - 57072: SAS Visual Analytics might display \"TypeError: Error #1009\" when you attempt to save a report after creating a brush interaction

Problem Notes for SAS®9 - 57062: The Tools Production of Score Code table in the Score Code Export Node chapter contains incorrect information in the HPDM Nodes section

Problem Notes for SAS®9 - 56852: The status of a purchase order plan might incorrectly be displayed with the status of the previous optimization or disaggregation

Problem Notes for SAS®9 - 56506: SAS Scalable Performance Data Server 5.2 cluster tables are not compatible with member tables from earlier SPD Server releases

Problem Notes for SAS®9 - 57047: Renaming a SAS Visual Analytics Report fails

Problem Notes for SAS®9 - 57018: Known security issues exist in Apache ActiveMQ

Problem Notes for SAS®9 - 57017: A KPI set that contains a variance KPI might display special characters

Problem Notes for SAS®9 - 57025: SAS Visual Analytics reports that use Parse and other string functions might perform slowly

Problem Notes for SAS®9 - 57020: A TypeMismatch exception occurs when you run the %INDHN_RUN_MODEL in SAP Hana

Problem Notes for SAS®9 - 57046: PROC LOGISTIC outputs incorrect association measures with the ROCOPTIONS(WEIGHTED)option

Problem Notes for SAS®9 - 57033: SAS Digital Marketing email directives added to the broadcast HTML fail when multiple directives are present

Problem Notes for SAS®9 - 56721: Hot Fix P83005 addresses several deployment issues for SAS Strategy Management 5.6_M1

Problem Notes for SAS®9 - 49994: The error \"No terminal connected to the SAS session\" occurs when you open a DBMS table from SAS Enterprise Guide

Problem Notes for SAS®9 - 57043: Macro variables SYSRC, SYSERR, and SQLRC are not being set when \"Error on server LIBNAME socket\" occurs on the SAS Scalable Performance Data Server

Problem Notes for SAS®9 - 56979: A segmentation violation or Read access violation might occur when you are accessing a DBMS table via the SQL procedure

Problem Notes for SAS®9 - 57037: SAS Workspace Server cannot load data directly to a SAS LASR Analytic Server on a different windows machine