When you optimize a campaign group in SAS Customer Intelligence Studio, the execution sometimes fails. When this failure occurs, the following error is generated:

Note: This issue happens only when you use Analytical or Priority-based scenario as the optimization method.

The error occurs only when you use many layers of Link node campaigns, as shown in this example where the Link node in campaign 3 looks through the counts of campaign 1:

• Campaign 1 Selection node ► Cell 1
• Campaign 2 Link node to campaign 1, Cell 1 ► Cell 2
• Campaign 3 Link node to campaign 2,Cell 2 ► . . .

If you clear the counts in all nodes for all member campaigns before you execute the campaign group, the execution does not fail.

Instead of clearing the counts for all member campaigns, you can also follow these steps:

1. Open the Link node's source campaign (the campaign that holds the Cell node available for linking) that contains the property Use the most current data when referenced by a link.
   1. If the property Use the most current data when referenced by a link is already selected, clear the check box.
   2. If Use the most current data when referenced by a link is not selected already, go ahead and select it.
2. Clear all counts in the source campaign. Then save and close the campaign.
3. Run the optimization again, and it should finish successfully.

Click the Hot Fix tab in this note to access the hot fix for this issue.

Note: When you generate or refresh SAS^® Marketing Optimization campaign group data, issues have occurred where the following Java arguments are in place in the wrapper.conf (Windows) or setenv.sh (UNIX) files:

For convenience, SAS Technical Support calls these options alwaysrun options because of the .alwaysrun extension.

In addition, the following property is set, typically, in conjunction with the Java arguments shown above. However, this property has no impact on a failed case:

The hot fix introduces a new Java argument:

When you generate or refresh campaign-group data (and you use many layers of Link-node campaigns), the .alwaysrun extension can increase execution time. Therefore, the new Java argument is introduced as a start-up property that explicitly turns on this behavior.

To set the alwaysrun functionality for all Link node campaigns and for generating or refreshing optimization campaign-group data, you must set these properties in the wrapper.conf (Windows) or setenv.sh (UNIX) file, as shown below:

Note: This new Java argument is valid only when using Analytical or Priority-based scenario as the optimization method. For Priority-based optimization, you should not set this argument.

The following property is obsolete and does not need to be set. However, leaving it in place does not have any negative side effect:

Operating System and Release Information

A fix for this issue for SAS Marketing Automation 6.5 is available at: