Content Management and Capture

 View Only

 Nodes not able to connect to the bring up ICN client after Upgrade

Yasir Sultan's profile image
Yasir Sultan posted Wed February 12, 2025 05:58 PM

Keep getting this message after the upgrading the ICN. 

Prior to the all the nodes were responding fine. 


But since the upgrade none of the nodes are responding/connecting to the server to bring up the client. 

Did several reboots and cache clearing for each node separately. 

Rolled back to the previous version, 3.0.14, without much success. 

Never had any issues such as this while upgrading.

Chuck Hauble's profile image
Chuck Hauble posted Thu February 13, 2025 01:53 PM

Are you running on WebSphere?  Is the HTTP Server mapped correctly under Manage Modules for the Application? 

I have seen the deployment not map it correctly if you used the CMUI tool to do the deployment

Moshe Elbaz's profile image
Moshe Elbaz posted Fri February 14, 2025 06:16 AM

Try to re import the LTPA key from the CM  SERVER

Stephen Weckesser's profile image
Stephen Weckesser posted Wed February 19, 2025 04:49 PM

Check the JNDI data source in the web.xml.  Sometimes the data source is empty when the ear gets built and deployed. 

Depending on the version you are coming from, you might have to choose to update the profile in configmgr too. 

Also, check the schema.  Under the dbscripts/modified, find the schema and see if the schema is correct.  The schema is usually the same as the user but not always.  When the ear is built it may use the schema name even if you don't run the db scripts (I am not certain about this but it's easy enough to compare the actual schema with what's in the script).