4 replies to this topic

[tomassa]

Hi
I got a problem at customer site, they try to install silent via Tivoli using command-line args., but repeately end up with error like this in the log file:

MSI © (C8:CC): Doing action: ISMsiServerStartup
Action start 08:07:37: ISMsiServerStartup.
MSI © (C8:CC): Creating MSIHANDLE (1) of type 790542 for thread 3788
Action ended 08:07:37: ISMsiServerStartup. Return value 1.
MSI © (C8:CC): Doing action: ISStartup
Action start 08:07:37: ISStartup.
MSI © (C8:CC): Creating MSIHANDLE (2) of type 790542 for thread 3788
1: The InstallScript engine version currently installed on this machine is adequate.
1: Event 'E738129' is created
1: GetInstallDriver, Can not find InstallDriver in ROT table, Return Code = 0x800401e3
1: {B376F08C-4964-439D-B822-2F0E4C49A17F}
1: Extract supporting files
1: Failed to extract _IsUser.dll, Ignore it.
1: Ev1813088
1: ISMsiServerStartup Failure, Failed to Open the shutdown event, Error 0x36b0
1: MsiServerStartup failed. Abort installation.
Action ended 08:07:39: ISMsiServerStartup. Return value 1603.
Action ended 08:07:39: ISStartup. Return value 3.
MSI © (C8:CC): Doing action: SetupCompleteError
Action start 08:07:39: SetupCompleteError.
Info 2898.Tahoma8, Tahoma, 0
Info 2898.TahomaBold10, Tahoma, 0
Action 08:07:39: SetupCompleteError. Dialog created
Action start 08:07:43: ISCleanUpFatalExit.
Action ended 08:07:43: ISCleanUpFatalExit. Return value 3.
DEBUG: Error 2896:  Executing action ISCleanUpFatalExit failed.
Internal Error 2896. ISCleanUpFatalExit
Action ended 08:07:43: SetupCompleteError. Return value 3.
Action ended 08:07:43: INSTALL. Return value 3.
MSI © (C8:CC): Closing MSIHANDLE (1) of type 790542 for thread 3788
MSI © (C8:CC): Destroying RemoteAPI object.

We have checked following:
- Check DCOM setting permissions
- Short file name creation is disabled on the target machine.
- Increase DiskSpace requirement in Setup.ini and try again.
- Reinstall Windows Installer by running InstMsiW.exe file to reinstall.
- The Windows Temp folders are full

But still with no success.

Especially the row:
"1: ISMsiServerStartup Failure, Failed to Open the shutdown event, Error 0x36b0"
confuses me, I find no hits on this in this forum or Installshield forum.

What to do? Any clues?

BR /Tomassa

[winklmj]

Bump...

I'm seeing this exact error too. Can't figure it out. We're doing a "silent" install of a vendor provided Setup.exe (meaning we didn't author the setup nor the MSI it contains).

[Stefan Krueger]

Hard to tell what's going wrong, especially without knowing the exact project type that was used to create the setup. I'd suggest you contact the author of the setup first.

[Morbid]

We are now experiencing this EXACT problem. The product is a McKesson product that installs fine if executed locally by a user with Admin privileges. However, if Tivoli installs the same program, we are recieving the exact message in the logs that the user posted in the OP.

We have spent a week going over EVERYTHING suggested when experiencing a 1603 error code, but to no avail. I, like the original poster, am curious to what

"1: ISMsiServerStartup Failure, Failed to Open the shutdown event, Error 0x36b0"

means, as it seems to be the root of the problem. I have found no mention of this message aside from this post.

Thanks for any advice.

[Stefan Krueger]

I suspect it's the same problem as discussed here:
http://community.ins...ad.php?t=149462

The problem seems to be which user the InstallScript engine tries to impersonate if setup is pushed unattended.

Unfortunately, I there doesn't seem to be a solution to this problem except getting rid of the InstallScript.

You could try playing with the DCOM settings (there's a KB artcile about that at support.installshield.com) maybe that would help in your case.