How to identify and recover if Storage Foundation for Windows 5.0 (SFW) Rollup Patch 1 (RP1) did not install properly on a 32 bit operating system (OS)

Article:TECH58361  |  Created: 2008-01-11  |  Updated: 2010-01-22  |  Article URL http://www.symantec.com/docs/TECH58361
Article Type
Technical Solution


Environment

Issue



How to identify and recover if Storage Foundation for Windows 5.0 (SFW) Rollup Patch 1 (RP1) did not install properly on a 32 bit operating system (OS)

Solution



There is a potential issue after a reported successful installation of SFW RP1, where Veritas Enterprise Administrator (VEA) will not start. When launching the Veritas Enterprise Administrator console on an affected system, there will be an error indicating a missing ExtensEnu.dll. The source of the issue has been identified and resolution is part of the updated RP1A package.

The specific condition under which the issue occurs with the original RP1:
  • On a system(s) that is running the 32bit version of the Windows operating system
  • HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node exists on the 32bit system because it has been written by an application that depends upon it.
Note: If you have the original 5.0 RP1 package, do not install it on your SFW or SFWHA systems. Please utilize the updated 5.0 RP1A package for any new upgrades. If you have 5.0 system(s) installed with the original RP1 package that do not suffer from this issue, you do NOT need to uninstall the original RP1 and install the new RP1A. If you have installed the original 5.0 RP1 package, you can proceed with the following information to confirm whether your system(s) are affected and perform the necessary steps for recovery on affected system(s).

How to Identify if the Issue Exists:
1.  Open up the registry on your 32bit system(s) and check for the existence of the following key:
\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node
If this key is not present on your 32bit system(s), then the known issue could not have occurred during the installation of the original RP1A. If it does exist, proceed with Step 2 for further verification.
2.  Open up the registry on your 32bit system(s) and check for the existence of the following keys:
\HKEY_LOCAL_MACHINE\SOFTWARE\Veritas\VxSvc\CurrentVersion\VolumeManager\ASR
\HKEY_LOCAL_MACHINE\SOFTWARE\Veritas\VxSvc\CurrentVersion\VolumeManager\Capacity
\HKEY_LOCAL_MACHINE\SOFTWARE\Veritas\VxSvc\CurrentVersion\VolumeManager\Languages
\HKEY_LOCAL_MACHINE\SOFTWARE\Veritas\VxSvc\CurrentVersion\VolumeManager\PartitionTypes
\HKEY_LOCAL_MACHINE\SOFTWARE\Veritas\VxSvc\CurrentVersion\VolumeManager\TaskIODelays
\HKEY_LOCAL_MACHINE\SOFTWARE\Veritas\VxSvc\CurrentVersion\VolumeManager\TaskThreads
If the keys are missing, the system(s) have the issue identified in the original 5.0 RP1. Please proceed to the next sections on recovering the system(s) from the issue.
Warning: Incorrect use of the Windows registry editor may prevent the operating system from functioning properly. Great care should be taken when making changes to a Windows registry. Registry modifications should only be carried-out by persons experienced in the use of the registry editor application. It is recommended that a complete backup of the registry and workstation be made prior to making any registry changes.

Resolution for system(s) running Storage Foundation 5.0 for Windows with RP1:
Note: DO NOT UNINSTALL RP1 first, as this will cause the server to go into an endless reboot. If this has already occurred, then follow TechNote 301195 found in the Related Documents section below.
The following steps are only for system(s) running Storage Foundation 5.0 for Windows with RP1 that have experienced the issue as confirmed in the steps above. These SFW system(s) can be running any combination of SFW options (DMP, FlashSnap, MSCS and VxCache). These steps are not for systems running VCS. Please refer to the next section for resolution instructions for SFWHA system(s).
Note: If the server has multiple paths managed by Storage Foundation for Windows DMP, please bring the server down to a single path before proceeding.
  • Open Add/Remove Programs from the Control Panel.
  • Select Storage Foundation for Windows 5.0 Server Components and select uninstall.
  • SFW 5.0 has to be completely uninstalled to resolve this issue. Selecting the SFW 5.0 Server components will also uninstall RP1.
  • Reboot the system after the uninstall completes.
  • Install SFW 5.0.
  • Reboot the system after the installation completes.
  • Install RP1A. The link to download RP1A is in the Related Documents section below.
  • Reboot the system after the installation completes.

Resolution for system(s) running Storage Foundation High Availability for Windows 5.0:
Note: DO NOT UNINSTALL RP1 first, as this will cause the server to go into an endless reboot. If this has already occurred, then follow TechNote 301195 found in the Related Documents section below.
Please open a support case for instruction and assistance in resolution for SFWHA system(s). Due to configuration variation and complexities, it is important to obtain the proper steps and guidance directly from Symantec Support.

Symantec strongly recommends the following best practices:
1. Always perform a Full backup prior to and after any changes to your environment.
2. Always make sure that your environment is running the latest version and patch level.

How to Subscribe to Software Alerts:
If you have not received this TechNote from the Symantec Email Notification Service as a Software Alerts, please subscribe at the following link:
http://maillist.entsupport.symantec.com/subscribe.asp








Legacy ID



301053


Article URL http://www.symantec.com/docs/TECH58361


Terms of use for this information are found in Legal Notices