Verifying the silent installation

To verify that the silent installation was successful, you can check the return code, log file, and the Windows registry.

Common reasons for the silent installation failing are:

• A previous or current version of Tivoli Directory Server is already installed. Only the following are supported:
  • A client from Tivoli Directory Server 6.0, 6.1, or 6.2
  • A server from Tivoli Directory Server 6.0, 6.1, or 6.2
• The prerequisites are not present. The server requires a valid version of DB2®, or DB2 must already be installed.
• There is not enough disk space to install.
• The options file is incorrect. Be very careful when editing the options file. There cannot be blank lines or control characters in the file. If the installation exits with no log file, this is usually because the options file is not valid (with blank lines, for example), or because the path to the options file was specified incorrectly.

Checking the return code

The %ERRORLEVEL% variable contains the return code. The following return codes can be received:

• 2002 Java exception (A possible cause is that you are attempting to install to a location where another version is installed. If you receive this return code, entries might have been created for Tivoli Directory Server 6.3 in the registry. Check the registry and, if there are any such entries, remove them before you try to install again.)
• 3001 Prerequisites missing
• 3002 Java exception
• 3003 No feature selected for silent install
• 3009 Cannot install a feature. (Refer to the log for the reason.)

Other return codes might be returned from the InstallShield program.

Checking the log file

To verify that silent installation was successful using the log file:

1. Check the log file to see if it exists in the target directory. If the log is not there, the installation failed, and you can refer to the log file that was specified on the silent installation command with the -log option to see why the installation failed.
2. Check the log file for the string Exiting LdapExit.

Checking the Windows registry

Verify that the installation was completed using the Windows registry. The following text should be in the registry, depending on which components were installed:

In HKEY_LOCAL_MACHINE\SOFTWARE\IBM\IDSLDAP\6.3

            ClientMajorVersion 6.3
            JavaClientMajorVersion 6.3
            BaseServerMajorVersion 6.3
            ServerMajorVersion 6.3
            ProxyServerMajorVersion 6.3
            WebadminMajorVersion 6.3
            WebSphereAppSrvMajorVersion 7.0
            LDAPHome install_location
            BitMode   set to 32 or 64

In HKEY_LOCAL_MACHINE\SOFTWARE\IBM\IDSLDAP\6.3\Client\

            ClientMinorVersion 0.0

In HKEY_LOCAL_MACHINE\SOFTWARE\IBM\IDSLDAP\6.3\JavaClient\

            JavaClientMinorVersion 0.0

In HKEY_LOCAL_MACHINE\SOFTWARE\IBM\IDSLDAP\6.3\Webadmin\

            WebadminMinorVersion 0.0

In HKEY_LOCAL_MACHINE\SOFTWARE\IBM\IDSLDAP\6.3\BaseServer\

            BaseServerMinorVersion 0.0             

In HKEY_LOCAL_MACHINE\SOFTWARE\IBM\IDSLDAP\6.3\Server\

            ServerMinorVersion 0.0             

In HKEY_LOCAL_MACHINE\SOFTWARE\IBM\IDSLDAP\6.3\ProxyServer\

            ProxyServerMinorVersion 0.0             

In HKEY_LOCAL_MACHINE\SOFTWARE\IBM\IDSLDAP\6.3\WebSphereAppSrv\

            WebSphereAppSrvMinorVersion 0.7

In HKEY_LOCAL_MACHINE\SOFTWARE\IBM\IDSLDAP\6.3\LanguagePack\

            LangPackVersion 6.3
            LPHome install_location

By default, LPHome is set to ldaphome\LangPack.

In addition, if you are installing on AMD/EM64T Windows, the following text is also in the registry.

In HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432NODE\IBM\IDSLDAP\6.3

            ClientMajorVersion 6.3
            JavaClientMajorVersion 6.3
            BaseServerMajorVersion 6.3
            ServerMajorVersion 6.3
            ProxyServerMajorVersion 6.3
            WebadminMajorVersion 6.3
            WebSphereAppSrvMajorVersion 7.0
            LDAPHome install_location 
            BitMode   64

In HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432NODE\IBM\IDSLDAP\6.3\Client\

            ClientMinorVersion 0.0

In HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432NODE\IBM\IDSLDAP\6.3\JavaClient\

            JavaClientMinorVersion 0.0

In HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432NODE\IBM\IDSLDAP\6.3\Webadmin\

            WebadminMinorVersion 0.0

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432NODE\IBM\IDSLDAP\6.3\BaseServer\

            BaseServerMinorVersion 0.0

In HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432NODE\IBM\IDSLDAP\6.3\Server\

            ServerMinorVersion 0.0

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432NODE\IBM\IDSLDAP\6.3\ProxyServer\

            ProxyServerMinorVersion 0.0

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432NODE\IBM\IDSLDAP\6.3\WebSphereAppSrv\

            WebSphereAppSrvMinorVersion 0.7

[ Top of Page | Previous Page | Next Page ]