ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

CA Identity Governance Service will not start reporting Port Conflict

book

Article ID: 16583

calendar_today

Updated On:

Products

CA Identity Manager CA Identity Governance CA Identity Portal

Issue/Introduction



An attempt to start IG may result in following even though you checked to make sure none of the ports dedicated to IG application is in use by any other application on the system.

 

Error messages generated in the application log file at startup: 

__________________________________________________________________________________________________________________

2017-12-04 14:16:32 Commons Daemon procrun stdout initialized 

*********************************************************************************************************** 

* 

* 

* Launching CA Identity Governance... 

* Please make sure that all data sources point to the correct databases, and use the correct SQL logins 

* 

* 

*********************************************************************************************************** 

 

GM_JAVA_OPTS: -Dwicket.configuration=deployment -Dworkpoint.classpath.url=../Workpoint/ -Dorg.jboss.as.logging.per-deployment=false -Djboss.node.name=ca-gm-node-1 

Checking that all required ports are free... 

3 required ports are blocked 

 

Use "netstat -anob" to discover which processes block the ports. 

 

Press any key to continue . . . 

___________________________________________________________________________________________________________________

 

At this point, IG has results in failure to start.

Environment

Release:
Component: SGRM

Resolution

The error message could be a false positive. Meaning, it has nothing to do with ports but rather to do with Java. If you have recently upgraded Java version (e.g. from 1.7.x to 1.8.x) or somehow lost JAVA_HOME from your environment, please check and make sure JAVA_HOME is defined correctly pointing to correct version/path where it is installed.

After adjusting/correcting JAVA_HOME, attempt to restart.

If the problem still persist, try starting the service manually.

i.e.

As an 'administrator' , if you go to C:\Program Files\CA\RCM\Server\eurekify-jboss\bin and run the .bat file (i.e. eurekify.bat) manually from there.

Powered by Wolken Software