Quantcast
Channel: Problem Notes for SAS®9 -
Viewing all 8921 articles
Browse latest View live

Problem Notes for SAS®9 - 62347: Known reasons why printing in SAS Visual Analytics might fail with \"HTTP Status 500 - Error executing print request\" and similar errors

$
0
0

Overview

When SAS Visual Analytics fails to print a report, this is one of the errors that you might see:
HTTP Status 500 - Error execu

Problem Notes for SAS®9 - 64749: Using PROC BUILD To PRINT the attributes of SAS/AF PROGRAM entries results in unexpected output

$
0
0
When using PROC BUILD with the PRINT option to write out the attributes of SAS/AF PROGRAM entries, the results might not look correct.

Problem Notes for SAS®9 - 45525: Data might be missing from non-Listing ODS output when using an ACROSS variable in PROC REPORT with the NOCOMPLETECOLS option

$
0
0
Columns of data might be missing from non-Listing ODS output when using an ACROSS variable in PROC REPORT with the NOCOMPLETECOLS option.

Problem Notes for SAS®9 - 64776: One area might always remain in SAS Field Quality Analytics Geographic Analysis despite none being selected

$
0
0
In SAS Field Quality Analytics, when deselecting all areas in a Geographic Analysis, one area might always remain showing in the graphic even if none are selected. This issue is exacerbated by having inconsistent location assignments in the mapping

Problem Notes for SAS®9 - 64775: The SAS Field Quality Analytics graphical Failure Relationship analytic output does not have a filter for transaction count and support (%)

$
0
0
Failure Relationship analytic output in SAS Field Quality Analytics lack a filter for transaction count and support (%) in the graphical section, but are available in the table section.

Problem Notes for SAS®9 - 64673: The SAS metadata server runs out of system memory and stops responding

$
0
0
The automatically scheduled batch relationship loading and cleanup tools introduced in SAS 9.4M3 (TS1M3) might cause the metadata server process to consume all available memory and stop responding. This automat

Problem Notes for SAS®9 - 64759: The errors \"Grid job failed to run\" and \"Remote signon...canceled\" occur in SAS Grid Manager after you use the GRDSVC_ENABLE function

$
0
0
When you submit the JOBNAME= argument with the GRDSVC_ENABLE function, the connection might fail with an error that is similar to the following:
Submitt

Problem Notes for SAS®9 - 64758: The -GRIDGETSTATUS command output displays the incorrect times for the start time and end time of a submitted job

$
0
0
When you submit the SASGSUB -GRIDGETSTATUS command for the SAS Grid Manager Client Utility, the output can display the value :00 for the seconds fo

Problem Notes for SAS®9 - 64760: An \"Unable to Load Published Modeling System\" error occurs when importing a SAS Model Implementation Platform export or modeling system file

$
0
0
When importing a SAS Model Implementation Platform export or modeling system file, the import might fail with the dialog message "Unable to Load Published Modeling System."

Problem Notes for SAS®9 - 64562: Cognos does not connect to SAS Federation Server 4.2 via the provided ODBC driver and you see messages regarding error HY092

$
0
0
Cognos does not connect to SAS Federation Server via ODBC Driver version 9403.100.22119.29796. The Cognos log file shows issues with the SQLGetInfo function and SQL_OUTER_JOINS.

Problem Notes for SAS®9 - 64712: \';CECL - Attribution Analysis\'; model displays a failed status and the analysis run returns an error

$
0
0
When running the ';CECL - Attribution Analysis'; model, you might see a failed status for the analysis run with an error message similar to "ERROR: The server response returned HTTP/1.1 500."

Problem Notes for SAS®9 - 64768: The Specify a Data Selection step might fail to respond when you create a Root Cause Analysis in SAS Asset Performance Analytics

$
0
0
When creating a Root Cause Analysis, the Specify a Data Selection step might fail to respond indefinitely when a large list of tags is used.

Problem Notes for SAS®9 - 64582: The BESTX format is assigned to numeric variables when a custom format is assigned but the format has an unknown location to SAS

$
0
0
When numeric variables are assigned custom formats but the location of the custom formats is unknown to SAS, the BESTX format is assigned to those variables. The following steps illustrate an example where the BE

Problem Notes for SAS®9 - 64733: The SAS Marketing Optimization sasmolauncher script returns an incorrect return code of 0 even before the data is completely refreshed

$
0
0
When you execute SAS Marketing Optimization in batch mode using the sasmolauncher script, an incorrect code of 0

Problem Notes for SAS®9 - 64754: A value is missing from the first row and column of PROC REPORT output results for a table that is inside a gridded layout

$
0
0
Missing text is generated as a result of using the SPANROWS option with the REPORT procedure and a gridded layout.

Problem Notes for SAS®9 - 64652: SAS Environment Manager contains a SpringSource Spring Framework library that has known vulnerabilities

$
0
0
Severity: High Description: SAS Environment Manager contains the Spring 3.0.4 library, which has the following known vulnerability: "https://nvd.nist.gov/vuln/detail

Problem Notes for SAS®9 - 64650: SAS Environment Manager contains XStream libraries with known vulnerabilities

$
0
0
Severity: High Description: The XStream 1.4.10 and 1.2.2 libraries that are included with SAS Environment Manager have the following known vulnerabilities:

Problem Notes for SAS®9 - 64579: Selecting Release from Allocation Management might not show evidence that the button was selected

$
0
0
In SAS Merchandise Allocation, you can select multiple header definitions then select Release .  However, when Release is selected, there might be no evidence that the butto

Problem Notes for SAS®9 - 64564: Export to excel does not complete successfully when exporting with formats

$
0
0
In SAS Merchandise Planning, exporting to excel might not complete successfully when you export with formats.  This issue is likely to occur when the row count exceeds several thousand and the column count exceeds 12

Problem Notes for SAS®9 - 64746: \"The maximum number of Cell Styles was exceeded. You can define up to 64000 style in a .xlsx Workbook\" error occurs in SAS Risk and Finance Workbench

$
0
0
"The maximum number of Cell Styles was exceeded. You can define up to 64000 style in a .xlsx Workbook" error occurs when you run a Preview Landing Area Data report for a large data set in SAS Risk and Finance Workbench.
Viewing all 8921 articles
Browse latest View live


Latest Images