Problem Note 19399: Multiple tasks have the same name error when you schedule or execute campaigns in SAS®Marketing Automation 4.4 or SAS®Customer Intelligence 5.1
It is possible for link nodes in SAS® Marketing Automation 4.4 or SAS®Customer Intelligence 5.1 Campaigns to become locked if the diagram is dynamic and they share a common ancestor diagram.
Expect to see an error similar to this in the macore logs.
yyyy-mm-dd hh:mm:ss,nnn [ERROR] User_Name
.analytics.crm.task.ejb.TaskExecutorBean - Execution error from task
sequence: 0-12 Flow Name
com.sas.analytics.crm.error.client.CodingException: Task sequence 0-12
Flow Name contains multiple tasks with the same name:
xxxxxxxxxxxxxxxx. One task created by node 'Node Name (same as below)'
and other task created by node 'Node Name (same as above)'
at
com.sas.analytics.crm.task.ejb.TaskSequence.execute(TaskSequence.java(Co
mpiled
Code))
at
com.sas.analytics.crm.task.ejb.TaskManagerHelper.executeTaskSequence(Tas
kManagerHelper.java:87)
at
com.sas.analytics.crm.task.ejb.TaskManagerHelper.executeSync(TaskManager
Helper.java:49)
at
com.sas.analytics.crm.flow.ejb.FlowBean.executeTasksParallel(FlowBean.ja
va:3329)
This will occur only if the upstream diagrams are linked and have had their counts cleared or if one of the cells(4.4) or diagrams(5.1) in the Communication is Dymanic. The solution is to ensure that the upstream link nodes do not reference a common ancestor diagram.
In SAS® Marketing Automation 4.4 for example:
If you have two diagrams,
Diagram1 with a single select node (Gender = 'F' and Gender = 'M'),
feeding a cell 'Cell1' OnChange. Update the counts on the cell and save.
Daigram2 with a link node from 'Cell1' and a select node (0 =<
Age =< 20)—feed these into an AND node, then a cell 'Cell2' OnChange.
Update the counts and save.
A communication with two link nodes,
Link1 fed by Cell1
Link2 fed by Cell2. Mark the Exclude
check box
AND these together and feed the results through an OnChange Cell (Cell3)
into the communication.
If you schedule and execute this campaign then everything works OK.
If you clear the node counts on all diagrams and schedule the campaign
or make Cell3 Dynamic, you will see the error.
To work around this, simply save a copy of the first diagram under a
different name (Dagram3 with link cell Cell4) and replace the Cell1
link in the Campaign diagram with a link to Cell4.
Select the Hot Fix tab in this note to access the hot fix for this issue.
Operating System and Release Information
SAS System | SAS Marketing Automation-Server | Microsoft Windows 2000 Server | 4.4 | | | |
Microsoft Windows Server 2003 Enterprise Edition | 4.4 | | | |
Microsoft Windows Server 2003 Standard Edition | 4.4 | | | |
Microsoft Windows XP Professional | 4.4 | | | |
Microsoft Windows Server 2003 Datacenter Edition | 4.4 | | | |
Microsoft Windows 2000 Professional | 4.4 | | | |
Microsoft Windows 2000 Datacenter Server | 4.4 | | | |
Microsoft Windows 2000 Advanced Server | 4.4 | | | |
64-bit Enabled Solaris | 4.4 | | | |
Solaris | 4.4 | | | |
AIX | 4.4 | | | |
64-bit Enabled AIX | 4.4 | | | |
HP-UX IPF | 4.4 | | | |
*
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: | medium |
Topic: | System Administration ==> Servers
|
Date Modified: | 2008-07-03 09:51:08 |
Date Created: | 2007-01-22 11:49:16 |