Installation guide
Table Of Contents
- COPYRIGHT
- TABLE OF CONTENTS
- INTRODUCTION
- Support OS - VM ESX
- PRE-REQUISITES
- ADDITIONAL INFORMATION
- WHAT’S NEW IN VOYENCECONTROL 4.1.0
- FIXED ISSUES
- (20112) – Cut-Through not offering a "more" Option when Viewing Configuration
- (21536) – User passwords – Visible in commmrg.log when using Cut-through
- (21555) – Device Data Fields- Cleared Despite no User Input
- (21618) – Network Navigation Tree – Problem with Display
- (21661) – Network Navigation Tree – Right-Click Options not Working Properly
- (21690) – Network Navigation Window – Right-Click Options – Working Intermittently
- (21759) – Pulled Cisco IOS Devices – Self-Check rule Failed
- (21834) – Database Size - More Space than Required
- (21878) – Failed Policies – Not Displaying in the Comments Section
- (21994) – Customize Column Sizing not being Maintained
- (22062) – Clicking "Schedule" after running Compliance Audit – Devices Missing
- (22147) – Repeated Error Message - Server and jboss logs
- (22157) – Audit Trail – Incorrect Hierarchy
- (22319) – Graphical User Interface - Slow Response/Jboss stuck at 100% CPU
- (22407) – Cannot Schedule OS Update for Multiple Devices
- (22521) – Large Auto Discovery Jobs do not Complete
- (22534) – Random "Resource Not Found" Error at Login
- (23074) – Compliance Error When Attempting to Execute Compliance Audit on Nokia Appliance
- KNOWN ISSUES
- (22192) – Data Field Names – New Data Field Names are not Replacing the Old Data Field names after Migration
- (22386) – Disabling SNMP causes Failing Request
- (22556) – Schedule Configuration Change - conflict with Velocity Template Commands
- (22579) – Upgrading from VoyenceControl 4.0.1 to 4.1.0 causes Exception on UI Load
- (22595) – Intermittent deadlock - Importing/Exporting Automation Library items.
- (22607) – Compliance Steps – Existing RegEx Compliance Test
- (22883) – SAML Enable Script - Source /etc/voyence.conf before Installation
- (22906) – Connection to SSH Proxy Fails
- (22943) – "Error: Version Already Installed" Message after a Failed install or Upgrade
- (23027) – Upgrading a Device Server from VoyenceControl 3.6.2 to 4.1.0 does not Retain Multi-Level Mode
- (23089) – Upgrading to VoyenceControl 4.1.0 - Report Advisor URL Points to "http:///web"
- (23118) – System Management Console - Password gets reset to 'sysadmin' after Upgrading (Windows Only)
- (23150) – Config Pulls After Auto Discovery - Not Getting Scheduled when Using a Remote Device Server
- (23542) – Installing from a Read Only File System – Components Needed
- (23548) – Can Not Install Integration Modules under the VoyenceControl 4.1 API in VoyenceControl version 4.1.0
- INSTALLING VOYENCECONTROL 4.1.0
- UPGRADING TO VOYENCECONTROL 4.1.0
- WHERE TO GET HELP
EMC VoyenceControl – Release Notes
(22943) – "Error: Version Already Installed" Message after a Failed install
or Upgrade
The "Version Already Installed" message indicated that enough of the product was
installed to make it appear that the new version is present. This could happen when
the installation is aborted or stopped in the middle of execution.
The steps below are provided as a work-around for this scenario if you receive this
error message when re-installing after a failed install or upgrade. Possible failure
scenarios include lack of sufficient disk space and/or loss of terminal session during
install/upgrade.
Install Workaround
If you receive the "Version Already Installed" error when attempting to re-install after a failed
install, the simplest approach is to uninstall, and then re-install. Run the uninstaller per the
instructions in the VoyenceControl Installation Guide. If the uninstall fails to run, complete the
following steps:
1. Stop all VoyenceControl services using:
/etc/init.d/vcmaster stop (Linux/Solaris)
“[Product Directory]\bin\ncmmaster.pl” stop (Windows)
2. Remove the VoyenceControl installation directory (Note: this deletes all VoyenceControl
data).
3. Remove the /etc/voyence.conf file (Linux and Solaris only).
4. Ensure that the failure condition is fixed (enough disk space, run session through screen
or VNC).
5. Run the install again.
Upgrade Workaround
If you receive the "Version Already Installed" error when attempting to re-install after a failed
upgrade, you can modify the current version number to allow the upgrade to continue. The
following steps should only be used if data migration has completed successfully, the upgrade
failed, AND you are receiving the "Version Already Installed" message when re-running the
upgrade.
1.
Change the current VoyenceControl build number. The build number is the last number
in the version. Change it to one less than its initial value. For example, if the line reads
4.1.0.850, change it to 4.1.0.849.
Linux/Solaris:
Edit the /etc/voyence.conf file and modify the VERSION line at the top.
Windows:
Edit the registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Voyence\Control\Configuration\VERSION
2. Ensure that the failure condition is fixed (enough disk space, run session through screen
or VNC).
3. Run the install again.
Release Notes Version 4.1.0
Page 15