SUPPORT

Select Your Region

Visit the Cary, NC, US corporate headquarters site

Americas

Europe

Middle East & Africa

Asia Pacific

View our worldwide contacts list for help finding your region

Americas

Europe

Middle East & Africa

Asia Pacific

Sign In

Get access to My SAS, trials, communities and more.

Sign Out

Get access to My SAS, trials, communities and more.

SAS Sites

sas.com
Support
Blogs
Communities
Developer
Curiosity
Videos

Documentation

Learn
Brand
PartnerNet
Merchandise
SUPPORT / SAMPLES & SAS NOTES
 

Support

Problem Note 47013: The communication status of the SAS® Marketing Automation campaign group optimization does not update correctly

DetailsHotfixAboutRate It

In SAS Marketing Automation, the communication status of a campaign group optimization is not updated correctly. This occurs when a campaign within the group is saved with a linked diagram. However, the linked diagram of the campaign, at this time, does not have connections to the data established. Later, when the connections are established in the linked diagram, the campaign group optimization fails to be updated with the correct status.

Attempting to set the optimization status for the campaign group results in a message that indicates that the campaign group is not ready for optimization.

As a workaround for this issue, you can open the campaign manually, open the Communication node, and resave the campaign. When you perform these steps, the campaign group optimization has the correct Ready status.

Click the Hot Fix tab in this note to access the hot fix for this issue.

After you apply the hot fix, you need to set the following option as a Java Virtual Machine (JVM) option for your Web application server:

       -Dsas.ci.dt.ConfirmCommsNotReadyForMOMA

The method for setting this option is different for each vendor of Web application servers. Check your instructions.html file to locate the JVM options for you Web application server.

The following example illustrates how to set the option for the JBoss Web Application Server, The SAS® Deployment Wizard sets default values for JBoss on the JAVA_OPTS environment variable that resides in C:\JBoss-installation-directory\bin\SASServer6.bat. Open the SASServer6.bat file and add the option discussed previously to the end of the JAVA_OPTS environment variable, as follows:

:start_as_script set JAVA_HOME=C:\jdk1.6.0_16 set JAVA_OPTS=-Xms1024m -Xmx2048m -XX:PermSize=512m -XX:MaxPermSize=512m -Xss256k -XX:NewSize=128m -XX:MaxNewSize=256m -XX:+UseConcMarkSweepGC -XX:+UseTLAB -XX:+DisableExplicitGC -XX:+CMSClassUnloadingEnabled -XX:+CMSPermGenSweepingEnabled -Dcom.sun.management.jmxremote -Djava.awt.headless=true -Djboss.platform.mbeanserver -Djavax.management.builder.initial=org.jboss.system.server.jmx.MBeanServerBuilderImpl -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Dsas.container.identifier=jboss -Dcom.sas.services.logging.disableRemoteList=true -Dcom.sas.services.logging.disableRemoteLogging=true -Dsas.jms.authentication.decorator=false -Dsas.svcs.http.max.connections=20 -Djava.net.preferIPv4Stack=true -Djava.net.preferIPv6Addresses=false -Dmulticast_udp_ip_ttl=1 -Dmulticast.address=239.21.16.70 -Dmulticast.port=8561 -Djava.security.policy="C:\jboss-4.2.0.GA\server\SASServer6\conf\sas.all.permissions.policy" -Djboss.home.dir="C:\jboss-4.2.0.GA" -Djboss.server.home.dir="C:\jboss-4.2.0.GA\server\SASServer6" -Dsas.deploy.dir="C:\jboss-4.2.0.GA\server\SASServer6\deploy_sas" -Dcom.sas.log.config.url=file:///C:/SAS/Config/Lev1/Web/Common/LogConfig/ -Dsas.auto.publish.port=8580 -Dsas.ci.dt.ConfirmCommsNotReadyForMOMA

When this option is set, campaigns within the Campaign group that have a Not Ready status are loaded and closed behind the scenes. As a result, the campaigns are viewed as ready, so no error is returned. This behavior, in turn, enables the Campaign Group with Optimization to have the correct Ready status.



Operating System and Release Information

Product FamilyProductSystemProduct ReleaseSAS Release
ReportedFixed*ReportedFixed*
SAS SystemSAS Marketing AutomationMicrosoft® Windows® for 64-Bit Itanium-based Systems5.4
Microsoft Windows Server 2003 Datacenter 64-bit Edition5.4
Microsoft Windows Server 2003 Enterprise 64-bit Edition5.4
Microsoft Windows XP 64-bit Edition5.4
Microsoft Windows 85.46.39.4 TS1M1
Microsoft Windows 95/985.4
Microsoft Windows 2000 Advanced Server5.4
Microsoft Windows 2000 Datacenter Server5.4
Microsoft Windows 2000 Server5.4
Microsoft Windows 2000 Professional5.4
Microsoft Windows 20125.46.39.4 TS1M1
Microsoft Windows NT Workstation5.4
Microsoft Windows Server 2003 Datacenter Edition5.4
Microsoft Windows Server 2003 Enterprise Edition5.4
Microsoft Windows Server 2003 Standard Edition5.4
Microsoft Windows Server 2003 for x645.4
Microsoft Windows Server 20085.46.39.4 TS1M1
Microsoft Windows Server 2008 for x645.46.39.4 TS1M1
Microsoft Windows XP Professional5.4
Windows 7 Enterprise 32 bit5.46.39.4 TS1M1
Windows 7 Enterprise x645.46.39.4 TS1M1
Windows 7 Home Premium 32 bit5.46.39.4 TS1M1
Windows 7 Home Premium x645.46.39.4 TS1M1
Windows 7 Professional 32 bit5.46.39.4 TS1M1
Windows 7 Professional x645.46.39.4 TS1M1
Windows 7 Ultimate 32 bit5.46.39.4 TS1M1
Windows 7 Ultimate x645.46.39.4 TS1M1
Windows Millennium Edition (Me)5.4
Windows Vista5.4
Windows Vista for x645.4
64-bit Enabled AIX5.46.39.4 TS1M1
64-bit Enabled HP-UX5.46.39.4 TS1M1
64-bit Enabled Solaris5.46.39.4 TS1M1
HP-UX IPF5.46.39.4 TS1M1
Linux5.46.39.4 TS1M1
* 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.