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

Problem Notes for SAS®9 - 65299: The Open Data Source window in SAS Visual Analytics unexpectedly shows duplicate table listings

$
0
0
When accessing the Open Data Source window in SAS Visual Analytics, available table names might be shown in duplicate. This problem can occur even if there are no duplicate tables loaded to the S

Problem Notes for SAS®9 - 65298: Sematic validation error that refers to a \"non-existent element\" appears when opening the diagnostic window in SAS Visual Analytics

$
0
0
If your report includes a hierarchy, then you might see a semantic validation error. The message includes content that is similar to "(Error) Step: [Step id:46578] refers to a non-existent element: bi12345." This problem can occur if the hi

Problem Notes for SAS®9 - 64532: Semantic validation error that references a PromptDefinition and its NumericRange appears when opening the diagnostic window in SAS Visual Analytics

$
0
0
If your report includes a slider with the Set value to dynamic minimum or Set value to dynamic maximum option set, then you might see a "Semantic Validation Errors" message when you open the SAS Visual Analytics Diagnostics window. The erro

Problem Notes for SAS®9 - 65149: SAS/AF applications that go through the CPORT/CIMPORT process cannot be executed until they are opened and saved

$
0
0
When using the transport process of CPORT/CIMPORT to move SAS/AF applications from one operating system to Linux, or from an earlier version of SAS to SAS 9.4 M6 (TS1M6) on Linux, you might receive an error that is simil

Problem Notes for SAS®9 - 61516: A PROC HPRISK step fails with, \"ERROR: The application received an invalid market buffer size for the basecase from the HPRisk Engine\"

$
0
0
When you run a PROC HPRISK step that references a large parameter matrix, the step might fail with the following messages in the SAS log:

Problem Notes for SAS®9 - 60942: Opening and submitting runs in SAS Model Implementation Platform is slow

$
0
0
In the SAS   Model Implementation Platform user interface, you might experience slow performance when attempting to open or submit a run. This slowdown occurs when one or both of the following

Problem Notes for SAS®9 - 60674: Stress tasks that output SCENTRANS fail when a query uses a subset of cross-classification variables

$
0
0
When you perform a task using the SAS  High-Performance Risk procedure that specifies the ScenTrans output data set, you might see the following errors:

Problem Notes for SAS®9 - 58379: The SAS Regulatory Risk Management user interface displays an incorrect entity rather than the entity that the user had specified

$
0
0
In SAS Regulatory Risk Management, the user interface (UI) displays the Entity value at the top of the screen, as shown in this image. imgsrc="{fusion_58379_1_entity_display_selected.png}" alt

Problem Notes for SAS®9 - 65293: In SAS High-Performance Risk models that have similar state values might produce incorrect values

$
0
0
In SAS High-Performance Risk, models that have similar state values might produce incorrect values. Similar state values are common within commercial models. For example, a credit transition from "A" to "AA" is indistinguishable

Problem Notes for SAS®9 - 65289: COMPILE procedure fails with, \"ERROR: The word \';_I_\'; is reserved, and cannot be used for the variable name in method \"

$
0
0
In SAS High-Performance Risk or in SAS Risk Dimensions , a direct or indirect reference to the variable _I_ in a COMPILE step can cause the COMPILE step to fail.

Problem Notes for SAS®9 - 65077: SAS Enterprise Case Management does not report an error when you attempt to attach a file with a blocked file extension

$
0
0
SAS Enterprise Case Management appears to allow upload of blocked file types.

Problem Notes for SAS®9 - 60801: Control objects in printed SAS Visual Analytics reports might be significantly reduced in size when the PDF includes an appendix

$
0
0
When you print a report object that has an applied local filter or display rule, the PDF contains an appendix with information about the filters and rules. The PDF also includes a tag that indicates that there is

Problem Notes for SAS®9 - 58764: Images in SAS Visual Analytics reports might be incorrectly remapped during promotion

$
0
0
When promoting SAS Visual Analytics reports, the Import wizard might incorrectly remap some of the images.

Problem Notes for SAS®9 - 65292: Errors are not being written to the MAXDATA.ALLOC_INTERFACE_LOG table

$
0
0
In SAS Merchandise Allocation, errors might not be written to the MAXDATA.ALLOC_INTERFACE_LOG table.  This issue is likely to occurs because of a modification that was inadvertently included in the SAS Merchandise Al

Problem Notes for SAS®9 - 65243: Records might be written to the System Exception folder or placed in a SavedE state during the batch import process

$
0
0
In SAS Merchandise Allocation, records might be written to the System Exception folder or placed in a SavedE state during the batch import process.  This issue is likely to&nbsp

Problem Notes for SAS®9 - 65242: You might be able to save a record with no details in the Merchandise tab in Allocation Attributes

$
0
0
In SAS Merchandise Allocation, you might be able to save a record with no details in the Merchandise tab in Allocation Attributes. This issue is likely to occur when you use a merchandise set to assign attribute values in

Problem Notes for SAS®9 - 65312: A pop-up error occurs when you create a custom detail using the selection group and set up a required field in SAS Customer Intelligence

$
0
0
In SAS Customer Intelligence, the following error occurs when you create a custom detail and set up a required field: "Creation validation for class ';flex.messaging.io.ObjectProxy'; failed."

Problem Notes for SAS®9 - 65307: You might encounter an issue in which 2-digit year dates have the wrong century in SAS 9.3 and earlier releases

$
0
0
In SAS 9.3 and earlier, the default value of the YEARCUTOFF= option is 1920. This default setting is going to cause data integrity issues because any 2-digit years of "20" in dates will be assumed to be 1920 instead of 202

Problem Notes for SAS®9 - 65316: Setting prompt values for SAS Stored Process Portlets fails with the error \"$ is not defined\"

$
0
0
When using a stored process that has prompts in a SAS Stored Process portlet, you might receive the following error when you attempt to select initial prompt values:

Problem Notes for SAS®9 - 65296: SAS Visual Analytics Transport Service does not provide tokenized cross-site request forgery (CSRF) protection

$
0
0
Severity: Medium Description: SAS Visual Analytics Transport Service does not provide tokenized CSRF protection. Potential Impact: An attacker might&nb
Viewing all 8921 articles
Browse latest View live


Latest Images