Information
Unsupported content This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Upgrade issue with BMC Server Automation


This topic describes issues you might encounter during upgrade. It contains the following sections:

BMC Server Automation upgrade fails due to one or more products running on the system

If you are running the BMC Server Automation Console, BladeLogic Network Shell, or other BMC Server Automation products (except for the RCSD Agent) on the target system, the installer fails to upgrade the BMC Server Automation product without an explanatory error message. This issue occurs because certain product files might be locked.

If the installation completes with a status of Fail, click View Log on the Installation Summary panel to verify the reason. If the failure is the result of the BMC Server Automation Console or other BMC Server Automation product running on the target system, perform the following steps:

  1. Stop the BMC Server Automation Console or BMC Server Automation product on the target system before launching the upgrade of the BMC Server Automation product.
  2. If you experience the failure during the installation or if the post-installation configuration failed, perform the following steps to remove the CONFIGURATION_BSA_COMPLETE property. :
    1. Open the <bsaInstallDir>\OpsManagerInstalledConfiguration.xml file.
    2. Delete the false value from CONFIGURATION_BSA_COMPLETE.
    3. Modify it from:

      <property>
        <name>CONFIGURATION_BSA_COMPLETE</name>
        <value>true</value>
      </property>

      to:

      <property>
        <name>CONFIGURATION_BSA_COMPLETE</name>
        <value></value>
      </property>
  3. (Linux only) If post-installation configuration fails because ports#9700 or port #9701 are in use, you can find the exception displayed in the ../NSH/br/AppServerLauncher.log file. Perform the following steps:

    1. Open the BMC Server Automation host.
    2. Open /etc/services in a text editor (for example, vi). 
    3. Search for 9700 and 9701.
    4. Comment out those lines.
    5. Perform the previous steps to remove the CONFIGURATION_BSA_COMPLETE property.
    6. Reboot the target BMC Server Automation host.
  4. Restart the installer.

BMC Cloud Lifecycle Management installation fails to detect and integrate with BMC Server Automation

BMC CLoud Lifecycle Management installer fails to detect and integrate BMC Server Automation product on the target server. This issue occurs because the APPSERVER entry was not present in the Version file. To workaround this issue, perform the following steps:

  1. Open the <bsaInstallDir>\Version file in a text editor (for example, vi). 
  2. Add an entry for the application server (for example, APPSERVER=8.7.00.256) and save the file.
  3. Click Previous and then Next on the BMC CLoud Lifecycle Management installation program to re-initiate integration. 

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

BMC Cloud Lifecycle Management 4.7