Problem Notes for SAS®9 -

If you have McAfee Data Loss Prevention (DLP) end-point service enabled and you attempt to save a SAS Enterprise Guide project, the following message error message occur:

Due to an error in handling the Kerberos cache, the object spawner might stop responding when it is used to launch Kerberized grid-enabled workspace server sessions.

The SAS Object Spawner keeps ports to mbatchd processes in a CLOSE-WAIT state indefinitely. Because these port connections do not close, you eventually encounter a situation in which there are no more available ephemeral ports.

You might get "ERROR: Unable to transcode data..." when accessing a non-Western Latin (WLATIN1) Netezza database.

The HPSPLIT procedure in SAS/STAT software supports a WEIGHT statement. However, information about the WEIGHT statement was omitted from the documentation. A pre-production draft document is available by

In SAS Regular Price Optimization, selected products might not be displayed in the Relationship values section in the Pricing Rules view for product relationship rules. This issue occurs when you se

You might see a problem when you import a complete package using the import feature in SAS Management Console. If you import the full package twice, subflows might disappear from the metadata.

PROC QUANTREG might issue "ERROR: Failure loading the optimization extension" when the ALGORITHM=IPM option is specified.

PROC PSMATCH might issue "ERROR: Failure loading the optimization extension" when FULL, OPTIMAL, or VARRATIO is specified in the METHOD=option.

Columns with numeric data type are incorrectly stored as character data types when exported to SPSS. This problem occurs when the SAS source data contains character columns longer than 255 bytes in width.

Characters are not transcoded correctly when exporting Wlatin2-encoded data to Microsoft Excel using the SAS PC Files Server. The result is incorrect characters in the Excel file.

When you run SAS/ACCESS Interface to the PI System on Linux or UNIX operating systems, you might get a segmentation violation error similar to the one shown below:

When you use sensitivity analysis with SAS Marketing Optimization, the Sensitivity Analysis graph does not show updated constraint values. Click the Hot Fix

In SAS Marketing Optimization, the following Read-access violation might occur when you optimize a scenario with very large input data.

Russian Cyrillic characters are ignored when you create a document PDF file for a campaign in SAS Customer Intelligence Studio. Click the Hot Fix tab in this note to access the hot fi

When you use parameters in the mo_opt_config.sas file in SAS Marketing Optimization, the parameters are not recognized during scenario optimization. To work around this problem, add the %GLOBAL statement before t

You might encounter the following exception in the SASCustIntelCore. x .log file when you change the selection criteria in a Split node in SAS Customer Intelligence Studio:

In an optimized campaign group, the pie and bar charts are not displayed on the Package Summary tab of the Selection Summary window. imgalt="image label" src="{fusion_59339_3_5

Corrupted Excel files might be created with either the ODS destination for Excel or the ExcelXP tagset. This is most likely to occur when the files are created in a Unicode (also called UTF-8) SAS session

This error occurs when you upgrade to SAS 9.4M5: The following problem was encountered while configuring SAS Web Application Server Configuration: An unexpected error occurred. Please refer to SAS-

Problem Notes for SAS®9 - 59826: The message \"Failed to save project. Access to the path is denied\" occurs when you try to save a SAS Enterprise Guide project

Problem Notes for SAS®9 - 59950: The SAS Object Spawner might fail suddenly when you are using grid-launched SAS Workspace Servers configured for Kerberos authentication

Problem Notes for SAS®9 - 59538: The SAS Object Spawner incorrectly keeps ports to mbatchd processes in a CLOSE-WAIT state indefinitely

Problem Notes for SAS®9 - 59905: \"ERROR: Unable to transcode data...\" occurs when accessing a non-Western Latin (WLATIN1) Netezza database

Problem Notes for SAS®9 - 59256: The WEIGHT statement in the HPSPLIT procedure was omitted from the documentation

Problem Notes for SAS®9 - 60030: Selected products might not be displayed in the Relationship values section in the Pricing Rules view for product relationship rules

Problem Notes for SAS®9 - 60072: Subflows are lost when reimporting the subflow with its parent flow in the same package

Problem Notes for SAS®9 - 59827: The QUANTREG procedure issues \"ERROR: Failure loading the optimization extension\"

Problem Notes for SAS®9 - 60061: The PSMATCH procedure issue \"ERROR: Failure loading the optimization extension\"

Problem Notes for SAS®9 - 60059: SAS numeric variables are incorrectly stored as character variables when exported to SPSS using SAS/ACCESS Interface to PC Files

Problem Notes for SAS®9 - 60060: Characters are not transcoded correctly when exporting Wlatin2-encoded data to Microsoft Excel using the SAS PC Files Server

Problem Notes for SAS®9 - 59983: Retrieving more than a million records using SAS/ACCESS Interface to the PI System under UNIX returns a segmentation violation error

Problem Notes for SAS®9 - 59861: Sensitivity Analysis graphs do not show updated constraint values in SAS Marketing Optimization

Problem Notes for SAS®9 - 59791: A Read-access violation might occur when you optimize a scenario in SAS Marketing Optimization

Problem Notes for SAS®9 - 58986: Russian Cyrillic characters are ignored in a document PDF file for a campaign

Problem Notes for SAS®9 - 59466: Parameters in the SAS Marketing Optimization configuration file are not recognized

Problem Notes for SAS®9 - 59633: An index-out-of-bounds exception occurs when you change selection criteria in a Split node in SAS Customer Intelligence Studio

Problem Notes for SAS®9 - 59339: The \"Package Summary\" tab (in the \"Selection Summary\" window) in SAS Customer Intelligence Studio does not display the pie and bar charts

Problem Notes for SAS®9 - 62455: Corrupted Excel files might be generated when you use either the ODS destination for Excel or the ExcelXP tagset

Problem Notes for SAS®9 - 62449: SAS Deployment Manager fails with errors in the \"SAS Web Application Server Configuration\" step (in the Apply Update stage) during an upgrade