You might receive the following error from Oracle WebLogic when you attempt to log in to SAS Campaign Studio:

Caused by: weblogic.jms.common.JMSException: 
Error creating connection on the server.

The error is further defined in the WebLogic logs, as follows:

This message might appear if a firewall is in place and a callback process is being terminated. The Java client calls Oracle WebLogic on port 7001, and then Oracle Weblogic starts the Java Message Service and a bean that functions as a "listener" in order to monitor the status of the client connection. This listener in Oracle WebLogic is a Java class that is trying to connect back to the Java client (in this case, SAS Campaign Studio or SAS^® Management Console). The firewall stops this callback to the Java client, because the call is on a new port.

In addition to the preceding error, you might also see the following error if you are trying to create a definition in SAS Management Console:

If this problem occurs in SAS^® Customer Intelligence, then add the following JVM argument to the sasmaclient.ini file:

Adding this argument defines that SAS Customer Intelligence Studio shall use the same port for the calls back and forward.

If the error occurs in the SAS Customer Intelligence plug-ins for SAS Management Console, then modify the sasmc.ini file and add the same JVM argument as shown above.

The argument needs to be added before the -cp option in the command line arguments string:

CommandLineArgs=-Xms128m -Xmx1024m -Djava.system.class.loader=com.sas.app.AppClassLoader -Dsas.app.class.dirs="C:\Program
Files\SAS\SASMarketingAutomation\4.1" -Dsas.app.class.path=sas.analytics.crm.ma.app.jar;. -Dsas.ext.config=sas.java.ext.config -
Dweblogic.corba.client.bidir=true -cp sas.launcher.jar com.sas.analytics.crm.app.Client

Operating System and Release Information