ProblemUpgrade from VERITAS CommandCentral (tm) 4.x to 4.2 for Windows fails when a non-default path is used for installation
*** This Technote has been updated in Feb/2006. A permanent fix is now available. See below. ***
When attempting to upgrade VERITAS CommandCentral 4.x to 4.2, if the installation directory is a non-default one, i.e. a directory other than C:\Program Files\VERITAS, the upgrade will fail. This occurs because the setup dialog "VERITAS CommandCentral Offerings" only allows the selection of the Program Destination Folder. The Management Server Destination Folder, which uses the default C:\Program Files\VERITAS, is grayed out. If proceeding, the upgrade of the CommandCentral database will fail, and the CommandCentral data will be inaccessible.
This condition occurs only in the following configuration:
CommandCentral 4.0 or 4.1 Storage Management Server, Web Engine, and/or CommandCentral 4.0 or 4.1 Service Management Server were installed to a non-default location, i.e. a directory other than C:\Program Files\VERITAS.
This condition does not occur if CommandCentral was originally installed in the default directory C:\Program Files\VERITAS. To verify the CommandCentral installation directory, follow these steps:
1. Open the "System" control panel
2. On the Advanced tab, click the Environment Variables button
3. Double-click "Path" from the System Variables
4. Review the current CommandCentral entry in the Path to see if it is the default (C:\Program Files\VERITAS). If it is not, then this technote applies.
5. Click "Cancel" to exit the "System" Control Panel
To avoid this issue, the following workaround should be used prior to upgrading VERITAS CommandCentral 4.x to 4.2 for Windows when a non-default installation path was used to install the earlier version.
To upgrade to CommandCentral 4.2 for Windows which was originally installed in a non-default directory, follow these steps to upgrade the management server and to upgrade CommandCentral databases (file vxcc.db and vxdmbulk.db) that were originally saved
Note: This workaround requires editing the Windows registry. Make a backup copy of the registry before you proceed. For instructions on backing up the Windows registry, see http://support.microsoft.com/default.aspx?scid=kb;en-us;322755
Before running the 4.2 upgrade, add the following registry string value "VxccDbUserSelectedPath" to the registry key:
The value of "VxccDbUserSelectedPath" should be similar to the value of DbPath but without the tailing "\CommandCentral\CC Data".
DbPath = "D:\Program Files\VERITAS\CommandCentral\CC Data"
VxccDbUserSelectedPath = "D:\Program Files\VERITAS"
After completing the above steps, the upgrade will automatically add "\CommandCentral\CC Data\db" to the path entered in the new, manually entered key and place it in the Management Server Data Destination Folder path for the database files.
However, during the upgrade, the administrator will still have to manually select the alternate path for the Program Destination Folder.
Note: If an administrator has already upgraded CommandCentral 4.x to 4.2 for Windows without the benefit of using this workaround, Symantec Enterprise Technical Support has developed additional procedures that will allow the administrator to restore the original data and correctly set the database path without having to completely reinstall the product. Call Symantec Enterprise Technical Support for assistance with the additional steps necessary to complete the upgrade successfully.
*** UPDATE ***
Permanent Fix: This issue is resolved in CommandCentral 4.2 Feature Pack 1. Contact Symantec Enterprise Technical Support to obtain the upgrade
If there are any questions about this issue, please contact Symantec Enterprise Technical Support
If receipt of this TechNote was not via email as a Software Alert, please ensure to subscribe to the CommandCentral products for Email Notification Service of Software Alerts by visiting the following link: http://maillist.support.veritas.com/subscribe.asp