sfw-Hotfix_5_1_00058_400_2144064

 Basic information
Release type: Hot Fix
Release date: 2010-10-18
OS update support: None
Technote: TECH140245 - VMDg / MountV resources fail to online or probe when Microsoft MS10-066 “Vulnerability in remote procedure call could allow remote code execution” is applied
Documentation: None
Popularity: 4635 viewed    downloaded
Download size: 1.49 MB
Checksum: 4127305990

 Applies to one or more of the following products:
Storage Foundation 5.1 On Windows IA64
Storage Foundation 5.1 On Windows x64
Storage Foundation HA 5.1 On Windows IA64
Storage Foundation HA 5.1 On Windows x64

 Obsolete patches, incompatibilities, superseded patches, or other requirements:
None.

 Fixes the following incidents:
2144064

 Patch ID:
None.

Readme file
Date: 2010-10-04
OS: Windows
OS Version: Windows 2003
Packages:  vxassist.exe, vxsnap.exe, vxcmd.dll, vxcmd64.dll, vxbridge.exe
Etrack Incidents:  2144064
Errors/Problems Fixed: This hotfix addresses an issue where storage related operations in a clustered environment fail due to the Microsoft Hotfix 982802.
Fixes Applied for Products: SFW 5.1 and SFW HA 5.1
Install/Uninstall Instructions: This package contains the following 
self-extracting files. Each file is the hotfix for a specific processor 
architecture and operating system version. Choose the appropriate file 
for your computer's configuration.


Operating System		Platform	File Name
-------------------------------------------------------------------------------------------
Microsoft Windows Server 2003	IA64		Hotfix_5_1_00058_400_2144064_w2k3_ia64.exe	
Microsoft Windows Server 2003	x64		Hotfix_5_1_00058_400_2144064_w2k3_x64.exe


Extract the hotfix
==================

The hotfix can be extracted from a file in one of two ways:

* Method 1
  Double-click the hotfix. The hotfix will be extracted and the install 
  wizard will automatically start and guide you through the installation 
  after the extraction has completed.

* Method 2
  Save your selected file to a local folder and then extract the hotfix 
  with the /x option.  For example, enter the command in the c:\tmp 
  directory

  c:\tmp>Hotfix_5_1_00058_400_2144064_w2k8_x64.exe /x
  
Hotfix files will be extracted to "Hotfix_5_1_00058_400_2144064" folder at:

on 32-bit system: "%CommonProgramFiles%\Veritas Shared\WxRTPrivates"
on 64-bit system: "%CommonProgramFiles(x86)%\Veritas Shared\WxRTPrivates"

Install the hotfix
==================

Refer to README.RTF file in "Hotfix_5_1_00058_400_2144064" folder for details on installation 
options for the hotfix.

To install the hotfix on Widows 2003 servers, Microsoft Core XML Services 
(MSXML) 6.0 need to be installed first. Please download and install 
MSXML 6.0 before installing the hotfix.  Refer to the following link 
for more information:

http://www.microsoft.com/downloads/details.aspx?FamilyId=993c0bcf-3bcf-
4009-be21-27e85e1857b1&displaylang=en

Microsoft posted service pack and/or security updates for Core XML 
Services 6.0.  Please contact Microsoft or refer to Microsoft web-site to 
download and install latest updates to Core XML Services 6.0.

Additional Notes: 

Contents

1. Overview
2. Resolution
3. Before you begin
4. Installing the hotfix
     - GUI Install
     - Command Line Install
     - Additional Notes
5. Disclaimer

1. Overview

After installing the Microsoft security update 982802 on clustered systems where SFW is used to manage storage, some of the storage related operations may fail.

- In a Veritas Cluster Server (VCS) environment, the cluster disk group resources (MountV, VMDg) do not come online on the nodes.
The Windows Event Viewer may contain the following events:
Event ID: 9515
Event Source: Agent Framework
Description: VMDg:nodename-VMDg:online:Init diskgroup : Unrecognized error code. 800706C6

Event ID: 31201
Event Source: RPC
Description:
Application "%vcs_home%\bin\VCSAgDriver.exe"
type VMDg with process id 2980 has failed to complete a COM/RPC call  because of an invalid message from server.

Here, %vcs_home% is typically C:\Program Files\Veritas\Cluster Server.

- In an Microsoft Cluster Server (MSCS) environment, the Volume Manager Disk Group resource creation may fail. Also, if the controlling node of the cluster becomes inactive, the quorum arbitration process may fail.

This issue occurs due to a failure in some of the cluster calls to VxBridge.exe on 64-bit Windows Server 2003 systems.


2. Resolution
This issue is fixed in the SFW components. An additional memory buffer is allocated for the output parameters. This ensures that the arguments passed from VxBridge.exe reach the clients.

3. Before you begin

This hotfix requires Microsoft Core XML Services (MSXML) 6.0 pre-installed 
in your setup. Download and install MSXML 6.0 before installing the hotfix.  
Refer to the following link for more information:

http://www.microsoft.com/downloads/details.aspx?FamilyId=993c0bcf-3bcf-4009-be21-27e85e1857b1&displaylang=en

Microsoft posted service pack and/or security updates for Core XML Services 
6.0.  Please contact Microsoft or refer to Microsoft web-site to download 
and install latest updates to Core XML Services 6.0.

4. Installing the hotfix


The hotfix installation requires stopping the Storage Agent (vxvm) 
service which will cause the 'Volume Manager Disk Group' (VMDg) resources 
in a cluster environment (MSCS or VCS) to fault. If this hotfix is 
being applied to a server in cluster, make sure any cluster groups 
containing a VMDg resource are taken offline or moved to another node in 
the cluster before proceeding.

Extract the hotfix to a temporary location on the server. The hotfix 
archive contains a hotfix installer for the following Windows Server versions 
and architectures:

Operating System		Platform	File Name
-------------------------------------------------------------------------------------------
Microsoft Windows Server 2003	IA64		Hotfix_5_1_00058_400_2144064_w2k3_ia64.exe	
Microsoft Windows Server 2003	x64		Hotfix_5_1_00058_400_2144064_w2k3_x64.exe

This hotfix includes the following updated file(s):

================================================================================
Filename     | Version 	   |  Windows 2003  |
================================================================================
vxcmd.dll    | 5.1.00058.400   |  x64, ia64 |
---------------------------------------------
vxbridge.exe | 5.1.00058.400   |  x64, ia64 |
---------------------------------------------
vxcmd64.dll  | 5.1.00058.400   |  x64, ia64 |
---------------------------------------------
vxassist.exe | 5.1.00058.400   |  x64, ia64 |
---------------------------------------------
Vxsnap.exe   | 5.1.00058.400   |  x64, ia64 |
---------------------------------------------

The hotfix can be installed using the GUI or CLI. Instructions for both 
options are provided below:


To install the hotfix using the GUI
------------------------------------
1. Double click the hotfix executable file to extract the contents to a 
default location on the cluster node.

- On 32-bit systems, the files are extracted to: 
"%commonprogramfiles%\Veritas Shared\WxRTPrivates"

- On 64-bit systems, the files are extracted to: 
"%commonprogramfiles(x86)%\Veritas Shared\WxRTPrivates"

* The Hotfix Installer Wizard is automatically launched after the files have 
been extracted.

2. Click "Next" on the Welcome screen. 

3. The 'Hotfix Installation Task' screen lists the tasks that are performed 
by the installer.

4. Select the "Install Hotfix" button to install the hotfix. 

5. While the hotfix installation updates the system, the status of each 
task is updated as it completes.

6. After all tasks have completed, select 'Next', then 'Finish' to complete the 
installation process.

7. If prompted to restart the server, do so.

8. If this is a clustered configuration (SFW-HA or MSCS), please perform steps 1-7 
on all additional nodes in the cluster.


To install the hotfix using the Command Line
---------------------------------------------
1. At the command prompt, run one of the following commands to extract the hotfix 
files to the default location:

C:\temp><Hotfix_BuildVersion_IncidentNumber_OS_Platform>.exe /x
C:\temp><Hotfix_BuildVersion_IncidentNumber_OS_Platform>.exe /extract

Example:
For Windows Server 2003 32-bit: C:\temp>Hotfix_5_1_xxxxx_xxx_xxxxxxx_w2k3_x86.exe /x  

2. From the command prompt, navigate to the default location where the hotfix 
files are extracted.

On 32-bit systems, the files are extracted to: 
"%commonprogramfiles%\Veritas Shared\WxRTPrivates\<Hotfix_BuildVersion_IncidentNumber_OS_Platform>"

On 64-bit systems, the files are extracted to: 
"%commonprogramfiles(x86)%\Veritas Shared\WxRTPrivates\<Hotfix_BuildVersion_IncidentNumber_OS_Platform>"

3. At the command prompt, run the following command to install the hotfix: 
VxHF.exe /install:<Hotfix_BuildVersion_IncidentNumber_OS_Platform> /silent

Note: <Hotfix_BuildVersion_IncidentNumber_OS_Platform> is the name of the hotfix file excluding the OS, platform, 
and .exe extension. This is also the name of the folder where the hotfix was 
extracted to under the \WXRTPRIVATES directory.

Example: 
Hotfix Executable Name: Hotfix_5_1_xxxxx_xxx_xxxxxxx_w2k3_x86.exe
When installing the hotfix, the <Hotfix_BuildVersion_IncidentNumber_OS_Platform> name is 
Hotfix_5_1_xxxxx_xxx_xxxxxxx (note how the '_w2k3_x86.exe' was excluded).

Command:
VxHF.exe /install:Hotfix_5_1_xxxxx_xxx_xxxxxxx /silent

4. Follow the instructions displayed in the command prompt to complete the hotfix 
installation.

5. If prompted to restart the server, do so at this time.

6. If this is a clustered configuration (SFW-HA or MSCS), please perform steps 1-5 
on all additional nodes in the cluster.

Additional Notes
----------------
- VxHF.exe logs are located at the following location: 
"%allusersprofile%\Application Data\Veritas\VxHF"

- For general information about the VXHF installer, please refer to the following 
technote: http://seer.entsupport.symantec.com/docs/329713.htm

- To view a list of hotfixes already installed on a system, please refer to the 
following technote: http://seer.entsupport.symantec.com/docs/329704.htm

- For information on uninstalling a hotfix, please refer to the following 
technote: http://seer.entsupport.symantec.com/docs/329709.htm


5. DISCLAIMER:
----------------+
This fix has not been fully tested. It is recommended that the fix be evaluated in a 
test environment before implementing it in your production environment. When the fix 
is incorporated into a Storage Foundation for Windows maintenance release, the resulting 
Hotfix or Service Pack must be installed as soon as possible. Symantec Technical Services 
will notify you when the maintenance release (Hotfix or Service Pack) is available.