Problem Notes for SAS®9 -

When you attempt to save a report, exploration, or data query in SAS Visual Analytics, you might see Error #2130.

In SAS ® Enterprise Miner™, creating a new model package (SPK file) might be slow. Creation might be slow in a multi-tier environment when the middle tier and the compute tier are on separate machines.

When you import data, such as a Microsoft Excel spreadsheet, SAS Visual Data Builder might display the error "[ColumnName] is not valid column name."

When you open the SAS ® Customer Intelligence Studio Custom Details page for an imported campaign definition, the following exception might be displayed:

Failed to Start the Serve

You might experience slow performance when you enter data into a SAS ® Financial Management data-entry form and then refresh the data-entry tables. If you experience this problem, contact "h

In SAS ® Promotion Optimization, you cannot change the status for a calendar from the Calendar Details view. The Change Status menu selection has no statuses available for selection.

You might receive an error message similar to the one below if you try to create a Greenplum table from another Greenplum table while using SAS ® Access to Greenplum:

ERROR

Including the option DEFER=YES in a LIBNAME statement with the DB2 engine might result in a note and an error when you execute one of the Base SAS ® procedures enabled for in-database processing with that l

SAS Model Manager Performance task returns a Java error when running a SAS Enterprise Miner SPK that includes a SAS Credit Scoring flow

There is a 4000-character limit for the number of characters for a Text variable from an Oracle database

Procedures that are run using SAS In-Database give "Base table or view already exists" errors

Permanent Tables should be deleted but are not during database clean up when running DMREG, DMDB, or DMINE.

In SAS ® Enterprise Miner™, running a flow might cause the following errors to be displayed in the Object Spawner log:

Unable to find an available server to redirec

If your response is binary and you specify the DIST=BINOMIAL option in the MODEL statement, and if you also specify a CLASS statement, then observations that are missing only on the response are not scored by the OUTPUT st

In SAS ® Model Manager, when you publish to Teradata, the ScoringResults.log file contains the following error:

ERROR: Insufficient authorization to access /config/Lev1/SASApp/u

SAS statements and functions that access a SAS data file (for example, a SAS data set) as an external file can detect that the file is bound to metadata, at which point SAS should not allow permissions such as acce

Due to a memory problem, you might see the following messages when you use the Remote Help for SAS 9.4 in a z/OS operating environment.

Could not compile the script: Insufficient Memory

In SAS ® Promotion Optimization, a successful optimization or evaluation might incorrectly have an error status in the user interface. When this issue occurs, there are no hyperlink details available about t

In SAS ® Risk Dimensions, risk factor variables that are created in batch might not be rendered correctly in the user interface. When you try to view or use the risk factor variables, the correction changes

SAS Drug Development 4.3.1 - Incorrect SAS Session IDLE and ACTIVE is displayed

Problem Notes for SAS®9 - 52187: SAS Visual Analytics might display Error #2130 when you attempt to save reports, explorations, or data queries

Problem Notes for SAS®9 - 52191: Creating a model package (SPK file) is slow in a multi-tier environment when the middle tier and the compute tier are on separate machines

Problem Notes for SAS®9 - 52172: Importing data into SAS Visual Data Builder might fail with a message about invalid column names

Problem Notes for SAS®9 - 51841: A \"Failed to Start the Server\" exception occurs when you access the Custom Details page for an imported campaign definition

Problem Notes for SAS®9 - 52141: Performance is slow when you refresh data-entry tables after data entry

Problem Notes for SAS®9 - 49874: Cannot change calendar status from Calendar Details view

Problem Notes for SAS®9 - 51721: Creating a Greenplum table from another Greenplum table might result in an error stating that the character value is too long

Problem Notes for SAS®9 - 51999: Including DEFER=YES in the LIBNAME statement with SAS/ACCESS Interface to DB2 might result in an error

Problem Notes for SAS®9 - 51664: SAS Model Manager performance tasks return a Java error when running a SAS Enterprise Miner(tm) SPK that includes a SAS Credit Scoring flow

Problem Notes for SAS®9 - 49800: A \"specified length too long for its datatype ...\" error occurs in the Create Data Source Wizard Advanced Advisor

Problem Notes for SAS®9 - 49177: Procedures that are run using SAS In-Database give \"Base table or view already exists\" errors

Problem Notes for SAS®9 - 49150: A \"Failed to fetch SQL results\" error occurs when SAS In-Database runs the procedures DMREG, DMDB, or DMINE

Problem Notes for SAS®9 - 41945: \"Unable to find an available server to redirect client\", \"failed to redirect client to available server in cluster sas - Logical Workspace Server ...\"

Problem Notes for SAS®9 - 48299: Scoring of observations with missing response not done for some binary response models in PROC GENMOD

Problem Notes for SAS®9 - 51949: The error \"Insufficient authorization to access /config/Lev1/SASApp/udfcode.dat\" is displayed when publishing to Teradata

Problem Notes for SAS®9 - 52078: You can manipulate metadata-bound SAS data sets regardless of server authentication or permissions set on the file

Problem Notes for SAS®9 - 51613: \"Could not compile the script\" and \"Insufficient Memory\" errors occur when you are using the Remote Help in SAS 9.4

Problem Notes for SAS®9 - 51744: A successful optimization or evaluation might incorrectly have an error status with no hyperlink details about the error

Problem Notes for SAS®9 - 52223: Viewing or using risk factor variables gives a \"SubmitSaveException: The changes to the Variable <variable name> have failed ...\" Java exception

Problem Notes for SAS®9 - 51872: SAS Drug Development 4.3.1 - Incorrect SAS Session IDLE and ACTIVE is displayed