Troubleshooting a Sametime Gateway installation

These steps help you troubleshoot installation problems by describing how you can use a different tablespace name for the database and how you can clean your system of previous installations.

About this task

Many installation problems are caused when the installer cannot locate the database or when installing a new instance of Sametime® Gateway and a previous installation has not been completely removed from the system. The following steps describe how to use a different tablespace in the database or clean your system of previous installations.

Procedure

  1. Open the installation log file at stgw_server_root\logs\installlog.txt
  2. If the log reports an error in finding the DB2® database, check to make sure you are using the tablespace name USERSPACE1. Sametime Gateway expects USERSPACE1 by default. To install using a different tablespace name, use the following command when you run the installer:
    install.bat -VTableSpaceName="tableSpaceName"
    Where tableSpaceName is the name of the tablespace that you want the installer to use.
  3. To clean your system of previous installations, use the log to find the location of the Install Shield Multiplatform (ISMP) database called the Vital Product Database (VPD). For example, examine this log entry from Windows® (formatted to fit on the page): 
    (Dec 24, 2009 2:22:22 PM), stGwInstall, 
com.ibm.rtc.gateway.install.CheckVPDRegistry, msg1, 
using VPD registry at C:\Program Files\Common 
Files\InstallShield\Universal\common\Gen2\_vpddb\vpd
    The location of this registry varies from system to system. On windows, VPD is usually found in the \Program Files\Common Files\InstallShield\Universal\common\Gen2 folder. If a Sametime Gateway server is uninstalled, but an error occurs and the product is not unregistered, the VPD shows that Sametime Gateway is installed on the system. When a new installation is initiated, and a previously installed Sametime Gateway server is detected, the installer prompts you to upgrade or install a new version, or the installer forces you to install a Deployment Manager server or a Primary Server on the same system. None of these scenarios are desired because there are no Sametime Gateway servers installed on the system.
  4. Back up the Gen2 folder.
    Note that the VPD registry may be used by other programs that are installed with InstallShield, so removing this registry may interfere with other programs. Do not remove the Gen2 folder unless it is absolutely necessary.
  5. Remove the original Gen2 folder.
  6. If installing on Windows, delete the following remaining files:
    C:\Windows\.nifregistry
C:\Windows\vpd.properties
  7. Start the installation again.