Users Guide

Versions Affected: 2.2 and later
What should I do when a web communication error in the
vCenter web client appears after changing the DNS
settings in OMIVV
If you see any kind of web communication error in the vCenter web client while doing any OMIVV-related tasks after changing the DNS
settings, do either of the following:
• Clear the browser cache.
• Log out and then log in from web client.
The settings page fail to load, if I navigate away and again
go back to the settings page
For vSphere v5.5, in web client, if you navigate away and go back to the Settings page, the page might fail to load and the spinner
continues to spin. The failure to load is a refresh issue and the page is not refreshing correctly.
Resolution: Click the global refresh and the screen refreshes correctly.
Versions Affected: 2.2 and 3.0
Task cannot be scheduled for the time in the past- error in
inventory schedule and warranty schedule page of Initial
Configuration Wizard appear
In web client, the error “Task cannot be scheduled for the time in the past” appears:
• if you select ‘All registered vCenters’ in the Initial Configuration wizard, and there are some vCenters with no hosts.
• when vCenters where some have inventory or warranty tasks already scheduled.
• when some vCenters with no inventory or warranty schedule set yet.
Resolution: Run the setting of inventory and warranty schedule separately again from the Settings page for the vCenters.
Versions Affected: 2.2 and later
Installation date appears as 12-31-1969 for some of the
firmware on the firmware page
In web client, the installation date appears as 12/31/1969 for some firmware items on the firmware page for a host. If the firmware
installation date is not available, the old date is displayed.
Resolution: If you see this old date for any firmware component, consider that the installation date is not available for it.
Versions Affected: 2.2 and later
Successive global refresh cause exception to be thrown in
the recent task window.
If you try to press the refresh button repeatedly, the VMware UI might throw an exception.
Resolution: You can dismiss this error and can continue.
Version Affected: 2.2 and later
142
Frequently Asked Questions-FAQ