Problem Note 54079: An error occurs and campaign execution fails when you use migrated Communication nodes with custom detail tags in SAS® Customer Intelligence 6.3
Executing a campaign fails and the following error occurs in the SASCustIntelCore6.3.log file when you use a migrated Communication node that contains migrated custom detail tags:
2014-07-16 11:14:44,826 ERROR [tomcat-http--40]
[764242e3a707e07d:-4d9bebbf:1473a8b830c:-943] [I003253].cm.ejb.CommunicationDefinitionProxyImpl -
Encountered client exception:unknown
field id: CommTagActioncode
java.lang.RuntimeException: unknown field id: CommTagActioncode
at com.sas.analytics.crm.export.client.ExportDefinitionLineItemDO.updateExportDO(ExportDefinitionLineItemDO.java:539)
at com.sas.analytics.crm.export.client.ExportDO.updateDO(ExportDO.java:892)
at com.sas.analytics.crm.export.client.ExportDO.updateDO(ExportDO.java:840)
at com.sas.analytics.crm.flow.MAExportBaseNode.computeExportDOList(MAExportBaseNode.java:4510)
at com.sas.analytics.crm.cm.ejb.CommunicationDefinitionProxyImpl.updateExportsForCommDefinition
(CommunicationDefinitionProxyImpl.java:332)
at com.sas.analytics.crm.cm.ejb.CommunicationDefinitionProxyImpl.saveCommunicationDefinition
(CommunicationDefinitionProxyImpl.java:234)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
The same error occurs when you open or modify the communication definition. If you open and save a Communication node in a migrated campaign, an error message indicates that the tags in the communication are unknown.
As a workaround, you can remove the tags from the selected fields in the export window and add then again in the same window.
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.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 |
*
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: | 2014-11-07 16:16:15 |
Date Created: | 2014-09-09 08:18:49 |