Date: 2010-02-17
OS: Windows
OS Version: 2003, 2008
Packages: Hotfix_5_1_10005_1960076_x86.exe, Hotfix_5_1_10005_1960076_x64.exe, Hotfix_5_1_10005_1960076_ia64.exe
Etrack Incidents: 1960076
Errors/Problems Fixed:
This hotfix includes a fix for the following VCS agents:
- Process agent
- GenericService agent
- ServiceMonitor agent
Overview
--------+
Process agent resources fault while trying to start the configured processes with the configured user credentials.
The Process agent log displays the following messages:
VCS ERROR V-16-2-13120 Thread(1748) Error receiving from the engine. Agent(Process) is exiting.
VCS ERROR V-16-10051-6531 Process:GenProc:online:Failed to get the password.
VCS ERROR V-16-2-13066 Thread(2572) Agent is calling clean for resource(GenProc) because the resource is not up even after online completed.
VCS ERROR V-16-2-13068 Thread(2572) Resource(GenProc) - clean completed successfully.
VCS ERROR V-16-2-13071 Thread(2572) Resource(GenProc): reached OnlineRetryLimit(0).
This issue is observed only on SFW HA 5.1 SP1.
Resolution
----------+
This issue has been fixed in the VCS agents.
(e1960076)
Fixes Applied for Products:
Veritas Storage Foundation and High Availability Solutions 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 files:
----------------------------------------
File name 	   | New Version number
----------------------------------------
Process.dll        |    5.1.10005.337
----------------------------------------
GenericService.dll |    5.1.10005.337
----------------------------------------
ServiceMonitor.dll |    5.1.10005.337
----------------------------------------
Before you begin
----------------+
This is applicable only 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 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. 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 SharedWxRTPrivates"
On 64-bit systems, the files are extracted to:
"%commonprogramfiles(x86)%Veritas SharedWxRTPrivates"
The Hotfix Installer Wizard is automatically launched after all the files are extracted.
2. Click "Next" on the Welcome screen.
The Hotfix Installation Tasks panel lists the tasks that are performed by the installer.
3. Click "Install Hotfix" to install the hotfix.
The status of each task is updated as it gets completed.
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.
6. 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. At the command prompt run one of the following commands to extract the hotfix files to the default location:
C:	emp><HotfixName_Platform.exe> /x
or
C:	emp><HotfixName_Platform.exe> /extract
For example, to extract this hotfix on a 64-bit cluster node, the command is:
C:	emp>Hotfix_5_1_10005_1960076_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 SharedWxRTPrivates"
On 64-bit systems, the files are extracted to:
"%commonprogramfiles(x86)%Veritas SharedWxRTPrivates"
3. 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_10005_1960076 /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
----------------+
- 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 DataVeritasVxHF"
- For general information about the hotfix installer (vxhf.exe), 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 steps mentioned in the following technote: 
http://seer.entsupport.symantec.com/docs/329704.htm
- For information on uninstalling a hotfix, please refer to the steps mentioned in the following technote: 
http://seer.entsupport.symantec.com/docs/329709.htm
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.