Hi all,

Several users have reported problems installing the TSM 4.1 client.
Symptoms include:

1) Instead of seeing the "Welcome" dialog, you see a dialog that says, "The
wizard was interrupted before Tivoli Storage Manager Client could be
completely installed. Your system has not been modified. To complete
installation at another time, please run setup again."

2) Error code 1603 from the setup program.

3) If you run setup with verbose logging turned on:

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

You will see that the StartUp action ends with return value 3. Here is a
segment from a typical setup.log file showing the problem:

   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.

One problem that we've identified is with the InstallShield for Windows
Installer software that we use to package the TSM client and TSM server for
Windows. The problem stems from cases where 8.3 file name creation support
for NTFS file systems has been disabled on Windows NT/2000. (Windows 9x
should not see this problem.)

If you are having problems installing the TSM 4.1 Windows client and/or
server, you can verify whether the 8.3 file name creation is at issue. Here
is how to do this:

1) Examine the following registry key:

   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem

2) In that key, locate a value named "NtfsDisable8dot3NameCreation". If
this value is set to 1, then 8.3 file name creation is turned off, and this
is most likely the problem. If the value is set to 0, then 8.3 file name
creation is still active, and this is probably not the problem. I suspect,
though, that you will find that this is the problem.

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

   regedit /e myreg.txt 
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem

Note: due to width restrictions, the above "regedit" command may appear to
consist of more than one line. If this is the case, ignore the line breaks;
this is one, continuous command.

Then review the myreg.txt file and look for the following line:

   "NtfsDisable8dot3NameCreation"=dword:00000001

If the value after "dword" is 00000001 then 8.3 file name creation is
disabled. If the value is 00000000, then 8.3 file name creation is enabled,
and this is not the problem.

We are pursuing this issue with InstallShield and will be expecting them to
provide something in the form of a code fix (no ETA at this time). In the
mean time, you can circumvent this 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 and unbootable. It is recommended that you
back up your registry before editing it. If you are unfamiliar or
uncomfortable with editing the registry, then you should ask someone else
who has expertise in editing the registry to make this change for you.

1) Change the above NtfsDisable8dot3NameCreation value to 0.

2) Reboot Windows (this is necessary and out of our control).

3) Run SETUP.EXE to install TSM.

If you wish to deactiate 8.3 file name creation after the install runs,
simply reset NtfsDisable8dot3NameCreation to 1 and reboot.

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

Andy Raibeck
IBM/Tivoli
Tivoli Storage Manager Client Development
e-mail: andrew.raibeck AT tivoli DOT com
"The only dumb question is the one that goes unasked."