3 replies to this topic

[Barbara]

A customer has problems to install a Setup on its W2k Server SP4 machine. The reason is, that ISStartup is not working. Here is the part of the LogFile:

##########################################
MSI © (7C:F4): Doing action: ISMsiServerStartup
Aktion gestartet um 15:25:42: ISMsiServerStartup.
MSI © (7C:F4): Creating MSIHANDLE (1) of type 790542 for thread 1524
Aktion beendet um 15:25:42: ISMsiServerStartup. Rückgabewert 1.
MSI © (7C:F4): Doing action: ISStartup
Aktion gestartet um 15:25:42: ISStartup.
MSI © (7C:F4): Creating MSIHANDLE (2) of type 790542 for thread 1524
Aktion beendet um 15:25:42: ISMsiServerStartup. Rückgabewert 1603.
Aktion beendet um 15:25:52: ISStartup. Rückgabewert 3.
MSI © (7C:F4): Doing action: SeStartup not workingtupCompleteError
Aktion gestartet um 15:25:52: SetupCompleteError.
Information 2898. Tahoma8, Tahoma, 0
Information 2898. TahomaBold10, Tahoma, 0
Aktion 15:25:52: SetupCompleteError. Dialog created
##########################################

When he klicks the Finish-Button of the SetupCompleteError Dialog, the Setup hangs.
I supposed the DCOM Settings or some hanging Idriver processes to be the reason, but no luck.
Also searched through the different Knowledge Bases and found nothing.
Any other suggestions ?

Thank you
Barbara

[Glytzhkof]

Might be worth checking if the MSI service is disabled.

[Barbara]

The Windows Installer Service must be working because setups without InstallSkript are installing without problems.

Barbara

[Barbara]

The solution was: All the permisions on the server were set wrong, only IUSR_... had access rights.

Barbara