Agent for virtual host : default did not initialized properly

book

Article ID: 225765

calendar_today

Updated On:

Products

SITEMINDER CA Single Sign On Secure Proxy Server (SiteMinder)

Issue/Introduction

CA Access Gateway is not running or working, server.log shows error during start up:

[08/Oct/2021:12:09:41-530] [INFO] - Initialize: [Agent Configuration = C:\Program Files\CA\secure-proxy\proxy-engine\conf\defaultagent\WebAgent.conf][Single Process Mode = true][retcode = -1][Initialized = false]
[08/Oct/2021:12:09:41-530] [ERROR] - [ERROR] Agent for virtual host : default did not initialized properly
[08/Oct/2021:12:09:41-749] [INFO] - Initialize: [Agent Configuration = C:\Program Files\CA\secure-proxy\proxy-engine\conf\myaccessagent\WebAgent.conf][Single Process Mode = true][retcode = -1][Initialized = false]
[08/Oct/2021:12:09:41-749] [ERROR] - [ERROR] Agent for virtual host : virtualhost did not initialized properly

Cause

Trusted host is no longer present in policy store. It was accidentally removed.

Hostname value can be found from agent side SmHost.conf.

You can verify this by searching the specific agent trusted hostname from admin ui on policy server side.

 

Environment

Release : 12.8

Component : SITEMINDER SECURE PROXY SERVER

Resolution

Re-register CA access gateway again with the working policy server will create new SmHost.conf.
Agent will connect again after agent registration.
 
Register a Trusted Host Using the smreghost Registration Tool
https://techdocs.broadcom.com/us/en/symantec-security-software/identity-security/siteminder/12-8/administrating/register-a-trusted-host-using-the-smreghost-registration-tool.html