When you schedule a campaign group in SAS Customer Intelligence, the domain ID might not be added in Microsoft Windows operating environments. When this situation occurs, you might see the following error message.

Caught exception
ApplicationException
Cause message is Bad username or password.
ERROR 08:Jul:2014 @ 06:01:03:987: EXCEPTION
ERROR Additional information: UserID = sasdemo context = XXX
ERROR 08:Jul:2014 @ 06:01:03:995: EXCEPTION
ERROR 20 Unable to log on to application server
ERROR 20 Unable to log on to application server
com.sas.analytics.crm.ma.launcher.LaunchException: 20 Unable to log on to application server

A command line similar to the following command line is created automatically by SAS Customer Intelligence Studio:

However, the command with the corrected domain ID is as follows:

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

With the hot fix, a new Java argument is introduced: -Dsas.ci.CampaignGroupScheduleWithDomainQualifiedUser-ID

1. For Windows environments in which the servers are started as Windows services, navigate to the SAS-configuration-directory\Lev1\Web\WebAppServer\SASServer6_1\conf directory and add the new argument to the wrapper.conf file, as shown below:
   
   wrapper.java.additional.XX=-Dsas.ci.CampaignGroupScheduleWithDomainQualifiedUser-ID

   In this argument, XX represents the next number in the sequence that already exists in the file. Modify XX to be the next number in that sequence.

2. Restart the middle tier so that the setting can take effect.

Operating System and Release Information

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