Problem Note 50762: Scheduling recurrent campaigns in SAS® Customer Intelligence Studio do not exceed 106 occurrences
 |  |  |  |  |
When you schedule a campaign in SAS Customer Intelligence Studio to recur daily for more than 106 days, the end date for the last occurrence is less than the end date that is set in the SAS® Marketing Automation schedule.
The solution for this problem is to add these options -Dsas.ci.maxNumOccurrences=1000 -Dsas.ci.maxExecutedOccurrences to JAVA_OPTIONS in the following locations:
- On the client machine that is running SAS Customer Intelligence Studio, add the options above in sasmaclient.in. This file is typically located in the C:\Program Files\SASHome\SASCustomerIntelligenceStudio\5.41 directory.
- In the middle tier, add the option above for either WebLogic, WebSphere, or JBoss (depending on which you are running) as follows:
- For WebLogic that is running the SAS Marketing Automation web application, add the options above in startup.bat or startup.sh.
- For WebSphere, add the options above at the end of the generic JVM arguments. These are typically located in the Application Servers/sasserver/Process Definition/Java Virtual Machine directory in the WebSphere Application Server console.
- For JBoss on Windows, add the options above at the end of the generic JVM arguments in the wrapper.conf. The file is typically located in the \JBossApplicationServer\server\SASServer6\ directory.
- For JBoss on UNIX, add the options above to JBoss-home-directory/bin/ and open the JBoss server start-up script file that is named SASServer6.sh
You need to restart the middle tier so that the settings can take effect.
You can increase the values of 1000 and 500, if necessary.
Notes
- The hard limit for occurrences in SAS® Marketing Automation 5.41 and earlier releases is 999. Occurrences beyond 998 fail to execute and the following error message is displayed:
s.analytics.crm.flow.MACommunicationNode - Occurrence number has exceeded maximum value (998) Current Occurrence: 999
If you need more than 999 occurrences, the only workaround is to save the campaign by selecting Save as. This resets the occurrence number to 1. The limit of 999 occurences is based on the structure of the SK values that are stored in the Common Data Model, which have a 3-digit limit. These limits have been removed in SAS® Customer Intelligence 6.1 and later.
- If you are using OS Scheduler instead of Platform LSF, the end date that is shown in the Windows Task Scheduler is still less than the end date that is set in the SAS Marketing Automation schedule. Click the Hot Fix tab in this note to access the hot fix for this issue.
For additional information related to this topic, see SAS Note 49957, "SAS® Marketing Automation Schedule Gantt chart might show an incorrect end date for recurring campaigns.”
Operating System and Release Information
| Product Family | Product | System | Product Release | SAS Release | ||
| Reported | Fixed* | Reported | Fixed* | |||
| SAS System | SAS Marketing Automation | Windows 7 Enterprise x64 | 5.41 | 6.1_M1 | 9.3 TS1M2 | 9.3 TS1M2 |
| Windows 7 Home Premium 32 bit | 5.41 | 6.1_M1 | 9.3 TS1M2 | 9.3 TS1M2 | ||
| Windows 7 Home Premium x64 | 5.41 | 6.1_M1 | 9.3 TS1M2 | 9.3 TS1M2 | ||
| Windows 7 Professional 32 bit | 5.41 | 6.1_M1 | 9.3 TS1M2 | 9.3 TS1M2 | ||
| Windows 7 Professional x64 | 5.41 | 6.1_M1 | 9.3 TS1M2 | 9.3 TS1M2 | ||
| Windows 7 Ultimate 32 bit | 5.41 | 6.1_M1 | 9.3 TS1M2 | 9.3 TS1M2 | ||
| Windows 7 Ultimate x64 | 5.41 | 6.1_M1 | 9.3 TS1M2 | 9.3 TS1M2 | ||
| Windows Vista | 5.41 | 6.1_M1 | 9.3 TS1M2 | 9.3 TS1M2 | ||
| Windows Vista for x64 | 5.41 | 6.1_M1 | 9.3 TS1M2 | 9.3 TS1M2 | ||
| 64-bit Enabled AIX | 5.41 | 6.1_M1 | 9.3 TS1M2 | 9.3 TS1M2 | ||
| 64-bit Enabled HP-UX | 5.41 | 6.1_M1 | 9.3 TS1M2 | 9.3 TS1M2 | ||
| 64-bit Enabled Solaris | 5.41 | 6.1_M1 | 9.3 TS1M2 | 9.3 TS1M2 | ||
| HP-UX IPF | 5.41 | 6.1_M1 | 9.3 TS1M2 | 9.3 TS1M2 | ||
| Windows 7 Enterprise 32 bit | 5.41 | 6.1_M1 | 9.3 TS1M2 | 9.3 TS1M2 | ||
| Microsoft Windows XP Professional | 5.41 | 6.1_M1 | 9.3 TS1M2 | 9.3 TS1M2 | ||
| Microsoft Windows Server 2012 Std | 5.41 | 6.1_M1 | 9.3 TS1M2 | 9.3 TS1M2 | ||
| Microsoft Windows Server 2012 Datacenter | 5.41 | 6.1_M1 | 9.3 TS1M2 | 9.3 TS1M2 | ||
| Microsoft Windows Server 2008 for x64 | 5.41 | 6.1_M1 | 9.3 TS1M2 | 9.3 TS1M2 | ||
| Microsoft Windows Server 2008 R2 | 5.41 | 6.1_M1 | 9.3 TS1M2 | 9.3 TS1M2 | ||
| Microsoft Windows Server 2008 | 5.41 | 6.1_M1 | 9.3 TS1M2 | 9.3 TS1M2 | ||
| Microsoft Windows Server 2003 for x64 | 5.41 | 6.1_M1 | 9.3 TS1M2 | 9.3 TS1M2 | ||
| Microsoft Windows Server 2003 Standard Edition | 5.41 | 6.1_M1 | 9.3 TS1M2 | 9.3 TS1M2 | ||
| Microsoft Windows Server 2003 Enterprise Edition | 5.41 | 6.1_M1 | 9.3 TS1M2 | 9.3 TS1M2 | ||
| Microsoft Windows Server 2003 Datacenter Edition | 5.41 | 6.1_M1 | 9.3 TS1M2 | 9.3 TS1M2 | ||
| Microsoft Windows 8 Pro x64 | 5.41 | 6.1_M1 | 9.3 TS1M2 | 9.3 TS1M2 | ||
| Microsoft Windows 8 Pro 32-bit | 5.41 | 6.1_M1 | 9.3 TS1M2 | 9.3 TS1M2 | ||
| Microsoft Windows 8 Enterprise x64 | 5.41 | 6.1_M1 | 9.3 TS1M2 | 9.3 TS1M2 | ||
| Microsoft Windows 8 Enterprise 32-bit | 5.41 | 6.1_M1 | 9.3 TS1M2 | 9.3 TS1M2 | ||
| Microsoft® Windows® for x64 | 5.41 | 6.1_M1 | 9.3 TS1M2 | 9.3 TS1M2 | ||
| Linux for x64 | 5.41 | 6.1_M1 | 9.3 TS1M2 | 9.3 TS1M2 | ||
| Solaris for x64 | 5.41 | 6.1_M1 | 9.3 TS1M2 | 9.3 TS1M2 | ||