Re: Installing TSM 4.1.0 Client in a WNT Server

Gerardo,

Does this system have NTFS 8.3 file name creation disabled? If
so, the following APAR (IC29085) probably describes your problem:

========== BEGIN APAR TEXT ==========
ABSTRACT:
THE WIZARD WAS INTERRUPTED BEFORE TIVOLI STORAGE MANAGER CLIENT
COULD BE COMPLETELY INSTALLED. YOUR SYSTEM HAS NOT BEEN MODIFIED

ERROR DESCRIPTION:
When installing the TSM 4.1 client for Microsoft Windows, rather
than seeing the "Welcome" dialog, you may see a dialog whose
text reads:

   The wizard was interrupted before Tivoli Storage Manager
   Client could be completely installed. Your system has not
   been modified. To complete the installation at another time,
   please run setup again.

If you run setup.exe with verbose logging active:

   setup /v"/l*v setup.log"

The setup.log will show that the setup ends with return code
1603. This is a result of a failure in the StartUp action, which
ends with return value 3. The following is a segment from a
typical setup.log file showing the error in StartUp:

   Action start 8:19:57: StartUp.
   MSI (c) (2D:32): Transforming table Binary.
   MSI (c) (2D:32): Creating MSIHANDLE (37) of type 790542 for
                    thread 306
   Action ended 8:19:58: StartUp. Return value 3.

The problem is in the InstallShield for Windows Installer
software that is used to package the client. The problem occurs
when 8.3 file name creation support for NTFS file systems has
been disabled on Windows NT or 2000 (Windows 9x users should not
experience this problem).

If you are having problems installing the TSM 4.1 Windows
client, run setup.exe with verbose logging enabled (as described
above). After the failure, examine the resulting setup.log file
for return code 1603 (near the bottom of the file) and the
StartUp failure described above. If setup.log matches these two
symptoms, then the next step is to verify whether 8.3 file name
creation is disabled, as follows:

1) Examine the following registry key:

  HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem

2) Within that key, locate a value with the name:

   NtfsDisable8dot3NameCreation

   If this value is set to 1, then 8.3 file name creation is
   disabled, and this APAR is a match for the problem. If the
   value is 0, then 8.3 file name creation is enabled, and this
   APAR is not a match for the problem.

Alternative: if you are unfamiliar or uncomfortable with
accessing the registry, then you can run the following command
from an OS prompt to obtain the same information. This command
only reads certain values from the registry; it does not update
the registry:

   regedit /e myreg.txt HKEY_LOCAL_MACHINE\SYSTEM\CurrentControl
   Set\Control\FileSystem

(Note: due to width restrictions, the above "regedit" command is
shown on two lines although it is one long command. There are no
spaces between "CurrentControl" at the end of the first line and
"Set" at the beginning of the next line.

The command will save the output to a file called myreg.txt.
Review the myreg.txt file and look for the following line:

   "NtfsDisable8dot3NameCreation"=dword:00000001

If the value following "dword:" is 00000001 then 8.3 file name
creation is disabled, and this APAR is a match for the problem.
If the value is 00000000, then 8.3 file name creation is enabled
and this APAR is not a match for the problem.

LOCAL FIX:
If 8.3 file name creation is disabled, you can circumvent the
problem by temporarily reactivating the 8.3 file name creation.
Here is how to do this:

NOTE: Mistakes in editing the registry can introduce instability
to your system, or even make it unusable or unbootable. It is
recommended that you back up your registry before editing it. If
you are unfamiliar or uncomfortable with editing the registry,
you should ask someone else who has expertise in editing the
registry to make this change for you.

1) Change NtfsDisable8dot3NameCreation value to 0.

2) Reboot Windows.

3) Run setup.exe to install TSM.

4) Disable 8.3 file name creation (if you wish) after the
   install runs by resetting NtfsDisable8dot3NameCreation to 1
   and rebooting.

Reference: Microsoft article "Q210638 - How to Disable Automatic
           Short File Name Generation".
=========== END APAR TEXT ===========

Hope this helps,

Andy

Andy Raibeck
IBM Tivoli Systems
Tivoli Storage Manager Client Development
e-mail: araibeck AT tivoli DOT com
"The only dumb question is the one that goes unasked."
"The command line is your friend"

>> Gerardo Zapata wrote:

Hi, I'm trying to install the TSM client 4.1.0 in a Windows NT Server SP6
which is a node of an MS Cluster. When running the setup.exe the installation
wizard stops with the following error message:

"The wizard was iterrupted before Tivoli Storage Manager could be completely
installed. Your system has not been modified. To complete installation at
another time, please run setup again"

Checking the NT Event Viewer, found an application error produced by the
"MS Installer" with no more detailed information.

Any suggestion, known experience or idea of the cause?

Thanks in advance

___________________________________
Gerardo Zapata
IT Specialist
Infrastructure & Systems Management

IBM Mexico
(525) 270 5889