Maximo Open Forum

 View Only

 Upgrading from 7.6.1.2(020) to 7.6.1.3(004) - receiving error message CTGIN5368E on the Feature Pack installation

  •   4
  • Maximo User Groups
Jennifer Romeiser's profile image
Jennifer Romeiser posted 02-21-2023 06:07

We are upgrading from 7.6.1.2 (020) to 7.6.1.3 (004) and receiving the error message "Operations-CTGIN5368E - An unexpected error occurred while obtaining the status of the application." 

#1: In WebSphere Application Services - Under Servers > Server Types > WebSphere Application Servers: We stopped MXSERVER.
#2 On Server, went to the Installation Manager under File>Preferences and added the zip file from Feature pack 76.1.3 click apply and ok.
#3 Using the Installation Manager - Click update (highlight IBM Trivoli's package) and Next. Confirmed that 7.6.1.3 versions are appearing under IBM Maximo Asset Management and IBM Maximo Trivoli's process automation engine. Read the license agreement, click Next - Completed without issue

#4 Under Configuration Program > Select Update Database and Build & Deploy EAR Files, Click Next. - Confirm that Update Summary show 7.6.1.3 and select Next and Finish.  - On the first step - Apply the changes to the database - we received the error message.

 

#4Nothing out of the norm and totally unexpected. Might anyone have a clue?

Ryan Medernach's profile image
Ryan Medernach posted 02-23-2023 17:18

Good afternoon Jennifer, 

I ran into this issue when setting up a demo 7.6.1.3 environment today. I'm assuming your database is a SQL server. 

Check this link out. https://www.ibm.com/support/pages/node/6615419

It looks like the new version of the JDBC forces encryption and the answer is to add the following to the jdbc entry 

;encrypt=false; 

P.S. Anyone from IBM reading this it sure would be nice to update the IFIX readme information with crucial information like this when a new issue is found directly related to a fix's with a readme file. It would have saved me some time looking for an answer this afternoon.

Also updated - You can also try this I was able to get my demo environment to connect and this is forcing the sslProtocol and trust the SQL servers certificates. You can see the link below.

https://www.ibm.com/support/pages/node/6953517

;sslProtocol=TLSv1.2;trustServerCertificate=true;

Jennifer Romeiser's profile image
Jennifer Romeiser posted 02-24-2023 14:13

Ryan,

Thank you SO MUCH! That is exacly what was needed. I had placed a ticket with IBM Support last week, and they didn't provide me with this specific link until this morning around 8:45 a.m. Thinking they must had read your post!! 

Craig Kokay's profile image
Craig Kokay posted 02-27-2023 23:53

As @Ryan Medernach mentioned, this is the fix, though would have been nice for IBM to have published the solution.

Related Content