System Health 9.50 upgrade failure issue

  • KM03249955
  • 19-Sep-2018
  • 21-Dec-2018

Summary

System Health 9.50 upgrade failure issue

Question

We are trying to upgrade System Health as part of APM solution from 9.26 to 9.50 version. but while installing 9.50 we are getting errors at the point where it tries to install "SystemHealthCore 9.50.081", wherein it says "No version of HPE System Health Application Component has been found".Here are few entries from Logs:-2018-09-07 08:39:02,732 INFO - Installing : package SystemHealthCore 9.50.081 (HPE System Health Application Component) 2018-09-07 08:39:05,872 INFO - No version of HPE System Health Application Component has been found2018-09-07 08:39:,872 INFO - Logfile for SystemHealthCore package installation is located at : C:\Users\ApData\Local\Temp\MicroFocusOvInstaller\SystemHealth_09.50\Package_msi_SystemHealthCore_install.log2018-09-07 08:39:05,872 INFO - 1. attempt verifying the existence of the package SystemHealthCore 9.50.081 (HPE System Health Application Component) failed.2018-09-07 08:39:05,872 INFO - 2. attempt verifying the existence of the package SystemHealthCore 9.50.081 (HPE System Health Application Component) failed.2018-09-07 08:39:05,872 INFO - 3. attempt verifying the existence of the package SystemHealthCore 9.50.081 (HPE System Health Application Component) failed.2018-09-07 08:39:05,872 INFO - 4. attempt verifying the existence of the package SystemHealthCore 9.50.081 (HPE System Health Application Component) failed.2018-09-07 08:39:05,872 INFO - 5. attempt verifying the existence of the package SystemHealthCore 9.50.081 (HPE System Health Application Component) failed.2018-09-07 08:39:05,872 INFO - 6. attempt verifying the existence of the package SystemHealthCore 9.50.081 (HPE System Health Application Component) failed.2018-09-07 08:39:05,872 INFO - 7. attempt verifying the existence of the package SystemHealthCore 9.50.081 (HPE System Health Application Component) failed.2018-09-07 08:39:05,872 INFO - 8. attempt verifying the existence of the package SystemHealthCore 9.50.081 (HPE System Health Application Component) failed.2018-09-07 08:39:05,872 INFO - 9. attempt verifying the existence of the package SystemHealthCore 9.50.081 (HPE System Health Application Component) failed.2018-09-07 08:39:05,872 INFO - 10. attempt verifying the existence of the package SystemHealthCore 9.50.081 (HPE System Health Application Component) failed.2018-09-07 08:39:05,872 ERROR - Failure installing : package SystemHealthCore 9.50.081 (HPE System Health Application Component) 2018-09-07 08:39:44,714 INFO - User requested to rollback this installation.

Answer

The first thing SysH attempts to do after full model sync is to invoke JMX on port 29601 to get the model.

How to add a JBoss user

On each Gateway server and Data Processing server used to connect to BSM, add an application user
to JBoss.

1. From a terminal window, go to the BSM folder.

For Linux platform: cd /opt/HP/BSM/

For Windows platform: cd %TOPAZ_HOME%\bin

2. Run the following script:
For Linux platform: ./jboss-as/bin/add-user.sh
For Windows platform: add_jboss_user.bat
3. Select the type of user to add. Select b to add an application user (application-users.properties).
4. Type a user name and password for this user.
5. Leave the response to the groups question blank unless you need the user to belong to a group.
6. Type No to answer the question Is this new user going to be used for one AS process to connect to another AS process.

From System Health please:

1) Go to System Health server
2) Stop service
3) Run Configuration tool
4) Complete the information
5) In the second step for user and password for the application use the JBOSS user and password