Known issues and workarounds for BSM Interoperability 8.5.1 SP 2 and BSM Reference Stack 2.1

SW00415331

Performing a BMC ProactiveNet Performance Management extensions upgrade from version 8.6.02 to 8.6.02 SP1 might result in the following error displayed for the BMC Atrium Explorer plug-in:

BMC_PN - Atrium Explorer Plugin - Failure.

Update the shared application properties value for BMC_PN: Atrium Explorer Plugin to 8.6.03.

SW00415325

The following error message is displayed after upgrading BMC Remedy Service Request Management:

SRM upgrade from 7.6.04 to 7.6.04 SP2 has been completed successfully with a warning.

The warning text (caused by the data import of the pt_BR locale) includes the following information:

Reinstalling BMC Remedy Service Request Management might correct the issue.

A similar issue is referenced in the BMC Service Request Management Technical Bulletin 7.6.04 SP2 (dated October 14, 2011) with a workaround. Locate this technical bulletin on the Product Documentation area of BMC Support.

SW00414630
QM001727283

BMC ProactiveNet Performance Management displays a validation error message during an upgrade from version 8.6.02 to 8.6.02 SP1. The message states that a few files under the pw directory are locked and need to be changed to manual mode, and that the server needs to be restarted. After these actions are performed, the error message window continues to appear, blocking the upgrade.

Stop the BMC Patrol Agent Service and continue with the upgrade.

SW00415751

You cannot configure BMC Impact Integration for PATROL 3.1.10 with the mcxp utility.

The following configuration changes are suggested for BMC Impact Integration for PATROL 3.1.10 with the mcxp utility:

1. Make changes in the mcxp.conf file to use the TCP protocol to communicate with BMC PATROL Agent 3.9.00. For example: MCXPAgentTransport=tcp

2. Restart the mcxp process.

If you use BMC Impact Integration for PATROL 3.1.20 or BMC Impact Integration for PATROL 7, these configuration changes are not required.

SW00412929

After you install BMC Atrium Orchestrator Content, some .arx files might not be imported successfully.

Re-import the .arx files.

SW00412926

Files for the BMC BladeLogic Decision Support for Network Automation installation might be placed in an incorrect directory.

If you are installing with an Oracle database, install BMC BladeLogic Decision Support for Network Automation in the C:\Program Files directory.

For more information, see the product release notes.

SW00411479

After the installation of BMC BladeLogic Client Automation Discovery Integration for CMDB, BMC Atrium Integration Engine instance names might not be displayed in the BMC Atrium Integration Engine console.

Add the instance manually in the EIE:DataExchange form and run the BMC Atrium Integration Engine service.

SW00412533

In the BMC Service Model Editor, after you execute a promotion, the promotion preview dialog box might stop responding.

Ensure that you are using Java version 1.6.

SW00412530

When installing BMC Impact Portal 7.4.01, publishing server communication errors might occur.

When installing BMC Impact Portal 7.4.01, apply the publishing server patch 7.4.01.01.

Note: The patch is not provided under BMC Impact Portal in the BMC Electronic Product Distribution (EPD) directory, but is under BMC Performance Manager Portal 2.9.10. The patch is for BMC Impact Publishing Server PABPS7.4.

SW00405751
QM001717363

Using BMC Atrium Orchestrator Platform 7.6.01.04 and BMC Atrium Orchestrator Content 7.6.05 could result in an error. The following steps were used in testing:
1. Disable the SSH adapter and restarted the grid.
2. Upload the sent aroar on the grid.
3. Enable it with empty configuration.
4. Execute using the Autopilot utilities.

Upgrade from SSH 1.5 to 2.0.

SW00396342

BMC Remedy ITSM 7.6.04 SP1 does not support backward-compatibility with BMC Remedy AR System 7.6.03.
BMC Remedy ITSM 7.6.04 SP2 issues an error that prevents installation if BMC Remedy AR System is at version 7.6.03.

Upgrade BMC Remedy AR System before installing BMC Remedy ITSM 7.6.04 SP 2.

QM001715718

In BMC Cloud Lifecycle Management 2.1, during installation, entering an invalid Java path does not return an error to the installation planner.

Stop and restart the installation, and then enter a valid Java path during the installation.

SW00404060

Adding a Network Container with a BMC BladeLogic Network Automation Job Approval type requires an approval to add a Network Container.

You can create the Network Container by turning off the Enable Job Approval for Actions system parameter. Alternatively, you can delete the Job approval types. If you do so, the system no longer requires an approval for the job and Network Container creation should succeed.

QM001711574

In BMC Cloud Lifecycle Management 2.1, the created Orchestration user does not have the last name of Orchestrator. This naming mismatch does not cause problems for BMC Cloud Lifecycle Management.

If you install BMC Continuous Compliance for Server Automation, its related Task and Change templates expect that "Orchestrator" is the last name of the user account. BMC Continuous Compliance for Server Automation requires a user account with the last name "Orchestrator" to maintain its integration with BMC Remedy Change Management. If you have installed BMC Continuous Compliance for Server Automation, update the user account last name to "Orchestrator."

QM001717399

Some BMC Atrium Orchestrator 20.11.01 and 20.11.02 adapters are incompatible with BMC Cloud Lifecycle Management 2.1.

For compatible versions, see BSM-Interoperability-releases.

QM001717405

In BMC Atrium Orchestrator Content 20.11.01 and 20.11.02, Triage and Remediation assigns Allen Allbrook as an Assignee in the Task templates.

Modify the Triage and Remediation Task templates with the correct user (orchestrationuser).

SW00405624

Reinstalling BMC Analytics 7.6.04 after uninstalling it results in an exception.

The error might be generated on re-installation, but the installation is still successful.

SW00380507

BMC Atrium Orchestrator Platform and BMC Atrium Orchestrator Content servers on Linux systems are not automatically started after a system restart.

Manually restart the servers after a system restart.

SW00380508

In BMC BladeLogic (using RCPClient/NSH), for non-root installations, after installation, the NSHDIR environment variable should be set as post-installation configuration.

The NSHDIR environment variable should be set to the <NSHInstallationDirectory>\NSH\lib folder, and LD_LIBRARY_PATH should be set to <NSHInstallationDirectory>\NSH.

SW00379975

In BMC BladeLogic Decision Support for Server Automation on Linux, there is no preinstallation check for required packages (libstdc++ and libXm).

If you receive the libXm.so error while loading shared libraries, install the openmotif package. Then manually create a symlink for libXm.so.3 that points to the working libXm.so binary libXm.so.4.0.2. See the product documentation for details.

SW00379977

In BMC BladeLogic Network Automation, there is no preinstallation check if a valid "local user account" is used during the installation (Microsoft Windows and Linux).

Create a BMC BladeLogic Network Automation local user account before installing BMC BladeLogic Network Automation. See the product documentation for details.

SW00380186

In BMC BladeLogic Integration with Atrium on Windows, during the preinstallation check for connectivity using NSH during installation, a firewall issue might occur.

Turn the Windows firewall off before installing BMC BladeLogic Automation.

SW00380187

BMC BladeLogic Decision Support for Server Automation installed with Linux and Oracle Database does not have a preinstallation check for Oracle characters.

The Oracle databases created for the BMC BladeLogic OM and BMC BladeLogic Decision Support for Server Automation data warehouse must have the same character set.

SW00380256

In BMC BladeLogic Decision Support for Network Automation, databases have to be created before installation.

Create BMC BladeLogic Decision Support for Network Automation databases before installing. See the product documentation for details.

SW00388975

In BMC BladeLogic Decision Support for Network Automation on Windows Server 2008 R2, a Microsoft SQL Server Native client is needed during installation.

Install the SQL Server Native client before installing BMC BladeLogic Decision Support for Network Automation on Windows Server 2008 R2. For more information, see the product documentation.

SW00389065

During the installation of Integration for BMC Remedy Service Desk, you might encounter an error during installation using AR Server driver.exe.

Add the BMC_AR_SYSTEM_HOME path to the PATH system environment variable before installing.

QM001716849

In the BMC ProactiveNet Performance Management - BMC Cloud Lifecycle Management integration, you might not be able to see performance data from a VMware ESX host.

The CMDB TokenID format for an ESX host is hostname:domainname.
Configure the domain for ESX hosts correctly so that the TokenIDs generated by each side are not different.