TM1 Forum

Hi Guys,

Anyone encountered this error below when accessing Ops Console? Basically, this error pops up after I update the expired SSL certificates on my customer's server which is using version 10.2.2 FP4. I still can access TM1 Web and PM Hub Admin page normally.


Here are the details. I had tried few fix pack versions on my vbox by following the IBM technote.

(1) 10.2.2 FP4
Before SSL cert update: Able to access Ops Console.
After SSL cert update: HTTP Status 500 error.
Steps on performing SSL cert update: http://www-01.ibm.com/support/docview.w ... wg21991546

(2) 10.2.2 FP5
Before SSL cert update: Able to access Ops Console.
After SSL cert update: Able to access Ops Console.
Steps on performing SSL cert update: http://www-01.ibm.com/support/docview.w ... wg21991545

(3) 10.2.2 FP6 IF1
Before SSL cert update: Able to access Ops Console.
After SSL cert update: HTTP Status 500 error.
Steps on performing SSL cert update: http://www-01.ibm.com/support/docview.w ... wg21991545

For test cases (1) and (3), If I revert back / undo the SSL cert update steps, I am able to access Ops Console again. What is the real thing that gives problem to Ops Console after the SSL cert update?

Issue 1 - Using the Technote -
After Point #14, but before #15, delete the 3 directories in the Tomcat working directory (pmhub/pmpsvc/tm1web)
Point #15 between the 2nd & 3rd steps, do a save in the cognos configuration
Then update settings in PMhub to use a FQDN

Issue 3 - Have you taken into account that there is an additional setting in the Cognos Configuration that uses only TLS 1.2?

dsproffitt wrote:Issue 1 - Using the Technote -
After Point #14, but before #15, delete the 3 directories in the Tomcat working directory (pmhub/pmpsvc/tm1web)
Point #15 between the 2nd & 3rd steps, do a save in the cognos configuration
Then update settings in PMhub to use a FQDN

Issue 3 - Have you taken into account that there is an additional setting in the Cognos Configuration that uses only TLS 1.2?

Hi,

Thanks for the reply. Will test out the steps for Issue 1.
I am not aware of the Issue 3 additional settings. Mind to elaborate further?

dsproffitt wrote:Issue 1 - Using the Technote -
After Point #14, but before #15, delete the 3 directories in the Tomcat working directory (pmhub/pmpsvc/tm1web)
Point #15 between the 2nd & 3rd steps, do a save in the cognos configuration
Then update settings in PMhub to use a FQDN

Issue 3 - Have you taken into account that there is an additional setting in the Cognos Configuration that uses only TLS 1.2?

For Issue 3, I think I found what you meant from here:
http://www-01.ibm.com/support/docview.w ... wg27048181

dsproffitt wrote:Issue 1 - Using the Technote -
After Point #14, but before #15, delete the 3 directories in the Tomcat working directory (pmhub/pmpsvc/tm1web)
Point #15 between the 2nd & 3rd steps, do a save in the cognos configuration
Then update settings in PMhub to use a FQDN

Issue 3 - Have you taken into account that there is an additional setting in the Cognos Configuration that uses only TLS 1.2?

For issue 1, had follow and tested the steps but the same problem still persist.