Identity Portal User Console is not available (Main Connector is down or not defined)
search cancel

Identity Portal User Console is not available (Main Connector is down or not defined)

book

Article ID: 438240

calendar_today

Updated On:

Products

CA Identity Portal

Issue/Introduction

Identity Portal Console is not available due to the Main Connector is down.

When connector is attempted to start manually via IP Management Console, a pop-up window appears with error message: "Reload connector failed".

Connector settings -> Managed Object Attributes: column "Backend Name" contains messages: "No backend names for this connector"

IP server log contains the following messages:

2026-04-22 22:45:05,278 INFO  [com.idmlogic.sigma.connector.ca.tews.DynamicWSService] (ServerService Thread Pool -- 85) Start generate java from the wsdl
2026-04-22 22:45:05,536 INFO  [stdout] (ServerService Thread Pool -- 85) Loading FrontEnd jaxws ...
2026-04-22 22:45:05,614 INFO  [stdout] (ServerService Thread Pool -- 85) Loading DataBinding jaxb ...
2026-04-22 22:45:05,660 INFO  [stdout] (ServerService Thread Pool -- 85) wsdl2java -b file:/opt/CA/IdentityPortal/IdentityPortal/temp/output/tews_binding.xml -d /opt/CA/IdentityPortal/IdentityPortal/temp/output -verbose -keep -compile -classdir /opt/CA/IdentityPortal/IdentityPortal/temp/output -clientjar caimClient.jar file:/opt/CA/IdentityPortal/IdentityPortal/temp/output/filtered.wsdl
2026-04-22 22:45:05,661 INFO  [stdout] (ServerService Thread Pool -- 85) wsdl2java - Apache CXF 3.0.12
2026-04-22 22:45:05,661 INFO  [stdout] (ServerService Thread Pool -- 85) 
2026-04-22 22:45:05,913 ERROR [com.idmlogic.sigma.connector.ca.tews.DynamicWSService] (ServerService Thread Pool -- 85) Could not generate ObjectFactory class: org.apache.cxf.tools.common.ToolException: org.apache.ws.commons.schema.XmlSchemaException: Attempt to set empty name.

Loaded WSDL file via http://<IM IP address>/iam/im/TEWS6/identityEnv?wsdl contains (replace identityEnv if necessary):

<xs:element name="">

 

 

 

Environment

vApp IM, IP 14.5

Cause

WSDL file contains elements with incorrect names, e.g. <xs:element name="">.

This can be caused by IM tasks incorrectly configured or exposed via web services by mistake.

 

Resolution

In the loaded WSDL file, find names of the task(s) containing incorrect names. Fix or disable these tasks via the IM User Console. Check (via URL above) that the new WSDL file contains no incorrect names. Start the IP Main Connector.

Powered by Wolken Software