SUPPORT / SAMPLES & SAS NOTES
Problem Note 54226: An error occurs when you update counts on diagram nodes using Link and Cell nodes in SAS® Customer Intelligence Studio
 |  |  |  |  |
When you update counts on a Cell node or on all nodes in a diagram using Link and Cell nodes, the updates might fail and the following error message occurs in the SASCustomerIntelligenceCore6.3.log file:
com.sas.analytics.crm.util.SystemCheck - Error executing campaign. com.sas.analytics.crm.error.client.CodingException: null memberTableDO, most likely someone calling markDirty() where they shouldn't be at com.sas.analytics.crm.flow.MANode.getMemberTableDescriptor(MANode.java:194) at com.sas.analytics.crm.flow.MACellNode.run(MACellNode.java:128) at com.sas.analytics.crm.flow.MAFlow.executeNode(MAFlow.java:1323) at com.sas.analytics.crm.flow.MAFlow.createTaskSequence(MAFlow.java:2270) at com.sas.analytics.crm.flow.MAFlow.createListofTaskSequences(MAFlow.java:2311) at com.sas.analytics.crm.flow.MAFlow.orderExecutableList(MAFlow.java:2594) at com.sas.analytics.crm.flow.MAFlow.executeTerminalNodeList(MAFlow.java:3373) at com.sas.analytics.crm.flow.MAFlow.flowExecuteCampaign(MAFlow.java:3579) at com.sas.analytics.crm.cm.Campaign.executeCampaign(Campaign.java:3418) at com.sas.analytics.crm.cm.Campaign.executeCampaign(Campaign.java:3389) 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:722)
In SAS Customer Intelligence Studio, the following message is displayed:
When this problem happens, the campaign becomes unresponsive and you need to close SAS Customer Intelligence Studio.
As a workaround, remove the Cell node between the Link and Limit nodes, as shown in the example below:
You can make the Link node behave like a CellAct as a marketing cell option in the Link node.
Click the Hot Fix tab in this note to access the hot fix for this issue.
Operating System and Release Information
| Product Family | Product | System | Product Release | SAS Release | ||
| Reported | Fixed* | Reported | Fixed* | |||
| SAS System | SAS Customer Intelligence Studio | Microsoft® Windows® for x64 | 6.3 | 6.4 | 9.4 TS1M0 | |
| Microsoft Windows 8 Enterprise x64 | 6.3 | 6.4 | 9.4 TS1M0 | |||
| Microsoft Windows 8 Pro x64 | 6.3 | 6.4 | 9.4 TS1M0 | |||
| Microsoft Windows 8.1 Enterprise 32-bit | 6.3 | 6.4 | 9.4 TS1M0 | |||
| Microsoft Windows 8.1 Enterprise x64 | 6.3 | 6.4 | 9.4 TS1M0 | |||
| Microsoft Windows 8.1 Pro | 6.3 | 6.4 | 9.4 TS1M0 | |||
| Microsoft Windows 8.1 Pro 32-bit | 6.3 | 6.4 | 9.4 TS1M0 | |||
| Microsoft Windows Server 2008 R2 | 6.3 | 6.4 | 9.4 TS1M0 | |||
| Microsoft Windows Server 2008 for x64 | 6.3 | 6.4 | 9.4 TS1M0 | |||
| Microsoft Windows Server 2012 Datacenter | 6.3 | 6.4 | 9.4 TS1M0 | |||
| Microsoft Windows Server 2012 R2 Datacenter | 6.3 | 6.4 | 9.4 TS1M0 | |||
| Microsoft Windows Server 2012 R2 Std | 6.3 | 6.4 | 9.4 TS1M0 | |||
| Microsoft Windows Server 2012 Std | 6.3 | 6.4 | 9.4 TS1M0 | |||
| Windows 7 Enterprise x64 | 6.3 | 6.4 | 9.4 TS1M0 | |||
| Windows 7 Professional x64 | 6.3 | 6.4 | 9.4 TS1M0 | |||
| 64-bit Enabled AIX | 6.3 | 6.4 | 9.4 TS1M0 | |||
| 64-bit Enabled Solaris | 6.3 | 6.4 | 9.4 TS1M0 | |||
| HP-UX IPF | 6.3 | 6.4 | 9.4 TS1M0 | |||
| Linux for x64 | 6.3 | 6.4 | 9.4 TS1M0 | |||
| Solaris for x64 | 6.3 | 6.4 | 9.4 TS1M0 | |||