Upgrade issues

1 

Restoring the earlier version of BMC TrueSight Infrastructure Management Server if the upgrade fails

When you upgrade the BMC TrueSight Infrastructure Management Server to 10.0, the installer automatically backs up the installation and configuration files of the earlier Infrastructure Management installation in the following folder:

• (Microsoft Windows) installationDirectory\BMC Software\ProactiveNet
• (Solaris or Linux) installationDirectory/BMC Software/ProactiveNet

However, the SAP SQL Anywhere database files and the cell configuration files are not copied into the folder. BMC recommends that you back up the database files and cell configuration files before upgrading the BMC TrueSight Infrastructure Management Server. For information about backing up the SAP SQL Anywhere database and the cell configuration files, see Prerequisites-for-upgrade.

2

A java.lang.NumberFormatException appears after upgrade

Explanation:
The pw\custom\pronet.conf file does not end with a new line.

User Response:
Open the pw\custom\pronet.conf file, and add a new line at the end. (Press Enter.)

3

The cell process does not run after upgrading with a non-root user

Explanation:
When upgrading the BMC TrueSight Infrastructure Management Server with a non-root user, the cell process does not run after the upgrade, and an error message is generated. This occurs only when a Utilities folder exists in the /var/tmp directory.

User Response:
Before upgrading the server with a non-root user, delete the Utilities folder from the /var/tmp directory.

4

The instance hierarchy is not displayed

Explanation:
For the instance hierarchy to work, you must upgrade all the remote agents to the same version and wait for the first scheduled autosync poll to occur.

User Response:
Upgrade all the remote agents, and wait for the first scheduled autosync poll to occur. After an autosync, the instances are displayed in the hierarchy on the Show Monitors, Group Matrix, Service Matrix, Monitor Matrix, Show Parent, and Show Children links on the graph windows. In Admin Auto, the Add children to the Group works as expected after the first scheduled autosync.

5

Navigation tree is missing

Explanation:
After the upgrade, the navigation tree is not displayed in the Infrastructure Management Console.

User Response:
Clear the browser cache. This might occur once after each upgrade.

6

Reusing customized local actions after upgrading

Explanation:
You can reuse customized local actions after upgrading BMC TrueSight Infrastructure Management Server.

User Response:
You can reuse customized local actions by completing one of the following procedures:
Procedure 1

1. Extract the localactions.jar file from the location to which you copied it during the upgrade.
2. Open the LocalAction.xml file and copy all customized local actions to installationDirectory\tomcat\webapps\localaction\localactions.jar. When copying customized local actions, replace all the <Role> tags with the <UserGroup> tag. Change the values of roles to groups because from this version of Infrastructure Management onwards, permission to access any local action depends on user groups.
3. Run the pw system start command to restart TrueSight Infrastructure Management server.
   
   Procedure 2
   1. Backup the localactions.jar file from the installationDirectory\tomcat\webapps\localaction.
   
   2. Copy the localactions.jar file from the location to which you copied it during the upgrade, and save it in the inatallationDirectory\tomcat\webapps\localaction location.
   
   3. Open installationDirectory\custom\conf\pronet.conf and add the following property: collectorPermissionBasedOn=2
   
   4. Run the following command on the client system to delete the .jar files related to the earlier versions of local actions:
   javaws -viewer

7

Child server status is not accurate

Explanation:
Even after upgrading the Child server, the status might display that the Child server version is lower than the Central Monitoring Administration version.

User Response:
Restart the TrueSight Infrastructure Management server of the Child server by running the pw system start command. 

8

Validation error message as 'More swap space required'

Explanation:
During upgrade, the installer validates the swap space and if there is less swap space as compared to the recommended space, the installer throws the validation error message as 'More swap space required'.

User Response:
Increase the swap space and run the upgrade again. For more information, refer the following links:

• (Windows): Changing the size of virtual memory on Windows
• (Linux): Increasing swap space on Linux

9

Resuming the upgrade if the preinstallation check fails

Before the upgrade process, Infrastructure Management runs a preinstallation check to check for the required settings and processes. If the check fails, an error message is displayed and the Next button is disabled. You cannot proceed to the upgrade.

Workaround: Restart the Infrastructure Management processes manually and resume the upgrade process.

10

Unable to log into the Infrastructure Management Server using a custom user

When you upgrade to the Infrastructure Management Server 10.0 and try to log into it, the internal server error or blank page is displayed. This issue occurs if the environment you are upgrading from (ProactiveNet 9.5, 9.6, or Infrastructure Management 9.6) contains any user group that has access to all Configuration Items (CIs) but does not have a Super Admin role. When you upgrade to the Infrastructure Management Server 10.0 and migrate such user group to the Presentation Server, the authorization profile for this user group is created with the information from all CIs. Therefore, when any user from this user group tries to log in, all CIs are updated with the access information and leads to timeout. 

Workaround: To resolve this issue, edit the authorization profile for such user group and provide 'unrestricted access' to CIs. For information about editing the authorization profile, see Editing-and-deleting-authorization-profiles.

12

Integration Service is stopped after Infrastructure Management installation

When the Infrastructure Management Server and Integration Service is installed on a same Linux or Solaris computer, after you upgrade the Infrastructure Management Server, the Integration Service is stopped. You must start the Integration Service manually.