---------------------- Weitergeleitet von Holger Bitterlich/BK/SK-Koeln am
07.03.2001 10:32 ---------------------------
An: [EMAIL PROTECTED]
Kopie:
Thema: Antwort: Re: TSM and Windows Installer Problems
good morning Andrew,
thanks for answering so fast ! I examined your suggestions.
to point 1: On the first Server ther was no NULL string, on the 2nd there was.
On this Machine I kicked out the registry key containong the NULL value,
rebooted, restart the installation and - get the same error: "Error 1631: The
windows installer service failed to start. Contact your support personnel".
to point 2: the registry on these two boxes contains the correct value "0". So
the Installation should go on, but it doesn`nt.
So these are the bad good news. What to do now ?
Thanks in advance
Holger
PS: Andrew, in the meantime I`m registered at the mailing list. I think it`s a
good idea to post this onto the adsm-lv List. So anotherone can participate.
An: Holger Bitterlich/BK/SK-Koeln@SK-Koeln
Kopie:
Thema: Re: TSM and Windows Installer Problems
Hi Holger,
A couple of questions:
1) On the problem machines, did you check whether you
have a NULL environment variable? This is described
in the workaround in article Q251274 that you
mentioned:
Examine the following registry key:
HKEY_LOCAL_MACHINE\
SYSTEM\
CurrentControlSet\
Control\
SessionManager\
Environment
In the Environment key, look for any values where
the data is NULL (i.e. empty string). If you find
any, try removing that datum from the key, reboot,
then retry the install. You should write down the
name of the datum item so you can put it back later,
if necessary.
2) The other problem we know about is one where 8.3
file name creation has been turned off. You can
verify this by checking registry key:
HKEY_LOCAL_MACHINE\
SYSTEM\
CurrentControlSet\
Control\
FileSystem
In that key, look at the value for datum
NtfsDisable8dot3NameCreation. If the value is
'1', then 8.3 name creation is disabled. To
install TSM, you will need to set this value
to '0', reboot, then try the install. After the
install finishes, set the value back to '1' and
reboot.
If none of these suggestions help, then can you open a
problem record with your local IBM office? We do have
some customers reporting the same symptoms as you, and
the above ideas do not help. At this time we are
investigating them, so if you have a record open, you
can be kept apprised of the progress.
With kindest regards,
Andy
Andy Raibeck
IBM Tivoli Systems
Tivoli Storage Manager Client Development
e-mail: [EMAIL PROTECTED]
"The only dumb question is the one that goes unasked."
Andrew,
at ADSM.org I read your article illustrating the Problems with the windows
installer and TSM Client 4.1 . I updated round about 70 NT boxes, without any
Problems. But on two I encountered large Trouble. After the Windows Installer
has been started, the TSM Client setup should go on. But instead of this the TSM
Install Process stopped and reads :
"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."
I installed on NT Boxes running NT 4.0 with Service Pack 4, 5, 6 , and 6a,
without any trouble. The failing Machine has SP 6 and hotfixes Q147222 and
Q246009 installed OS and SP`s are german, don`t know if this has any meaning for
you). I tried installing by using the local Admin account, as you mentioned.
Also, I stopped everything (eg. Services, batches,...) running on that box.
Then I ran SETUP /V"/L*V SETUP.LOG" . The result you can find at the end of
this mail.
OK,
that`s one Problem. The other one is known at Microsoft by the Patch Q251274.
The Symtom is the Installer stopps with error 1631. They (Microsoft) suggest to
exchange an dll file (userenv.dll Date:1/18/2000 Time:3:47pm Size 76,048) . But
they are not sure what will happen, read the bugfixing, its a joke ( not really,
it`s gloomy) . But the biggest thing is tha you can`t find this dll at
Microsoft at all, not even in the net . The only dll`s I can find have different
Sizes, dates, ... .
This is what the log says: (soory, it`s in german)
=== Protokollierung gestartet: 05.03.01 15:32:00 ===
Aktion gestartet um 15:32:00: INSTALL.
Aktion gestartet um 15:32:00: EngineStartup.
1: extracting engine MSI file
1: Installing kernel files
1: scpthdlr.dll
1: After file installation, return code = 0
1: ikernel.exe
1: After file installation, return code = 0
1: iuser.dll
1: After file installation, return code = 0
1: knlwrap.exe
1: After file installation, return code = 128
1: msihook.dll
1: After file installation, return code = 0
1: objectps.dll
1: After file installation, return code = 0
1: Installing script engine
1: iscript.dll
1: After file installation, return code = 0
Aktion beendet um 15:32:13: EngineStartup. Rückgabewert 1.
Aktion gestartet um 15:32:13: StartUp.
Aktion beendet um 15:32:16: StartUp. Rückgabewert 3.
Aktion gestartet um 15:32:16: SetupCompleteError.
Interner Fehler 2898. Tahoma8, Tahoma, 0
Interner Fehler 2898. TahomaBold10, Tahoma, 0
Aktion 15:32:17: SetupCompleteError. Dialog created
Aktion beendet um 15:32:21: SetupCompleteError. Rückgabewert 2.
Aktion beendet um 15:32:21: INSTALL. Rückgabewert 3.
=== Protokollierung beendet: 05.03.01 15:32:21 ===
MSI (c) (D9:C4): Produkt: Tivoli Storage Manager Client -- Installationsvorgang
fehlgeschlagen.
Can you help me ?
Thx a lot !!!
Regards HBit
______________________________________________________________________
Da E-Mails leicht unter fremdem Namen erstellt oder manipuliert werden
koennen, muessen wir zu Ihrem und unserem Schutz die rechtliche
Verbindlichkeit der vorstehenden Erklaerungen ausschliessen. Die fuer die
Stadtsparkasse Koeln geltenden Regeln ueber die Verbindlichkeit von
rechtsgeschaeftlichen Erklaerungen mit verpflichtendem Inhalt bleiben
unberuehrt.
