"A connection could not be made to the scheduling server..." occurs when scheduling campaigns in SAS® Customer Intelligence Studio


This SAS KB article describes how to solve issues when you fail to schedule campaigns from SAS® Customer Intelligence Studio 6.6. When this issue occurs, the following pop-up message is commonly displayed:

"A connection could not be made to the scheduling server. Please contact your system administrator."

To circumvent this issue, do as follows:

Verify That the Scheduler Works

If you use the Platform Suite for SAS scheduler, check whether the lsid command works. This command works for Windows and Unix Operating Systems:

$ lsid

$ lsid
IBM Spectrum LSF Standard 10.1.0.9, Oct 16 2019
Copyright International Business Machines Corp. 1992, 2016.
US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

My cluster name is trcvxxx_cluster1
My master name is trcvxxx.trc.sas.com
Cluster in ISV mode : SAS
$

If you use Operating System Services on a Unix system, check that the user has permissions to run the at command. Log on as the lsfadmin user and run the following:

$ at -V
at version 3.1.20
$

Check the Permissions in SAS® Management Console

  1. The SAS System Services group must be a member of the Customer Intelligence Scheduling Users group.

    Customer Intelligence Scheduling Users ► Members ► Current Members: SAS System Services

  2. Ensure that the Groups and Roles tab does not contain a member.

    Customer Intelligence Scheduling Users ► Available Groups and Roles tab should not contain a member

  3. Ensure that the login defined for the Customer Intelligence Scheduling Users group is a valid Operating System account with a valid password for this user. The authentication domain is CISchedAuthDomain.

    Logins defined for Customer Intelligence Scheduling Users

  4. Customer Intelligence Services User must be a member of the SAS System Services group.

    Customer Intelligence Services User Properties ► Available Groups and Roles ► Member of: SAS System Services

  5. SAS Trusted User should also a member of the SAS System Services group.

    SAS Trusted User Properties ► Groups and Roles tab ► Available Groups and Roles: Analytical Data Set Builder Users ► Member of: SAS System Services

Check the Following Properties:

  1. The name of the Scheduling Server in the Advanced Properties for Customer Intelligence Core must match exactly with the Scheduling Server Name.

    Navigate to SAS Management Console ► Application Management ► SAS Application Infrastructure ► Customer Intelligence Core 6.6 ► Properties ► the Advanced tab.

    SAS® Management Console ► Application Management ► SAS Application Infrastructure ► Customer Intelligence Core 6.6 ► Properties ► the Advanced tab.

    Note: This example uses the Platform Process Manager. If you use the OS Scheduling Server, you need to check the name of the OS Scheduling Server.

    Server Manager ► Platform Process Manager - sasbap

    Note: You can copy and paste the name from Server Manager to the Customer Intelligence Core 6.6 Advanced Properties to ensure that the name is identical.

  2. In SAS Management Console, expand Environment Management ► Server Manager ► click the Scheduling Server (for example, Platform Process Manager). In the right window, navigate to Connection: Platform Process Manager ► Options. Check whether Options contains the correct port and host name and the correct Authentication domain.

    Connection: Platform Process Manager - sasbap Properties

  3. In SAS Management Console, navigate to Server Manager ► SASApp. Check whether the "SASApp MA Java Batch Server" points to the correct host.

    SASApp - MA Java Batch Server Properties ► Options ► Associated Machine: localhost

  4. If issues with scheduling still occur, enable trace as described below, which will provide more messages in the SASCustIntelCore6.6.log file:
    1. Save a backup of the current <sasconfig>\Lev1\Web\Common\LogConfig\SASCustIntelCore=log4j.xml file.
    2. Edit the SASCustIntelCore=log4j.xml file to enable DEBUG for com.sas.analytics.crm.persistence, as shown below:

      <logger name="com.sas.analytics.crm.persistence" additivity="false">
      <level value="DEBUG"/>
      <appender-ref ref="SAS_FILE"/>
      </logger>

Note: If you made any changes to the steps described above, it is mandatory that you restart the SAS Object Spawner on the SAS Compute Tier and SASServer6_x on the mid-tier because the current values are cached.