Executing a campaign via sasmalauncher might fail when you use a proxy server. When you encounter this problem, the following error message is displayed in the SASCustIntellCore6.3.log or the sasmalauncher.log files:

Later, the following message is displayed in the SASCustIntellCore6.3.log file:

Because of these errors, sasmalauncher tries to execute the same campaign again. If the first campaign is still running, then the second execution (of the same campaign) will fail and log off from the session.

This problem occurs because the proxy server uses different hosts and ports for the Internal and External Connections. However, sasmalauncher does not use the Internal Connection settings. Instead, it always uses the External Connection settings, which cut off connections after a few minutes by default.

As a workaround, you can change the configured time-out value for the ProxyPass setting.

Note: Executing the same campaign in SAS^® Customer Intelligence Studio is successful.

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

Operating System and Release Information

A fix for this issue for SAS Marketing Automation 6.4 is available at:

A fix for this issue for SAS Marketing Automation 6.3 is available at: