In SAS Customer Intelligence Studio, a green process indicator (a spinning wheel) runs when you use a Process node downstream from a Communication node. The first time you update counts
↧
Problem Notes for SAS®9 - 57141: SAS Customer Intelligence Studio shows a green process indicator when you use a Process node downstream of a Communication node updating count
↧
Problem Notes for SAS®9 - 56719: SAS Life Science Analytic Framework 4.6 - Scheduled events minute, hourly, and daily do not include occurrences that would run on the end date
Currently in SAS ® Life Science Analytic Framework, schedules with trigger types like minute, hour, day use a Quartz Simple trigger. This trigger mechanism fires at the start time and repeats for the specifi
↧
↧
Problem Notes for SAS®9 - 57111: Syntax errors occur when you use the MULTISTMT= option in SAS/ACCESS Interface to Teradata
Syntax errors might occur when generating long SQL queries with SAS/ACCESS Interface to Teradata. The problem is likely to occur when using the MULTISTMT= option.
↧
Problem Notes for SAS®9 - 57103: Performing command-line batch deployments in SAS Data Integration Studio generates code that contains USER= and PASSWORD= instead of AUTHDOMAIN
The command-line batch deployment tool does not provide the ability to generate code with the AUTHDOMAIN= option when authentication code is required. Statements that require authentication code are always generated with the USER= and PASSWORD= opti
↧
Problem Notes for SAS®9 - 57099: WebHDFS REST API does not work correctly on SAS/ACCESS Interface to Hadoop when high availability is configured in the Hadoop cluster
Using the WebHDFS RESTFUL application programming interface (API) does not work correctly on Hadoop clusters when high-availability mode is enabled. As a result, you must
implement the standard Java configuration steps a
↧
↧
Problem Notes for SAS®9 - 57034: Support for Vertica 7.1 with the SAS/ACCESS Interface to Vertica
SAS/ACCESS Interface to Vertica does not currently support version 7.1 of the Vertica database system.
Click the Hot Fix tab in this note to access the hot fix for this issue.
↧
Problem Notes for SAS®9 - 57097: The Update Host Name References tool in SAS Deployment Manager builds an invalid JDBC URL and an error message is generated
When you use the SAS Deployment Manager Update Host Name utility, configuration of the SAS Web Infrastructure Platform might fail. With this failure, an invalid Java database connectivity (JDBC) URL is built, and the we
↧
Problem Notes for SAS®9 - 55402: When you open SAS Enterprise Guide , an \"...invalid character...\" error occurs
"The error " ';.';, hexadecimal value 0x00, is an invalid character. Line 1, position 1" might occur When you open SAS Enterprise Guide.
↧
Problem Notes for SAS®9 - 55376: Installing SAS Enterprise Guide 7.1 might generate the error \"The program can\';t start because MSVCR120.dll is missing from your computer\"
If you install SAS Enterprise Guide 7.1 after SAS ® Enterprise Guide ® 6.1 M1 has been removed, SAS Enterprise Guide 7.1 might generate the error "The program can';t start because MSVCR120.dll is
↧
↧
Problem Notes for SAS®9 - 52763: Using a shortcut to invoking SAS Enterprise Guide might cause the application to crash
Using a shortcut to start SAS Enterprise Guide might cause the application to fail and result in these errors:
%windir% not found.
%windir% missing.
The problem occurs on computer↧
Problem Notes for SAS®9 - 57105: The PLM procedure might end abnormally when the item store includes model variables with associated formats
If formats are associated with model variables in the analysis procedure that is used to create an item store, PROC PLM might fail with errors.
↧
Problem Notes for SAS®9 - 56906: Importing or exporting a SAS Marketing Automation package fails and returns a null pointer exception error
If you import or export a SAS Marketing Automation package that contains either a campaign definition or a communication definition, the action fails and you receive a null pointer exception error.
To work aro
↧
Problem Notes for SAS®9 - 56883: Column selections are not saved in the Selection Campaigns workspace for SAS Marketing Automation
When you use the Manage Columns toolbar icon in SAS Marketing Automation, selections might not be saved after you make column modifications to the Selection Campaigns workspace. <
↧
↧
Problem Notes for SAS®9 - 57068: Invalid dates are inserted into the contact history after the initial contact history insert fails
When you initially insert data into the SAS ® Real-Time Decision Manager contact-history table, sometimes that insertion fails. This failure is normal in some cases. However, when the automatic recovery proce
↧
Problem Notes for SAS®9 - 42784: SAS Profitability Management calculations will run faster with an optimized delete query
When you calculate a SAS Profitability Management
model, one of the tasks performed as part of the calculation process is a delete query on
the BehaviorAssignment table within the PM
↧
Problem Notes for SAS®9 - 57100: In SAS Enterprise Guide , the Project Properties option to \"Allow parallel execution on the same server\" might not work correctly
In SAS Enterprise Guide, one of the properties for a project is Allow parallel execution on the same server . To set this property, you navigate to File ► Project Properties ►Code Submis
↧
Problem Notes for SAS®9 - 57116: In SAS Enterprise Guide , the option to \"Run Branch From\" might run objects out of order and generate an error
Using the Run Branch From option might run objects in the process flow in the wrong order and might generate the following error:
ERROR: Unable to get SAS code. Unable to ope![]()
↧
↧
Problem Notes for SAS®9 - 56978: A Read access violation error might occur when you are running an SQL procedure query
When you access a database management system (DBMS), if you use the LIBNAME engine and an SQL query that includes a function that is not passed down to the DBMS, a Read access violation might occur. The error might look si
↧
Problem Notes for SAS®9 - 56374: The options to prevent duplicate emails and to identify preview messages fail after the SAS Digital Marketing web applications are rebuilt
SAS Digital Marketing Studio provides options to prevent duplicate emails ( Prevent duplicate e-mails per broadcast ) and to identify preview messages ( Identify preview messages in the subject line
↧
Problem Notes for SAS®9 - 56178: The Summary and History properties of a broadcast in SAS Digital Marketing Studio incorrectly show that zero (0) emails were successfully sent
In SAS Digital Marketing Studio, the Summary and History properties of a broadcast incorrectly show that zero (0) emails were sent successfully. This problem occurs only when the audit level is set to FAILURE.
↧