Resolved Issues

Known Issues

General

404 error appears during upgrade
When upgrading either the Windows or RHEL version of vCenter Operations Manager from 5.0 or 5.0.1 to 5.8 directly or in any chain upgrade path (for example, 5.0 > 5.7.1 > 5.8), the UI displays a "404 error" and the following NullPointerException error is written to the localhost.XXX.log (tomcat\logs\): SEVERE: Exception sending context initialized event to listener instance of class com.integrien.alive.ui.util.MainPortalListener java.lang.NullPointerException at com.integrien.alive.ui.util.WebProperties.loadProperties(WebProperties.java:117)Workaround: Add the following lines to the web.properties file in <installation_directory>\user\conf\web.

#maxMetricsPerAlertToPlot The maximum number of metrics to plot for a consolidated alert in a single pass
maxMetricsPerAlertToPlot=25

#tagPickerMaxResourcesPerNode the maximum number of resources per node displayed in tagpicker
tagPickerMaxResourcesPerNode=300

System performance impacts data collection
A large vCenter Management Operations deployment that manages many vCenters can experience a computational bottleneck when calculating world object group metrics during every data collection cycle. Workaround: The Analytics virtual machine in vCenter Operations Manager dynamically disables the world metrics calculation. No manual intervention is required.

In the vCenter Operations Manager custom environment, the datastore count in the Custom Overview displays zero.
When the Datastore tag in the Environment Overview treeview is expanded, all of the listed datastores display datastore count "0". Resources related to the selected datastore are not visible.Workaround: None

The export to .csv file fails if there is no file name specified in Conf.properties file
If you configure the Conf.properties file to export data to .csv file, and you provide the path of the file, the Repository Adapter does not create the file under the path specified in the conf.properties file.Workaround: Include a file name with the file path.

A resource that is in maintenance mode in the vCenter cannot be permanently removed from maintenance mode in vCenter Operations Manager.
vCenter Operations Manager pulls maintenance mode data from the vCenter, and puts resources in manual maintenance mode in vCenter Operations Manager. While you can remove a resource from maintenance mode in vCenter Operations Manager, during the next collection cycle, the resource is put back into maintenance mode. Workaround: There is no workaround. If a resource is in maintenance mode in the vCenter, do not remove the resource from maintenance mode in vCenter Operations Manager.

NoClassDefFoundError in Tomcat log
Hyperic API Adapter collection does not occur when using the standalone version of vCenter Operations Manager. NoClassDefFoundError appears in the Tomcat log. This is because two JAR files are missing from the directory $ALIVE_BASE/tomcat/webapps/HttpPostAdapter/WEB-INF/lib. Workaround: Copy the following files from $ALIVE_BASE/common/lib to $ALIVE_BASE/tomcat/webapps/HttpPostAdapter/WEB-INF/lib and restart the web service:

commons-logging-1.1.jar

commons-collections-3.1.jar

Unable to uninstall non-English language versions
When attempting to uninstall a non-English language version of vCenter Operations Manager on Windows, all selections on the uninstall menu are grey and inactive.Workaround: Launch the installer, choose English and re-install using the installation wizard. Then uninstall normally.

Unable to install vmware-om-adapter on Windows Standalone system
When vCenter Operations Manager is upgraded, the path to the JRE is lost. During the VMware adapter upgrade, an error message appears: "Could not find a valid Java virtual machine to load. You may need to reinstall a supported Java virtual machine." Workaround: After upgrading vCenter Operations Manager, add '
<VCOPS_BASE>/jre/bin' to the path environment variable and run the installer. For example, add C:\vmware\vcenter-operations\jre\bin to the path environment variable.

vCenter Server health badge and metric profile change
Changing the metric profile (from Balanced Profile to Full Profile or from Full Profile to Balanced) can affect the active fault score of a vCenter Server object. The fault badge score will be reset to zero (0) from a previous score although the fault alert is still active. This can directly affect the health badge of the vCenter Server object. This is specific only to the vCenter Server objects. Fault badges of other objects are not affected by profile changes.Workaround: To change Fault and health badge scores to their previous state, restart the collector.

Some custom interface widgets lose configuration settings after upgrading from 5.0 hotfix to 5.8
The Size By, and Color By settings selections highlights for Heat Maps are lost after upgrading, but the Heat Map displays data for the selected options only.
The selection highlighting for Metric Weather Map, and Top-N Analysis widgets is lost after upgrading, but the filtering criteria displays the selected metric.Workaround: Before you upgrade from 5.0, remove the widget configurations for the Heat Maps, Metric Weather Map, and Top-N Analysis widgets.

The feature to edit the eventlist.txt file settings is not supported in 5.x releases
In vCenter Operations Enterprise 1.0.2, you can edit the eventlist.txt file to specify that certain events can generate alerts. This feature is documented in the vCenter Operations Administration Guide (Custom UI); however, it is not supported in vCenter Operations Manager 5.x.Workaround: None.

The CPU load heat map displays the wrong color
In the custom interface, the CPU load heat map under Heatmaps dashboard > CPU Load widget > Hosts by CPU Usage, displays the color for memory usage instead of CPU usage. This applies to upgrades from vCenter Operations Manager 5.7.1 or 5.7.2 to 5.8. It does not apply to a new installation of vCenter Operations Manager 5.8.Workaround: To configure the correct color display for the CPU Load Widget:

Select the CPU Load Widget and click the edit widget icon.

From the Edit screen, choose the CPU Usage from the "color by" option and choose Usage (%).

Click the update selected configuration icon (image of a disk).

Click OK to save the configuration.

Custom views and reports are overwritten after upgrade
If you upgrade to vCenter Operations Manager 5.8, and your custom views or reports are overwritten, it is because you are using the same view or report key as our out-of-the-box view and report key for 5.8.Workaround: To recover your version of a custom view or report, find the corresponding XML that contains your view or report definition. Change the view or report key and run the "update" command.

After upgrading, no metrics display in the EMC Storage Dashboard
If you upgrade from vCenter Operations Manager 5.6.1 to 5.7.x , and have EMC VNX adapters, no metrics display in the EMC Storage Dashboard if you are using Firefox.Workaround: Use Chrome or Internet Explorer instead of Firefox.

After upgrading to 5.8, the Support Dashboard reports the error:
'Not all key information was found....'
When you select Admin > Support > Info > System Tools and click the "Go to Support Dashboard" button, the following error message displays: "Not all key information was found..." This error can occur if you use remote collectors or change the name of a local collector.Workaround: After the upgrade, edit the widget so that all of the collectors are selected.

Adapter instance test fails if you click the Test button too soon after installing the adapter
During adapter installation, you click the Describe icon to begin the describe process. The Collector restarts approximately two minutes after the describe process is finished (the "Describe done" status appears in the user interface). If you configure an adapter instance and click the Test button before the Collector has a chance to restart, the test fails.Workaround: Because the duration of the describe process can vary, wait at least 10 minutes before you click the Test button after you install an adapter.

After upgrading an adapter, the collector.log reports an exception error
After upgrading an adapter on vCenter Operations Manager installations on Widows and Linux operating systems, the collector.log reports the errors: "java.lang.NoSuchMethodError: org.apache.http.conn.scheme.Scheme""java.lang.NoClassDefFoundError: com/vmware/vim/vmomi/client/http/impl/HttpConfigurationCompiler."These errors are caused by old jar files that should have been deleted during the adapter upgrade.Workaround: Before upgrading the adapter, stop vCenter Operations Manager services, install the adapter, then start the vCenter Operations Manager services. If the duplicate jar files are not deleted, and the collector.log continues to report the errors, repeat the workaround.

Tomcat server does not start after upgrading to vCenter Operations Manager 5.8
The Tomcat server fails to start and generates an exception similar to "SEVERE: Exception starting filter struts Unable to load configuration. - [unknown location]"
This problem occurs when InstallAnywhere could not remove the old .jar files and there is a conflict between the old and new .jar files.Workaround: Find the conflicting struts .jar files in $ALIVE_BASE/tomcat/webapps/ROOT/WEB-INF/lib/, remove or rename the old .jar files, and restart the Tomcat server. For example, rename or remove old $ALIVE_BASE/tomcat/webapps/ROOT/WEB-INF/lib/struts2-core-2.2.1.1.jar file to resolve the conflict with a newly installed
$ALIVE_BASE/tomcat/webapps/ROOT/WEB-INF/lib/struts2-core-2.3.4.1.jar file.

vCenter Operations Manager custom interface might stop responding after an upgrade
The vCenter Operations Manager custom interface might stop responding about a day after an upgrade. Existing user sessions remain open, but you cannot create new login sessions. Views stop responding and data collection stops.
This problem occurs because the upgrade process does not check the database deployment and table space configuration. If a third party made custom table space modifications between updates (for example, to improve performance), the upgrade can place the indexes into the wrong table space and the data table space can exceed its allocated space requirement. This problem can also occur if the default table space becomes full and no modifications are applied between updates. Workaround: Use one of the following workarounds, depending on the cause of the problem:

After the upgrade, migrate the indexes to the appropriate table space.

After the upgrade, revert the database to the default configuration on a larger table space.

Disk Space metrics collection fails after upgrading vCenter Operations Manager
Disk Space metric collection from vCenter Storage Monitoring Service might fail after upgrading from vCenter Operations Manager version 1.0.x to version 5.6.
This failure can lead to missing disk space metrics and scores for the Risk and Efficiency badges.
Workaround:
Find and remove the file vijava2120100715.jar under $ALIVE_BASE/user/plugins/inbound/vmwarevi_adapter3/lib/ and restart the collector or vCenter Operations Manager services.

vCenter Operations Manager custom interface displays characters of high ASCII as question marks when connected to an Oracle database with the default character setting
For example, if dashboards or resource tags that have high ASCII characters in their names, those letters appear as question marks (?).
Workaround: Configure the Oracle database to use a Unicode character set such as UTF-8 to make characters display correctly.

Exception occurs when you perform a search on the Environment Overview page
The message "Error 'Could not execute query' in the UI, and Exception in the web.log" occurs when you perform a search on the Environment Overview page in the Custom user interface. This problem is caused by a known issue in Oracle 10g.Workaround: For pre-11gR2 databases, set cursor sharing to 'EXACT' (the default setting). For 11gR2 and later databases, no changes are required and the problem is resolved in 11gR2 Fixpack 2 (11.2.0.2).

Installing vCenter Operations Manager Standalone with MS SQL in console mode on Linux fails to test the database connection
Testing the database configuration will fail due to .RSA and .SF file inconsistencies when the configuration wizard is run from InstallAnywhere, but this failure doesn't impede the overall installation process.
Workaround: This failure can be ignored. The installation is successful afterwards.
If the user wants to test the database connection which failed during setup, the configuration wizard can be run from the bash shell using the "$HOME/Configure_VMware_vCenter_Operations -i console" command.

Cyclic redundancy check (CRC) errors manifest as missing data
CRC errors appear as missing data for a given resource.Workaround: Check the vcenter-ops/data/vcops/log/analytics.log file to see if CRC-related errors are logged, for example:

Documentation

The following product changes were not described in the release documentation.

All and group options for dashboard commands
For the dashboard import, dashboard delete, and dashboard reorder commands, you can use one of the following options instead of specifying a user name:
* --all
* --group:<group_name[,<group_name>]

The --all option applies the command to all user accounts. The --group:<group_names[,<group_name>] option applies the command to all user accounts that belong to the specified user groups.
For example, the command dashboard import group:Administrators,Operators "templates\MyDashboard.bin" imports the dashboard MyDashboard.bin to all user accounts that belong to the Administrators and Operators user groups.

The dashboard import command also has a --set <rank> option that enables you to set the dashboard order.
For example, the command dashboard import MyUser2 "dashboards/MyDashboard.bin" --set 1 imports the dashboard MyDashboard.bin and makes it the first dashboard in the dashboard list for the user MyUser2.

Missing information in the custom interface online help: "Data Age" field displays "Unknown" in the VCOps/VCM Compliance breakdown
vCenter Operations Manager will only display the last collection date (Data Age) if a collection filter is assigned to the VCM compliance rule group.