CA Access Gateway (SPS) fails to deploy CHS with error: SmHostConf does not exist
search cancel

CA Access Gateway (SPS) fails to deploy CHS with error: SmHostConf does not exist

book

Article ID: 441370

calendar_today

Updated On:

Products

CA Single Sign On Agents (SiteMinder) CA Single Sign On Secure Proxy Server (SiteMinder) SITEMINDER CA Single Sign-On

Issue/Introduction

After upgrading or installing CA Access Gateway (SPS) 12.8 or higher (including 12.9), the CHSContextListener fails to initialize. The following error is reported in the logs:

2026-05-19 06:38:24 ERROR CHSContextListener:- Deployment of CHS failed due to incorrect configuration.
com.ca.federation.cloud.ConfigurationException: SmHostConf does not exist

Cause

The Cloud Http Service (CHS) cannot locate the required host configuration file. This typically occurs because the SmHostConfPath parameter is empty or incorrectly defined in the CHS configuration properties (1).

Resolution

To resolve this issue, manually define the path to the SmHost.conf file (1):

  1. Stop the Access Gateway.
  2. Locate your SmHost.conf file. By default, this is found in:

    <SPS_HOME>/proxy-engine/conf/

  3. Open the chsConfig.properties file for editing. This file is located at:

    <SPS_HOME>/Tomcat/webapps/chs/WEB-INF/classes/config/chsConfig.properties

  4. Locate the SmHostConfPath parameter and add the absolute path to your SmHost.conf file.
  5. Save the changes.
  6. Start the Access Gateway.

Additional Information

  1. Credential Selector Page is Not Displayed