Date: 2010-10-22
OS: Windows
OS Version: 2003
Packages: Hotfix_5_1_10029_2165655_x86.exe, Hotfix_5_1_10029_2165655_x64.exe, Hotfix_5_1_10029_2165655_ia64.exe
Etrack Incidents: 2165655, 2169385

Errors/Problems Fixed:
----------------------+
This hotfix includes fixes for the VCS Mount agent.

Overview
---------
The following issues may occur where a service group containing the VCS Mount agent resource is configured in the cluster:

=======
Issue 1
=======
Intermittent Delayed Write Failed errors are observed on nodes where the service group is not online.
After switching the service group from an active node to another node, these errors are again seen on the active node where the service group is now offline.

The VCS Mount agent log may display the following:
VCS ERROR V-16-10051-8029 Mount:<MountResourceName>:offline:Unable to lock the volume. Disk No. = <Disk#>, PartitionNo = <Partition#>. Error : 5

The Windows Event Viewer may contain the following events:
Event ID 57: Source: ftdisk
Warning: The system failed to flush data to the transaction log. Corruption may occur.

Event ID 50: Source: ntfs
Warning: {Delayed Write Failed}Windows was unable to save all the data for the file <filename>. The data has been lost. This error may be caused by a failure of your computer hardware or network connection. Please try to save this file elsewhere.

There may also be an application pop-up message displaying the following message:
Event ID 26: Source: Application Pop-up
Information: Windows - Delayed Write Failed : Windows was unable to save all the data for the file \\ServerName\VolumeMountPointName\FileName. This data has been lost. This error may be cause by a failure on your computer hardware or network connection. Please try to save this file elsewhere.

=======
Issue 2
=======
Mount agent crashes while switching or taking the service group offline.
There may also be a pop-up message that displays the following error related to VCSAgDrive.exe:
The instruction at "0x78147347" referenced memory at "0x00000000". The memory could not be "written".

The Windows Event Viewer may contain the following events:
Event ID 1000: Source: Application Error
Error: Faulting application VCSAgDriver.exe, version 5.1.10000.320, faulting module msvcr80.dll, version 8.0.50727.762, fault address 0x00017347.

Event ID 8029: Source: AgentFramework
Error: Mount:<MountResourceName>:offline:Unable to lock the volume. Disk No. = <Disk#>, PartitionNo = <Partition#>. Error : 5

Resolution
-----------
These issues have been fixed in the VCS Mount agent.

After installing this hotfix, the Mount agent ignores the MountResName attribute.
The MountResName attribute was applicable for folder mounts.

If you have configured folder mounts in a service group, then after installing this hotfix, the Mount resources may go in to an unknown state.

To resolve this, specify the complete mount path value in the MountPath attribute itself.
For example, if MountPath value is \Dir and MountResName value is the name of the resource monitoring X:, then change the MountPath attribute value to X:\Dir.
The MountPath attribute value must be the complete mount path.
You can change the attribute value either before or after installing the hotfix.


Fixes Applied for Products
---------------------------+
Veritas Cluster Server 5.1 SP1 for Windows


Install/Uninstall Instructions
-------------------------------+
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.

This hotfix includes the following updated file:
----------------------------------
File name   | New Version number
----------------------------------
Mount.dll   |    5.1.10029.393
----------------------------------

Before you begin
-----------------
In case of Windows Server 2003 systems, 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.
Refer to the following link for more information:
http://www.microsoft.com/downloads/details.aspx?FamilyId=70C92E77-9E5A-41B1-A9D2-64443913C976&displaylang=en

To install the hotfix using the GUI
------------------------------------
1. The Mount agent ignores the MountResName attribute after installing the hotfix.
If you have configured folder mounts in a service group, then specify the complete mount path value in the MountPath attribute.
For example, if MountPath value is \Dir and MountResName value is the name of the resource monitoring X:, then change the MountPath attribute value to X:\Dir.

2. 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 all the files are extracted.

3. Click "Next" on the Welcome screen.
The Hotfix Installation Tasks panel lists the tasks that are performed by the installer.

4. Click "Install Hotfix" to install the hotfix.
The status of each task is updated as it gets completed.

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

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

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


To install the hotfix using the command line
---------------------------------------------
1. The Mount agent ignores the MountResName attribute after installing the hotfix.
If you have configured folder mounts in a service group, then specify the complete mount path value in the MountPath attribute.
For example, if MountPath value is \Dir and MountResName value is the name of the resource monitoring X:, then change the MountPath attribute value to X:\Dir.

2. At the command prompt run one of the following commands to extract the hotfix files to the default location:
C:\temp><HotfixName.exe> /x
or
C:\temp><HotfixName.exe> /extract

For example, to extract this hotfix on a 64-bit cluster node, the command is:
C:\temp>Hotfix_5_1_10029_2165655_x64.exe /x

3. 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"

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

4. At the command prompt, run the following command to install the hotfix:
vxhf.exe /install:<HotfixName> /silent

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

For example, to install this hotfix on a 64-bit cluster node, the command is:
vxhf.exe /install:Hotfix_5_1_10029_2165655 /silent

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

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

7. If this is a clustered configuration (SFW-HA 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 and HA 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.