SAS Drug Development Desktop Connection 1.6 - Direct uploads to SAS Drug Development 4 might fail for large files using a mapped drive
↧
Problem Notes for SAS®9 - 51247: SAS Drug Development Desktop Connection 1.6 - Direct uploads to SAS Drug Development 4 might fail for large files using a mapped drive
↧
Problem Notes for SAS®9 - 58980: Variables filtered out in a SAS Real-Time Decision Manager \"SAS Process\" node definition appear to be deleted
If you edit a SAS Process node definition in SAS ® Customer Intelligence Studio, you might find that one or more of the defined input or output variables no longer appear in the definition. T
↧
↧
Problem Notes for SAS®9 - 58966: Relative date expressions do not work when the Polish locale is used in SAS Marketing Automation
Relative dates expressions might not work in SAS Marketing Automation. This problem might occur when you use the Polish locale ( Polish - Poland ) and you perform steps similar to the following:
↧
Problem Notes for SAS®9 - 57592: Manually created store groups might be missing from the PROFILE_CLUSTER table
In SAS ® Size Profiling, manually created store groups might be missing from the PROFILE_CLUSTER table. This issue occurs when you manually assign stores to a new store group and then copy that profile to an
↧
Problem Notes for SAS®9 - 58927: Risk-factor-only alerts are not generated when you run the alert generation process in SAS Anti-Money Laundering
The risk ranking (fcf_risk_ranking) macro used in the alert generation process might not correctly
identify the evaluation period, which might affect the creation of risk-factor-only alerts.
There is no wor
↧
↧
Problem Notes for SAS®9 - 58783: Items in the category pane in SAS Customer Intelligence Studio appear in English when the locale is set to a language other than English
In SAS Customer Intelligence Studio, the items in the category pane (on the left of the application) might appear in English, even when the locale is set to another language.
For example, the following disp
↧
Problem Notes for SAS®9 - 58925: Subjects and Incidents are incorrectly matched based on Type, Category, and Subcategory using Integrated Event Management
In SAS ® Anti-Money Laundering, the fcf_iem_load_subject and fcf_iem_load_incident macros used in the Integrated Event Management (IEM) process contain incorrect matching criteria. The incorrect matching cr
↧
Problem Notes for SAS®9 - 58383: Attempting to recover the same backup more than once fails and returns status code 323 and the error \"COMMAND_ARCV_CHECKSUM_VALIDATION_ERROR\"
The Deployment Backup and Recovery tool';s sas-recover command fails with an error when the backup has previously been successfully restored.
↧
Problem Notes for SAS®9 - 58982: The \"Warranty program usage limitation\" menu item is not available (grayed out) in the analysis options when analysis exposure type is set to Usage
When the exposure type for an analysis is set to Usage, the Warranty program usage limitation menu item is not available (grayed out) in the SAS ® Field Quality Analytics analysis options.
↧
↧
Problem Notes for SAS®9 - 58895: \"WARNING: The protocol version of the HPRISK engine on the grid (313) does not match the server version (314)\" occurs after you apply a hot fix
When you apply the Z07002 server TKGRID component of the Z08002 HP Risk 3.6 hot fix, you need to manually apply this portion of the hot fix to the nodes of the grid.
↧
Problem Notes for SAS®9 - 58953: Sum aggregation for the SAS Visual Scenario Designer rolling window results in a missing value (.) instead of zero (0)
For the rolling window in SAS Visual Scenario Designer, the sum aggregation for an action boolean-variable results in a missing value (.) instead of zero (0). However, the SAS ® LASR
↧
Problem Notes for SAS®9 - 58896: You receive \"WARNING: Data truncation occurred on a variable document_type_name...\" in SAS Enterprise Case Management
If you configure the global search feature, you might encounter a data truncation warning.
For example, the instructions in the " "http://supportprod.unx.sas.com/documentation/solutions/ecm/6.2/casemgm
↧
Problem Notes for SAS®9 - 58933: User-defined functions created with SAS Scoring Accelerator for Netezza 7.2.1 or later fail with undefined symbol error
When using a scoring function that was created with the scoring macro or with
SAS ® Model Manager, you might encounter an error similar to this:
ERROR: CLI execute error: ERRO![]()
↧
↧
Problem Notes for SAS®9 - 58894: You see the error \"Uncaught ReferenceError...\" in the JavaScript Console after rendering any search page results in SAS Enterprise Case Management
When you perform a search in SAS Enterprise Case Management, you might find an error similar to the following in your browser';s JavaScript Console when the results are rendered:
Uncaught R![]()
↧
Problem Notes for SAS®9 - 58892: No rows are displayed in SAS Enterprise Case Management
If you change the number of rows to be displayed in a case containing a check box or radio-button column on the SAS Enterprise Case Management search screen, you might find that no rows are displayed.
For exam
↧
Problem Notes for SAS®9 - 58778: The SAS Object Spawner stops launching Java client-initiated workspace servers that are doubly redirected
A SAS Object Spawner that has a load-balanced cluster of pooled workspace servers might stop responding and launching workspace servers for launch requests from an Integration Technologies client program based on Java.
↧
Problem Notes for SAS®9 - 58687: SAS Life Science Analytics Framework 4.7 - Java cross-site scripting vulnerability
In SAS ® Life Science Analytics Framework, it is possible that malicious Java script could be executed. This is a form of a Java cross-site scripting vulnerability. The user interface is potentially suscepti
↧
↧
Problem Notes for SAS®9 - 59008: An \"Open cursor error...\" occurs when using SAS/ACCESS Interface to OLE DB configured for UTF-8 encoding to query OLAP cubes
You encounter a problem when you run the SQL procedure pass-through facility to query a Microsoft SQL Server cube in SAS/ACCESS Interface to OLE DB configured for UTF-8 encoding. Here is an example:
↧
Problem Notes for SAS®9 - 59043: Changes to the delimiter in an export definition in SAS Customer Intelligence Studio do not persist
In SAS Customer Intelligence Studio, when you change the delimiter in an export definition, that change does not persist. This problem happens when you perform steps similar to the following:
You create a
↧
Problem Notes for SAS®9 - 59006: An error might occur when you create a data column or computed column names for MXG adapter tables in SAS IT Resource Management 3.5
In SAS IT Resource Management 3.5, aggregation jobs might fail with an error similar to the following when you create a data column or computed column names for MXG adapter stage tables that contain mixed-cased column nam
↧