SUPPORT

Select Your Region

Visit the Cary, NC, US corporate headquarters site

Americas

Europe

Middle East & Africa

Asia Pacific

View our worldwide contacts list for help finding your region

Americas

Europe

Middle East & Africa

Asia Pacific

Sign In

Get access to My SAS, trials, communities and more.

Sign Out

Get access to My SAS, trials, communities and more.

SAS Sites

sas.com
Support
Blogs
Communities
Developer
Curiosity
Videos

Documentation

Learn
Brand
PartnerNet
Merchandise
SUPPORT / SAMPLES & SAS NOTES
 

Support

Problem Note 58023: A "java.lang.NullPointerException" error occurs when you select the "Cell represents a control group" option in SAS® Customer Intelligence Studio

DetailsHotfixAboutRate It

In SAS Customer Intelligence Studio, a selection campaign group might fail during optimization when one of the member campaigns contains a cell where the option Cell represents a control group is selected.

Consider the following scenario:

  1. You create a campaign where one Cell node has Cell represents a control group selected.

    2. image label

  2. You use this Cell node as a holdout, as shown below:

    3. image label

  3. You add this campaign to a campaign group.
  4. You create a scenario and optimize the scenario.
  5. Then you execute the campaign group.

When you execute the campaign group a dialog box appears with the message execution successful. However, the execution is not successful, and the following error appears in the CICore6.x.log file:

2016-02-04 11:09:16,963 ERROR [CIAsyncExec-9] [48d4f0844ed7a19e:-70ddbf33:152a9e3a840:6ba3] [sasdemo] analytics.crm.flow.ForkCampCommExecution - Uncaught exception: java.lang.NullPointerException at com.sas.analytics.crm.flow.MACommunicationNode.run(MACommunicationNode.java:582) at com.sas.analytics.crm.flow.MACommunicationNode.run(MACommunicationNode.java:364) at com.sas.analytics.crm.flow.MAFlow.executeNode(MAFlow.java:1350) at com.sas.analytics.crm.flow.MAFlow.createTaskSequence(MAFlow.java:2298) at com.sas.analytics.crm.flow.MAFlow.createListofTaskSequences(MAFlow.java:2339) at com.sas.analytics.crm.flow.MAFlow.orderExecutableList(MAFlow.java:2622) at com.sas.analytics.crm.flow.MAFlow.executeTerminalNodeList(MAFlow.java:3401) at com.sas.analytics.crm.flow.MAFlow.flowExecuteCampaign(MAFlow.java:3621) at com.sas.analytics.crm.cm.Campaign.executeCampaign(Campaign.java:3520) at com.sas.analytics.crm.cm.Campaign.executeCampaign(Campaign.java:3475) at com.sas.analytics.crm.flow.ForkCampCommExecution.run(ForkCampCommExecution.java:86) at com.sas.analytics.crm.security.SecurityExecutorServiceImpl$WrappedRunnable.run(SecurityExecutorServiceImpl.java:61) at com.sas.analytics.crm.task.ejb.ClearedThreadLocalRunnable.run(ClearedThreadLocalRunnable.java:17) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:744)

You will notice that the execution is not successful only when you open one of the member campaigns, and execute that member campaign. When you do that, another dialog box appears with a message saying that the execution is successful. However, a continuously-spinning, process indicator (a green wheel) is shown for the Communication node. In addition, the contact history is not updated for the target nor for the control group.

If you disable the holdout in the Communication node, you can execute and optimize the campaign group successfully.

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



Operating System and Release Information

Product FamilyProductSystemProduct ReleaseSAS Release
ReportedFixed*ReportedFixed*
SAS SystemSAS Customer Intelligence StudioMicrosoft® Windows® for x646.1_M16.59.4 TS1M3
Microsoft Windows 8 Enterprise 32-bit6.1_M16.59.4 TS1M3
Microsoft Windows 8 Enterprise x646.1_M16.59.4 TS1M3
Microsoft Windows 8 Pro 32-bit6.1_M16.59.4 TS1M3
Microsoft Windows 8 Pro x646.1_M16.59.4 TS1M3
Microsoft Windows 8.1 Enterprise 32-bit6.1_M16.59.4 TS1M3
Microsoft Windows 8.1 Enterprise x646.1_M16.59.4 TS1M3
Microsoft Windows 8.1 Pro 32-bit6.1_M16.59.4 TS1M3
Microsoft Windows 8.1 Pro x646.1_M16.59.4 TS1M3
Microsoft Windows 106.1_M16.59.4 TS1M3
Microsoft Windows Server 20086.1_M16.59.4 TS1M3
Microsoft Windows Server 2008 R26.1_M16.59.4 TS1M3
Microsoft Windows Server 2008 for x646.1_M16.59.4 TS1M3
Microsoft Windows Server 2012 Datacenter6.1_M16.59.4 TS1M3
Microsoft Windows Server 2012 R2 Datacenter6.1_M16.59.4 TS1M3
Microsoft Windows Server 2012 R2 Std6.1_M16.59.4 TS1M3
Microsoft Windows Server 2012 Std6.1_M16.59.4 TS1M3
Windows 7 Enterprise 32 bit6.1_M16.59.4 TS1M3
Windows 7 Enterprise x646.1_M16.59.4 TS1M3
Windows 7 Home Premium 32 bit6.1_M16.59.4 TS1M3
Windows 7 Home Premium x646.1_M16.59.4 TS1M3
Windows 7 Professional 32 bit6.1_M16.59.4 TS1M3
Windows 7 Professional x646.1_M16.59.4 TS1M3
Windows 7 Ultimate 32 bit6.1_M16.59.4 TS1M3
Windows 7 Ultimate x646.1_M16.59.4 TS1M3
64-bit Enabled AIX6.1_M16.59.4 TS1M3
64-bit Enabled Solaris6.1_M16.59.4 TS1M3
HP-UX IPF6.1_M16.59.4 TS1M3
Linux for x646.1_M16.59.4 TS1M3
Solaris for x646.1_M16.59.4 TS1M3
* For software releases that are not yet generally available, the Fixed Release is the software release in which the problem is planned to be fixed.