This page lists publically-released patches for Veritas Enterprise Products.
For information on private patches, contact Veritas Technical Support.
For NetBackup Enterprise Server and NetBackup Server patches, see the NetBackup Downloads.
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.
The latest patch(es) : vcs-win_x64-CP7_VCSW_601
|Sign in if you want to rate this patch.|
|OS update support:||None|
|Technote:||TECH209086 - Storage Foundation for Windows High Availability, Storage Foundation for Windows and Veritas Cluster Server 6.0.1 Cumulative Patches|
|Popularity:||524 viewed 18 downloaded|
|Download size:||5.84 MB|
Applies to one or more of the following products:
Cluster Server 6.0.1 On Windows x64
Obsolete patches, incompatibilities, superseded patches, or other requirements:
Fixes the following incidents:
2938704, 3054751, 3065921, 3099727, 3113887, 3164649, 3186666, 3247363, 3248926
Readme file [Save As...]
This readme has the following sections: =====================| * Date * OS/Version * Packages * Etrack Incidents * Fixes Applied for Products * What's new in this CP * Install instructions * - Before you begin * - To install in the verbose mode * - To install in the non-verbose (silent) mode * Post-install steps * Known issues * Errors/Problems fixed * Additional notes * Disclaimer =====================| Date: 2013-07-29 OS: Windows OS Version: 2008, 2008 R2 Packages: ================================================ Architecture/OS Windows Server 2008 / 2008 R2 ================================================ x64 CP1_VCSW_601_W2k8_x64.exe ------------------------------------------------ Etrack Incidents: 3065921, 2938704, 3099727, 3054751, 3164649, 3186666, 3113887, 3247363, 3248926 Fixes Applied for Products ==========================| Veritas Cluster Server (VCSW) 6.0.1 for Windows What's new in this CP =====================| The following hotfix has been added in this CP: - HotFix_6_0_10002_3065921 - HotFix_6_0_10004_2938704 - Hotfix_6_0_10005_3099727 - Hotfix_6_0_10006_3054751a - Hotfix_6_0_10007_3164649 - Hotfix_6_0_10008_3186666 - Hotfix_6_0_10010_3113887 - Hotfix_6_0_10011_3247363 - Hotfix_6_0_10012_3248926 For more information about these hotfixes, see the "Errors/Problems fixed" section in this readme. Install instructions ====================| Download the appropriate cumulative public patch (CP) executable file to a temporary location on your system. You can install the CP in a verbose mode or in a non-verbose mode. Instructions for both options are provided below. Each cumulative public patch includes the individual hotfixes that contain enhancements and fixes related to reported issues. See "Errors/Problems Fixed" section for details. Before you begin ----------------:  Ensure that the logged-on user has privileges to install the CP on the systems.  One or more hotfixes that are included with this CP may require a reboot. Before proceeding with the installation ensure that the system can be rebooted.  Symantec recommends that you close the Cluster Manager (Java Console) and the Veritas Enterprise Administrator (VEA) Console before installing this CP.  Before installing CP, ensure that the Startup type of the VCS Authentication Service is set to Automatic. This is applicable only if you have configured a secure cluster and installed CP or Agent Pack 2Q2012 on your system.  Before installing CP on Windows Server Core systems, ensure that Visual Studio 2005 x86 redistributable is installed on the systems. To install in the verbose mode ------------------------------: In the verbose mode, the cumulative public patch (CP) installer prompts you for inputs and displays the installation progress status in the command window. Perform the following steps:  Double-click the CP executable file to extract the contents to a default location on the system. The installer displays a list of hotfixes that are included in the CP. On 64-bit systems, the hotfixes executable files are extracted to: "%commonprogramfiles(x86)%\Veritas Shared\WxRTPrivates\<CPName>" The installer also lists the hotfixes that require a reboot of the system after the installation. If system reboot is not an option at this time, you can choose not to install these hotfixes. In such a case, exit the installation and then launch the CP installer again from the command line using the /exclude option. See "To install in a non-verbose (silent) mode" section for the syntax.  When the installer prompts whether you want to continue with the installation; type Y to begin the hotfix installation. The installer performs the following tasks: - Extracts all the individual hotfix executable files On 64-bit systems the files are extracted at %commonprogramfiles(x86)%\Veritas Shared\WxRTPrivates\<HotfixName> - Runs the pre-install tasks - Installs all the hotfixes sequentially - Runs the post-install tasks The installation progress status is displayed in the command window.  After all the hotfixes are installed, the installer prompts you to restart the system. Type Y to restart the system immediately, or type N to restart the system later. You must restart the system for the changes to take effect. Note that the installer prompts for a system restart only if hotfixes that require a reboot are included in the CP and are installed. To install in the non-verbose (silent) mode -------------------------------------------: In the non-verbose (silent) mode, the cumulative public patch (CP) installer does not prompt you for inputs and directly proceeds with the installation tasks. The installer displays the installation progress status in the command window. Use the VxHFBatchInstaller.exe utility to install a CP from the command line. The syntax options for this utility are as follows: vxhfbatchinstaller.exe /CP:<CPName> [/Exclude:<HF1.exe>,<HF2.exe>...] [/PreInstallScript:<PreInstallScript.pl>] [/silent [/forcerestart]] where, - CPName is the cumulative public patch executable file name without the platform, architecture, and .exe extension. For example, if CP executable name is CP1_VCSW_601_W2K8_x64.exe, specify it as CP1_VCSW_601. - HF1.exe, HF2.exe,... represent the executable file names of the hotfixes that you wish to exclude from the installation. Note that the file names are separated by commas, with no space after a comma. The CP installer skips the mentioned hotfixes during the installation. - PreInstallScript.pl is the Perl script that includes the pre-installation steps. These steps forcefully kill the required services and processes in case a graceful stop request does not succeed. Symantec recommends that you use this option and script only in case the CP installer fails repeatedly while performing the pre-installation tasks. - /silent indicates the installation is run in a non-verbose mode; the installer does not prompt for any inputs during the installation. - /forcerestart indicates that the system is automatically restarted, if required, after the installation is complete. Perform the following steps:  From the command prompt, navigate to the directory where the CP executable file is located and then run the file to extract the contents to a default location on the system. The installer displays a list of hotfixes that are included in the CP. - On 64-bit systems, the hotfixes executable files are extracted to: "%commonprogramfiles(x86)%\Veritas Shared\WxRTPrivates\<CPName>" The installer also lists the hotfixes that require a reboot of the system after the installation. If system reboot is not an option at this time, you can choose not to install these hotfixes. In such a case, launch the CP installer from the command line using the /exclude option.  When the installer prompts whether you want to continue with the installation; type N to exit the installer.  In the same command window, run the following command to begin the CP installation in the non-verbose mode: vxhfbatchinstaller.exe /CP:<CPName> /silent For example, to install a VCSW 6.0.1 x64 CP for Windows Server 2008, the command is: vxhfbatchinstaller.exe /CP:CP1_VCSW_601 /silent The installer performs the following tasks: - Extracts all the individual hotfix executable files On 64-bit systems the files are extracted at %commonprogramfiles(x86)%\Veritas Shared\WxRTPrivates\<HotfixName> - Runs the pre-install tasks - Installs all the hotfixes sequentially - Runs the post-install tasks The installation progress status is displayed in the command window.  After all the hotfixes are installed, the installer displays a message for restarting the system. You must restart the system for the changes to take effect. Note that the installer prompts for a system restart only if hotfixes that require a reboot are included in the CP and are installed. The installer automatically restarts the system if you had specified the /forcerestart option in step 3 earlier. VxHFBatchInstaller usage examples: ---------------------------------- [+] Install CP in silent mode, exclude hotfix Hotfix_6_0_00003_2650336_w2k8_x64.exe: vxhfbatchinstaller.exe /CP:CP1_VCSW_601 /Exclude:Hotfix_6_0_00003_2650336_w2k8_x64.exe /silent [+] Install CP in silent mode, restart automatically: vxhfbatchinstaller.exe /CP:CP1_VCSW_601 /silent /forcerestart Known issues ============| The following section describes the issues related to the individual hotfixes that are included in this CP.  Hotfix_6_0_10006_3054751a In case if you have environment variable in the binary path of services that VCS installs, please run the commands as mentioned in the Workaround. ImagePath has registry value of type REG_EXPAND_SZ which by design expects environment variables to expand, while REG_SZ is just a sequence of characters and it will not support expansion of environment variables. With this hotfix, REG_EXPAND_SZ data type has been changed to REG_SZ. Due to this change, environment variables are not expanded. Workaround: Run the following commands: - sc config vcscomm binPath= "<Value Of>” replace the <value of> with the registry key value of HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\VCSComm\ImagePath - sc config had binPath= "<Value Of>” replace the <value of> with the registry key value of HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\Had\ImagePath - sc config hadhelper binPath= "<Value Of>” replace the <value of> with the registry key value of HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\HadHelper\ImagePath - sc config cmdserver binPath= "<Value Of>” replace the <value of> with the registry key value of HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\CmdServer\ImagePath The above mentioned commands will correct the registry data types. -------------------------------------------------------+ Errors/Problems fixed =====================| The fixes and enhancements that are included in this cumulative public patch (CP) are as follows:  Hotfix name: HotFix_6_0_10002_3065921 Symptom: VMwareDisks agent does not work if ESX is not on the same network as VM. Description: VMwareDisks agent accepts an ESXDetails attribute which contains the details of ESX to be used to perform online/offline operations. In case ESX is not accessible from the VM network, agent will not work. Resolution: VMwareDisks agent has been modified to work with vCenter details as well. ESXDetails attribute will now accept either ESX details or vCenter deatils.No attribute change is involved, the same attribute will be used. Limitation - With vCenter given in the ESXDetails attribute, and if VMHA is not enabled, then if the ESX of the node where application is running faults, then the agent will not be able to detach disks from the faulted ESX's VM. Application failover will not be impacted. The subsequent power ON of the faulted ESX's VM will involve extra manual step to detach disks from the VM. Otherwise VM power ON will not go through. Binary / Version: VMwareDisks.dll / 6.0.10002.264 VMwarelib.dll / 6.0.10002.264 -------------------------------------------------------+  Hotfix name: HotFix_6_0_10004_2938704 Symptom: This hotfix addresses an issue where the MSMQ resource failed to bind to the correct port. Description: When the MSMQ agent was brought online, the Event Viewer reported an error stating that Message Queuing failed to bind to port 1801. This error could occur due to various reasons. Even though the binding failed, the agent reported the MSMQ resource as Online. Resolution: The MSMQ agent has been enhanced to verify that the clustered MSMQ service is bound to the correct virtual IP and port. By default, the agent performs this check only once during the Online operation. If the clustered MSMQ service is not bound to the correct virtual IP and port, the agent stops the service and the resource faults. You can configure the number of times that this check is performed. To do so, create the DWORD tunable parameter 'VirtualIPPortCheckRetryCount' under the registry key 'HKLM\SOFTWARE\VERITAS\VCS\BundledAgents\MSMQ'. If this parameter is set to a value greater than 1, the agent starts the clustered MSMQ service again and verifies its virtual IP and port binding as many times. It waits 2 seconds between each verification attempt. If the clustered MSMQ service is bound to the correct virtual IP and port, the agent reports Online. Binary / Version: MSMQ.dll / 6.0.10004.268 -------------------------------------------------------+  Hotfix name: Hotfix_6_0_10005_3099727 Symptom: [Issue 1] An online Lanman resource takes 1 minute or longer to go offline. [Issue 2] A newly created Lanman resource appears ONLINE even though the service group is not brought online. Description: The Lanman agent does not correctly identify the virtual name (configured under the Lanman resource) that is being monitored or taken offline on a cluster node. This happens if the following conditions are satisfied on the node where the operation is being performed: (a) NetBIOS over TCPIP (NetBT) is disabled on the network adapter. (b) The first few characters of the virtual name (for example, Site10_Svr_ExchApp) are identical to any other virtual name (configured under another Lanman resource) or physical computer name registered on the node (for example, Site10_Svr). No issues occur if the first few characters of the virtual name configured under the Lanman resource (for example, Site10_Svr_ExchApp) are not identical to any other computer name registered on the node (for example, Site10_Svr_EV or Site11_Svr). Resolution: The Lanman agent has been updated to correctly identify the Lanman resource on which an operation is being performed; it now reports the accurate resource status. Binary / Version: Lanman.dll / 6.0.10005.269 -------------------------------------------------------+  Hotfix name: Hotfix_6_0_10006_3054751a Symptom: Windows Server Backup fails to perform a system state backup with the following error: Error in backup of C:\program files\veritas\\cluster server\ during enumerate: Error [0x8007007b] The filename, directory name, or volume label syntax is incorrect. Description: The backup operation fails because the VCS service image path contains an extra backslash (\) character, which Windows Server Backup is unable to process. Resolution: This issue has been fixed by removing the extra backslash character from the VCS service image path. This hotfix changes the following registry keys: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Had\ImagePath HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HADHelper\ImagePath HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Cmdserver\ImagePath HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VCSComm\ImagePath -------------------------------------------------------+  Hotfix name: Hotfix_6_0_10007_3164649 Symptom: The Exchange 2010 Database Agent Configuration Wizard does not create a MountV resource for certain transaction logs. Description: This issue occurs only if the transaction logs folder of the Exchange 2010 database is located directly on the folder mount, instead of being located within another folder on the root drive. Resolution: The Exchange 2010 Database Agent Configuration Wizard has been updated to resolve this issue. It now creates the MountV resource for the transaction logs even if they are located in a subfolder on the root drive. Binary / Version: Exch2010Wizard.exe / 6.0.10007.274 -------------------------------------------------------+  Hotfix name: Hotfix_6_0_10008_3186666 Symptom: Users are unable to add or modify custom settings on printers clustered under VCS. Description: When a printer with custom settings (like printing shortcuts) is added to VCS clustered virtual name, the printer settings become unavailable. This issue occurs because any customizations to printer settings are not recognized after a printer is clustered. Resolution: This hotfix addresses the issue. However, for the hotfix to work, you need to perform the following tasks manually. Create the following DWORD registry key and set its value to 1. - For global configurations, create: HKEY_LOCAL_MACHINE\SOFTWARE\VERITAS\VCS\BundledAgents\PrintSpool\__GLOBAL__\PrinterDriverSupport - For per resource configurations, create: HKEY_LOCAL_MACHINE\SOFTWARE\VERITAS\VCS\BundledAgents\PrintSpool\ <resource_name>\PrinterDriverSupport After creating this key, do one of the following: - If a PrintSpool resource if offline, bring it online. - If a PrintSpool resource is already online, probe it. Upon installing the hotfix, the PrintSpool agent creates the 'HKEY_LOCAL_MACHINE\Cluster' key. Make sure that the key exists, and then add printers to the virtual name. NOTE: Existing printers will continue to have this issue. Symantec recommends deleting and re-creating such printer resources. CAUTION: This hotfix may cause unexpected effects on other applications that can be clustered (or are already clustered) on the same node. Binary / Version: PrintSpool.dll / 6.0.10008.275 -------------------------------------------------------+  Hotfix name: Hotfix_6_0_10010_3113887 Symptom: After every 49.7 days, VCS logs report that the Global Counter VCS attribute is not updated. This error is reported on all nodes in the cluster, except the node with the lowest node ID value. The 'GloablCounter not updated' error also appears in the Event Viewer. Description: The error indicates that there could be communication issues between the cluster nodes. However, this error is incorrectly reported, and no communication issues actually occur. Resolution: This issue has been fixed and the error is no longer reported at that odd interval. Binary / Version: had.exe / 6.0.10010.277 hacf.exe / 6.0.10010.277 -------------------------------------------------------+  Hotfix name: Hotfix_6_0_10011_3247363 Symptom: The VCS for Windows FileShare and SQL Server 2008 agent configuration wizards do not recognize shared disks if they are available on same bus as the system LUN, for example, when booting from SAN. Description: Even though the necessary shared disks are attached, the VCS for Windows configuration wizards display the following error: "No shared drives discovered. Possibly the volumes are already part of another service group in the current configuration." Resolution: This hotfix addresses the issue. However, for the hotfix to work, you must create the following DWORD registry key and set its value to 1, on all the nodes in the cluster: HKEY_LOCAL_MACHINE\SOFTWARE\VERITAS\VCS\BundledAgents\DiskRes\__global__\AllowDisksOnOSPort Relaunch the configuration wizards after applying this hotfix and creating this registry key. KNOWN ISSUE: The VCS for Windows FileShare and SQL Server 2008 agent configuration wizards allow you to select system volumes for application clustering. However, when the configuration is complete, the corresponding mount resource goes into the UNKNOWN state. (3270171) Binary / Version: DiskResDiscover.dll / 6.0.10011.279 -------------------------------------------------------+  Hotfix name: Hotfix_6_0_10012_3248926 Symptom: VCS for Windows does not support NetApp SnapDrive 6.4 or later. Description: Support for NetApp SnapDrive 6.4 onwards is required. Resolution: This hotfix adds support for NetApp SnapDrive 6.4 and 6.5 to VCS for Windows. -------------------------------------------------------+ Additional notes ================| [+] To confirm the list of patches installed on a system, run the following command from the directory where the CP files are extracted: vxhfbatchinstaller.exe /list The output of this command displays a list of patches and the hotfixes that are installed as part of a CP. This command also displays the hotfixes that are included in a CP but are not installed on the system. [+] To confirm the installation of the hotfixes, perform one of the following: - Run the following command: vxhf.exe /list The output of this command lists the hotfixes installed on the system. - In the Windows Add/Remove program, click "View installed updates" to view the list of the hotfixes installed on the system. [+] The CP installer (vxhfbatchinstaller.exe) creates and stores logs at: "%allusersprofile%\Application Data\Veritas\VxHF\VxHFBatchInstaller.txt" [+] The hotfix installer (vxhf.exe) creates and stores logs at: "%allusersprofile%\Application Data\Veritas\VxHF\VxHF.txt" [+] 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 is provided without warranty of any kind including the warranties of title or implied warranties of merchantability, fitness for a particular purpose and non-infringement. Symantec disclaims all liability relating to or arising out of this fix. 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 if you sign up for notifications from the Symantec support site http://www.symantec.com/business/support and/or from Symantec Operations Readiness Tools (SORT) http://sort.symantec.com.