This page lists publically-released patches for Veritas Enterprise Products.
For Product GA build, see Veritas Entitlement Management System(VEMS) by clicking the Veritas Support 'Licensing' option.
For information on private patches, contact Veritas Technical Support.
Veritas is making it easier to find all software installers and updates for Veritas products with a completely redesigned experience. NetBackup HotFixes and NetBackup Appliance patches are now also available at the new Veritas Download Center.
Patches for your product can have a variety of names. These names are based on product, component, or package names. For more information on patch naming conventions and the relationship between products, components, and packages, see the SORT online help.
sfw-Hotfix_5_1_01007_407_2164301
Sign in if you want to rate this patch.

 Basic information
Release type: Hot Fix
Release date: 2010-10-20
OS update support: None
Technote: TECH140245 - VMDg / MountV resources fail to online or probe when the "Microsoft MS10-066: Vulnerability in remote procedure call could allow remote code execution" security fix is applied
Documentation: None
Popularity: 813 viewed    95 downloaded
Download size: 1.48 MB
Checksum: 2678573554

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

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

This patch requires: Release date
sfw-win64-5.1AP1 2008-12-20
sfw-win32-5.1AP1 2008-12-20

 Fixes the following incidents:
2164301

 Patch ID:
None.

 Readme file  [Save As...]
Date: 2010-10-07
OS: Windows
OS Version: Windows 2003
Packages: vxcmd.dll, vxbridge.exe, vxcmd64.dll, vxassist.exe, vxsnap.exe
Etrack Incidents: 2164301

Errors/Problems Fixed
----------------------+ 
This hotfix addresses an issue where storage related operations in a clustered environment fail due to the Microsoft Hotfix 982802.

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 (VMDg) 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.

Resolution
-----------
This issue is fixed for 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.

Fixes Applied for Products
--------------------------+
Storage Foundation 5.1 AP1 for Windows 
Storage Foundation and High Availability Solutions 5.1 AP1 for Windows

Install/Uninstall Instructions
------------------------------+
This package contains self-extracting files that are specific to the processor architecture and operating system version.

==========================================================================
Operating System      Platform  File Name
==========================================================================
Windows Server 2003   IA64      Hotfix_5_1_01007_407_2164301_w2k3_ia64.exe	
                      x64       Hotfix_5_1_01007_407_2164301_w2k3_x64.exe
--------------------------------------------------------------------------

Download the appropriate hotfix executable to a temporary location on your system.
You can install this hotfix using the GUI or from the command line.
Instructions for both options are provided below.

Each self-extracting file includes the following updated file(s):

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

Before you begin
-----------------
- For Windows Server 2003, 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 website to download and install latest updates to Core XML Services 6.0.
Refer to the following link for more information:
http://www.microsoft.com/downloads/details.aspx?FamilyId=70C92E77-9E5A-41B1-A9D2-64443913C976&displaylang=en

- 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 a cluster, make sure any cluster groups 
containing VMDg resources are taken offline or moved to another node in 
the cluster before proceeding.

- Sometimes the hotfix may fail to install due to some stray rhs.exe processes that keep running even after the cluster service has been stopped. In such a case, you should manually terminate all the running rhs.exe processes, confirm that the clussvc service is stopped, and then retry installing the hotfix.


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 are extracted.

2. Click "Next" on the Welcome screen. 
The 'Hotfix Installation Task' screen lists the tasks that are performed by the installer.

3. Click "Install Hotfix" to begin the hotfix installation. 
The status of each installation task is updated as it completes.

4. After the tasks are complete, click "Next" and then click "Finish" to complete the installation process.

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

6. If this is a clustered configuration (VCS or MSCS), please perform steps 1-5 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
or
C:\temp><Hotfix_BuildVersion_IncidentNumber_OS_Platform>.exe /extract

For example, to extract this hotfix on a 32-bit Windows 2003 system, the command is:
C:\temp>Hotfix_5_1_01007_407_2164301_w2k3_x64.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

Here, <Hotfix_BuildVersion_IncidentNumber_OS_Platform> is the name of the hotfix file excluding the OS, platform, and .exe extension.

For example, the command to install this hotfix is:
VxHF.exe /install:Hotfix_5_1_01007_407_2164301 /silent

Hotfix Executable Name is Hotfix_5_1_01007_407_2164301_w2k3_x64.exe.
When installing the hotfix, the <Hotfix_BuildVersion_IncidentNumber_OS_Platform> name is Hotfix_5_1_01007_407_2164301.
(note that the "_w2k3_x86.exe" is excluded).

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 (VCS or MSCS), please perform steps 1-5 on all additional nodes in the cluster.


Additional Notes
----------------+
- To confirm the installation of the hotfix, run the following command:
vxhf.exe /list

The output of this command lists the hotfixes installed on a system.

- For details about a particular hotfix, run the following command:
vxhf.exe /display:<HotfixName>

Here, <HotfixName> is the name of the hotfix file without the platform and the .exe extension.

- The hotfix installer (vxhf.exe) creates and stores logs at:
"%allusersprofile%\Application Data\Veritas\VxHF"

- For general information about the hotfix installer (vxhf.exe), please refer to the following technote:
http://www.symantec.com/business/support/index?page=content&id=TECH73446

- To view a list of hotfixes already installed on a system, please refer to the steps mentioned in the following technote: 
http://www.symantec.com/business/support/index?page=content&id=TECH73438

- For information on uninstalling a hotfix, please refer to the steps mentioned in the following technote: 
http://www.symantec.com/business/support/index?page=content&id=TECH73443


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.



Read and accept Terms of Service