Installation troubleshooting and best practices for Veritas Storage Foundation for Windows

  • Article ID:100031243
  • Last Published:
  • Product(s):InfoScale & Storage Foundation


Installation troubleshooting and best practices for Veritas Storage Foundation for Windows



This article addresses the most common causes for problems that occur while installing Veritas Storage Foundation for Windows (SFW).

SECTION I - Useful Documentation

1. Read the installation guides and release notes to review the installation steps for your environment and learn about installation problems that are already known to Veritas.
Installation & Upgrade Guides :
For SFW 6.0.1: 
For SFW 6.0: 
For SFW 5.1 SP2: 
For SFW 5.1 SP1: 

Release Notes:

2.  Ensure that the configuration matches the HCL (Hardware Compatibility List) and the SCL (Software Compatibility List).
Both of these documents can be found here:
From the window header:
·          Select Veritas Storage Foundation and High Availability (SFW/HA)
·          Select Windows.
·          Check the Compatibility Lists checkbox.
·          Check the English checkbox (or other preferred language).
From the list that loads in the window body:
·          Select Compatibility Lists for your version of SFW/HA
an article that explains how to read the HCL can be found here:

SECTION II - Initial Troubleshooting Steps

1. Log into a console session. Start any Remote Desktop sessions with the "console" switch. This can be done by typing the following from a Windows command prompt:
mstsc /console
2. Verify that Driver Signing is set to Ignore. This can be checked by performing the following steps:

a. Right-click on  My Computer.
b. Select  Properties.
c. Click  Hardware.
d. Click  Driver Signing
e. Select  Ignore - Install the software anyway and don't ask for my approval.


Important Note:
      Installing Veritas Trusted certificate for unsigned drivers
Beginning with Storage Foundation for Windows 5.1 SP2, the Veritas product installer provides an installation option for Veritas Trusted Software Publisher Certificate for Veritas Storage Foundation for Windows drivers that are not certified by Microsoft.
If you select this installation option, a Veritas Trusted certificate is installed
on the systems you select for installation.
Warning: On Windows Server 2008, if this option is not selected, a remote install
will not install any SFWdrivers that are not certified by Microsoft. No notification
is given and it will appear that installation was successful, but issues can arise
later because the drivers were not installed. If installing locally on Windows Server
2008, if this option is not selected, a driver signing popup will be displayed
requiring user interaction.
If you select this option when installing on Windows Server 2003, you do not need
to set the driver signing options to Warn or Ignore.

3. Log in with a user account that is a member of the local Administrators group. If the user is a Domain Administrator, verify that the Domain Admins group is member of the local Administrators group.
4. Log into the Domain (not the local computer). 

SECTION III - Reviewing the PATH Statement

Many installation failures are caused by problems with the PATH statement.

1. From a Windows command prompt, use Echo to determine the values of TEMPTMPPATH, and PROGRAMFILES.
For example:
echo %TEMP%
This returns the path to the temp folder that is associated with the logged in user. 
2. Ensure that all of the values that are returned are pointing to real folders and are valid.
Note: It is particularly critical to check this if roaming profiles are enabled.
3. Remove any files that are contained within the user temp folder that was returned by the Echo command. 
Note: This will not necessarily be c:\windows\temp. Use the Echo command to determine the location of the user temp folder.
4. In many environments, the PATH variable is limited to 1023 characters. Ensure that there is enough unused space within this variable to accommodate the any paths that are added by the SFW installation. A typical installation of SFW can add over 300 characters to this statement. If the statement already contains numerous paths, the SFW installation may not complete properly (Figure 1).

Figure 1


Note: Starting with Windows 2003, the maximum size of the PATH has been increased to a theoretical limit of 2047 characters. However, this new limit is not always realized unless Windows 2003 Service Pack 2 is installed. Information on this issue can be found in the following Microsoft article:  

Additional information about the PATH statement can be found in the following Microsoft article:  

SECTION IV - Security Templates

Security templates that have been designed for high security will interfere with an installation of SFW. In some cases, it is necessary to temporarily revert to a less-secure template for the duration of the installation. 

Information on security templates for Windows 2003 can be found here:
For information regarding Security Templates and their use in Windows Server 2008, refer to the following article:
Note: Importing or modifying a security template should only be performed with a full understanding of the effects that the changes will make.

SECTION V: Further Troubleshooting

1. Insufficient DCOM (Distributed Component Object Model) permissions will cause an installation of SFW to fail. Information about checking and configuring DCOM permissions can be found in the following article:
2. The VPI (Veritas Product Installer) creates log files during the installation that can be reviewed to determine the cause of the failure. By default, these logs are stored in the following locations:
    For Windows Server 2003:
         C:\Documents and Settings\All Users\Application Data\VERITAS\VPI\log
    For Windows Server 2008:
VxInstaller.log and  VPITrace.log can be used to determine the component that was being installed at the time of the failure. Once the name of the component has been determined, review the MSI (Microsoft Installer) log that is associated with the affected component. The MSI log files will end with an *.msi.log file extension. 
Note: When reviewing an MSI log, searching for "Return Value 3" is useful for locating an error.

Keywords: 292314, install, installation, installing, installation failed, installation fails, install fails, percent, %




Was this content helpful?

Get Support