SUPPORT / SAMPLES & SAS NOTES
Problem Note 67268: A failure occurs and an error is generated when you modify a migrated treatment in SAS® Customer Intelligence Studio
 |  |  |  |  |
In SAS Customer Intelligence Studio, a failure might occur when you modify a migrated treatment. This problem happens when you perform steps similar to the following:
- Modify a treatment that is already attached to a campaign (for example, delete or modify one of the custom-details fields).
- Open the Campaign and navigate to the Treatment tab. On that tab, you can see that the treatment update is available (denoted by the red icon).
- Click the green check mark to accept the treatment update in the campaign.
The following error message is shown in the SASCustIntelCore6.x.log file:
2020-10-02 17:05:40,589 ERROR [CIAsyncExec-4] [f62fdd11b6cc2da5:-1271839c:174b3a099cb:587a] [sasdemo] s.analytics.crm.cm.ejb.CampaignProxyImpl - Encountered client exception:Error updating campaign reference data.
com.sas.analytics.crm.error.client.ApplicationException: Error updating campaign reference data.
at com.sas.analytics.crm.util.SystemCheck.createMAException(SystemCheck.java:106)
at com.sas.analytics.crm.util.SystemCheck.handleExceptionForEJB(SystemCheck.java:83)
at com.sas.analytics.crm.flow.ejb.FlowBean.updateCampRefData(FlowBean.java:2672)
at com.sas.analytics.crm.flow.client.FlowDelegate.updateCampRefData(FlowDelegate.java:1214)
at com.sas.analytics.crm.cm.ejb.CampaignProxyImpl$22.run(CampaignProxyImpl.java:1894)
at com.sas.analytics.crm.cm.ejb.CampaignProxyImpl$22.run(CampaignProxyImpl.java:1778)
at com.sas.analytics.crm.cm.ejb.util.RunnableWithInstance.call(RunnableWithInstance.java:9)
at com.sas.analytics.crm.cm.ejb.util.WrappedRunnable.run(WrappedRunnable.java:78)
at com.sas.ci.services.common.services.asynchronous.SessionCountingRunnableQueue$QueueHandler.run(SessionCountingRunnableQueue.java:88)
at com.sas.analytics.crm.task.ejb.ClearedThreadLocalRunnable.run(ClearedThreadLocalRunnable.java:24)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.lang.NullPointerException
com.sas.analytics.crm.error.client.ApplicationException: Error updating campaign reference data.
at com.sas.analytics.crm.util.SystemCheck.createMAException(SystemCheck.java:106)
at com.sas.analytics.crm.util.SystemCheck.handleExceptionForEJB(SystemCheck.java:83)
at com.sas.analytics.crm.flow.ejb.FlowBean.updateCampRefData(FlowBean.java:2672)
at com.sas.analytics.crm.flow.client.FlowDelegate.updateCampRefData(FlowDelegate.java:1214)
at com.sas.analytics.crm.cm.ejb.CampaignProxyImpl$22.run(CampaignProxyImpl.java:1894)
at com.sas.analytics.crm.cm.ejb.CampaignProxyImpl$22.run(CampaignProxyImpl.java:1778)
at com.sas.analytics.crm.cm.ejb.util.RunnableWithInstance.call(RunnableWithInstance.java:9)
at com.sas.analytics.crm.cm.ejb.util.WrappedRunnable.run(WrappedRunnable.java:78)
at com.sas.ci.services.common.services.asynchronous.SessionCountingRunnableQueue$QueueHandler.run(SessionCountingRunnableQueue.java:88)
at com.sas.analytics.crm.task.ejb.ClearedThreadLocalRunnable.run(ClearedThreadLocalRunnable.java:24)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.lang.NullPointerException
This problem happens only for migrated treatments from a previous release. New treatments work as they should.
As a workaround, remove the treatment from the campaign and re-attach it.
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 Server 2003 Standard Edition | 6.6 | |||
| Microsoft Windows Server 2003 Enterprise Edition | 6.6 | |||||
| Microsoft Windows Server 2003 Datacenter Edition | 6.6 | |||||
| Microsoft Windows NT Workstation | 6.6 | |||||
| Microsoft Windows 2000 Professional | 6.6 | |||||
| Microsoft Windows 2000 Server | 6.6 | |||||
| Microsoft Windows 2000 Datacenter Server | 6.6 | |||||
| Microsoft Windows 2000 Advanced Server | 6.6 | |||||
| Microsoft Windows 95/98 | 6.6 | |||||
| Microsoft Windows 10 | 6.6 | |||||
| Microsoft Windows 8.1 Pro x64 | 6.6 | |||||
| Microsoft Windows 8.1 Pro 32-bit | 6.6 | |||||
| Microsoft Windows 8.1 Enterprise x64 | 6.6 | |||||
| Microsoft Windows 8.1 Enterprise 32-bit | 6.6 | |||||
| Microsoft Windows 8 Pro x64 | 6.6 | |||||
| Microsoft Windows 8 Pro 32-bit | 6.6 | |||||
| Microsoft Windows 8 Enterprise x64 | 6.6 | |||||
| Microsoft Windows 8 Enterprise 32-bit | 6.6 | |||||
| Microsoft® Windows® for x64 | 6.6 | |||||
| Microsoft Windows Server 2003 for x64 | 6.6 | |||||
| Microsoft Windows Server 2008 | 6.6 | |||||
| Microsoft Windows Server 2008 R2 | 6.6 | |||||
| Microsoft Windows Server 2008 for x64 | 6.6 | |||||
| Microsoft Windows Server 2012 Datacenter | 6.6 | |||||
| Microsoft Windows Server 2012 R2 Datacenter | 6.6 | |||||
| Microsoft Windows Server 2012 R2 Std | 6.6 | |||||
| Microsoft Windows Server 2012 Std | 6.6 | |||||
| Microsoft Windows Server 2016 | 6.6 | |||||
| Microsoft Windows Server 2019 | 6.6 | |||||
| Microsoft Windows XP Professional | 6.6 | |||||
| Windows 7 Enterprise 32 bit | 6.6 | |||||
| Windows 7 Enterprise x64 | 6.6 | |||||
| Windows 7 Home Premium 32 bit | 6.6 | |||||
| Windows 7 Home Premium x64 | 6.6 | |||||
| Windows 7 Professional 32 bit | 6.6 | |||||
| Windows 7 Professional x64 | 6.6 | |||||
| Windows 7 Ultimate 32 bit | 6.6 | |||||
| Windows 7 Ultimate x64 | 6.6 | |||||
| Windows Millennium Edition (Me) | 6.6 | |||||
| Windows Vista | 6.6 | |||||
| Windows Vista for x64 | 6.6 | |||||