Problem Notes for SAS®9 -

SAS Real-Time Decision Manager enables you to automatically choose the best option(s) among multiple potential treatments to deliver to a customer. One method that you can use for this arbitration among potential treatmen

When the DDFM=KENWARDROGER option is specified in the MODEL statement in PROC MIXED and the number of observations per subject is large, the procedure might abend with the following error messages:

SAS ® Merchandise Intelligence Load_SRC2STG_Main job might generate the following warning in one or more of the Load_SRC2STG_ STG_table .log files.

WARNING: Attempt to dele

If you use an alias in the FROM e-mail address, a SAS program that sends e-mail fails.

In SAS ® High-Performance Markdown Optimization, the resume captains function in the etlEnd task might result in the following exception in the grid server log when there are online_opt requests queued:

SAS Digital Marketing responses might fail to update the SAS Customer Intelligence common data model for new broadcasts. New broadcasts are those that have been created since the last time the SAS Digital Mark

The SAS Digital Marketing migration script takes an excessive amount of time to execute. If you are planning a migration of SAS Digital Marketing, contact "http://support.sas.com/ctx/supportform/creat

A DATA step error similar to the following might occur when you publish SAS ® Customer Intelligence campaigns that contain numeric list type user-defined fields (UDFs):

ERRO

Beginning with SAS 9.2, SAS uses the IBM Large Block Interface by default whenever possible when reading an external file. This might cause an error when you read the same file twice with different block sizes.

The %MDUCHGV macro, one of the user import macros for managing identity information in metadata, generates the following error message when the distinguished name ( Disting

Opening a previously saved SAS Digital Marketing broadcast from the Edit Content page in SAS Customer Intelligence Studio causes the screen to become unresponsive. The system enters into a waiting state and the green c

Running the SAS ODS Graphics Designer from SAS Studio 3.1 Basic Edition generates the following error:

HTTP Status 404

There is no option to run the SAS ODS Graphic

When using SAS ® High-Performance Markdown Optimization, the Recommended Spend ($) metric in the Markdown Overview view might not match the Recommended Spend ($) metric in the Markdown Approval

In PROC REPORT, the $VARYING. format is used in LINE statements to conditionally hide a line, which might produce fewer detail lines per page. As a result, when you send output to the LISTING destination, the number of pages of output might increase.

When you execute an IOM Direct Interface Stored Process, the presence of a carriage return (CR) and a line feed (LF) in the program code can cause the SAS Workspace Server to stop responding or to fail. The

From the SAS Enterprise Miner 12.1 client, you can open a model that is registered in the SAS ® Metadata Server. When you try to open the model package from a registered model, the Open Package

If SAS Web Report Studio is deployed using JBoss 7, you might see the following error when you attempt to run a report that includes a stored process:

Unsupported protocol in URL (Load

When you have a SAS ® 9.2 Content Server clustered environment with an IBM WebSphere application–server configuration, the SAS Content Server periodic journal synchronization fails with the following er

After you apply Windows 8.1 Update 1 or Windows Server 2012 R2 Update 1, batch commands for the SAS 9.4 Deployment Backup and Recovery tool might fail. When the problem occurs, the batch command is not executed.

In SAS Pack Optimization, stores with a desired target quantity of 0 might still receive units after optimization. This issue occurs because optimization allocates units based on cost. In some cases, a store with a targ

Problem Notes for SAS®9 - 53415: Response time for a SAS Real-Time Decision Manager campaign increases significantly with each additional treatment when you use sort arbitration

Problem Notes for SAS®9 - 51894: PROC MIXED issues ERROR: Integer overflow on computing amount of memory required

Problem Notes for SAS®9 - 53409: Load_SRC2STG_Main generates \"WARNING: Attempt to delete macro variable LOADVIEW failed. Variable not found.\"

Problem Notes for SAS®9 - 53105: A SAS program to send e-mail fails and returns the error \"501 5.1.7 Invalid address\" when the SMTP server does not support aliases

Problem Notes for SAS®9 - 44736: \"ERROR - Exception thrown during the invocation of method etlEnd.\"

Problem Notes for SAS®9 - 53403: SAS Digital Marketing responses might fail to update the SAS Customer Intelligence common data model for new broadcasts

Problem Notes for SAS®9 - 53402: The SAS Digital Marketing migration script takes an excessive amount of time to execute

Problem Notes for SAS®9 - 53400: \"Data Step error while attempting to Convert COMMUNICATION_UDF records\" occurs when you publish a migrated campaign

Problem Notes for SAS®9 - 43560: The message \"ERROR: Undetermined I/O failure\" occurs when an external file is read in SAS 9.2

Problem Notes for SAS®9 - 51979: Synchronizing identity data in metadata generates the error message \"IdentityGroup with this name is being added and deleted\"

Problem Notes for SAS®9 - 53405: Opening a SAS Digital Marketing broadcast from the Edit Content page causes the content to be lost and the screen to become unresponsive

Problem Notes for SAS®9 - 53299: The SAS ODS Graphics Designer does not work with the Enterprise and Basic editions of SAS Studio 3.1

Problem Notes for SAS®9 - 45054: Recommended Spend ($) metrics might not match between views

Problem Notes for SAS®9 - 53287: Using the $VARYING. format in a LINE statement in the REPORT procedure might generate more output than is expected in the LISTING destination

Problem Notes for SAS®9 - 52849: The SAS Workspace Server fails and an error is generated when you execute an IOM Direct Interface Stored Process

Problem Notes for SAS®9 - 53281: The Open Package option is unavailable (grayed out) when you open a registered model in the SAS Enterprise Miner 12.1 client

Problem Notes for SAS®9 - 53390: SAS Web Report Studio reports that include a SAS Stored Process might return an \"unsupported protocol\" error

Problem Notes for SAS®9 - 53115: SAS Content Server fails and generates the error message \"java.sql.SQLException: Unable to create IStatement handle\"

Problem Notes for SAS®9 - 53274: Windows 8.1 Update 1 or Windows Server 2012 R2 Update 1 might cause batch commands for the SAS 9.4 Deployment Backup and Recovery Tool to fail

Problem Notes for SAS®9 - 52249: Stores with a desired target quantity of 0 might receive units after optimization in SAS Pack Optimization