Problem Note 66768: A "java.lang.NullPointerException" error occurs when you execute campaigns in SAS® Customer Intelligence Studio
In SAS Customer Intelligence Studio, scheduled campaigns might fail with the following error message displayed in the SASCustIntelCore6.6.log:
ERROR [CIAsyncExec-48] [d5387de8adbf6c91:-3a3dc96d:17433c14024:1a13] [sasdemo] com.sas.analytics.crm.util.SystemCheck - Error executing campaign.
com.sas.analytics.crm.error.client.ApplicationException
at com.sas.analytics.crm.flow.ForkCampCommExecution.run(ForkCampCommExecution.java:117)
at com.sas.analytics.crm.security.SecurityExecutorServiceImpl$WrappedRunnable.run(SecurityExecutorServiceImpl.java:78)
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
If you review and execute the campaign manually in SAS Customer Intelligence Studio after the failure occurs, you might see that only one Communication node is visible in the diagram. However, a second Communication node appears in the Execute Now and Set Schedule windows. The campaign document also shows two Communication nodes.
Typically, this problem happens when campaigns are migrated from an earlier release of SAS Customer Intelligence.
To work around this problem, copy and paste all nodes into a new diagram.
Click the Hot Fix tab in this note to access the hot fix for this issue.
Operating System and Release Information
SAS System | SAS Customer Intelligence Studio | Microsoft® Windows® for x64 | 6.6 | | | |
Microsoft Windows 8 Enterprise 32-bit | 6.6 | | | |
Microsoft Windows 8 Enterprise x64 | 6.6 | | | |
Microsoft Windows 8 Pro 32-bit | 6.6 | | | |
Microsoft Windows 8 Pro x64 | 6.6 | | | |
Microsoft Windows 8.1 Enterprise 32-bit | 6.6 | | | |
Microsoft Windows 8.1 Enterprise x64 | 6.6 | | | |
Microsoft Windows 8.1 Pro 32-bit | 6.6 | | | |
Microsoft Windows 8.1 Pro x64 | 6.6 | | | |
Microsoft Windows 10 | 6.6 | | | |
Microsoft Windows 95/98 | 6.6 | | | |
Microsoft Windows 2000 Advanced Server | 6.6 | | | |
Microsoft Windows 2000 Datacenter Server | 6.6 | | | |
Microsoft Windows 2000 Server | 6.6 | | | |
Microsoft Windows 2000 Professional | 6.6 | | | |
Microsoft Windows NT Workstation | 6.6 | | | |
Microsoft Windows Server 2003 Datacenter Edition | 6.6 | | | |
Microsoft Windows Server 2003 Enterprise Edition | 6.6 | | | |
Microsoft Windows Server 2003 Standard Edition | 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 | | | |
64-bit Enabled AIX | 6.6 | | | |
64-bit Enabled Solaris | 6.6 | | | |
HP-UX IPF | 6.6 | | | |
Linux for x64 | 6.6 | | | |
Solaris for x64 | 6.6 | | | |
*
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.
Type: | Problem Note |
Priority: | high |
Date Modified: | 2020-12-23 13:46:02 |
Date Created: | 2020-10-13 10:00:23 |