4 replies to this topic

[noquestion]

Hello All,

I created a kind of Plug-In that acts a a stand-alone installation that has a UI, but should also be installed silent in some cases. I have a Custom IScript action "Resolve_XXX_DIR", where I do not ignore the returnvalue, and that has "Execute only once" set and the is placed in the UI sequence and the Execute sequence. I use ISWI 2.03.

If I start in in the script debugger with the settings:
/qn /Liwrmo!veapcu c:\logmpg.log
everything is OK.

If I start
setup.exe /S
everything is OK too.

only if I start:
msiexec /I "...my.msi" /qn
the installation fails at the custom action whichs returnvalue is not ignored.
I tried return 1 and return ERROR_SUCCESS. Both failed.
Any ideas ? And what is the difference between Setup.exe /S and msiexec /I ..... /qn

If the installation failes, the log says:

1: ISScriptHandle engine Started
1: Extracting support files...
1: Script Handler initialization failed, error = 0x0
1: StartUp 2: 1
MSI (s) (6C:90): Doing action: LaunchConditions
1: LaunchConditions 2: 1
MSI (s) (6C:90): Note: 1: 2262 2: LaunchCondition 3: -2147287038
1: LaunchConditions 2: 1
MSI (s) (6C:90): Doing action: FindRelatedProducts
1: FindRelatedProducts 2: 1
MSI (s) (6C:90): Note: 1: 2262 2: Upgrade 3: -2147287038
1: FindRelatedProducts 2: 1
MSI (s) (6C:90): Doing action: AppSearch
1: AppSearch 2: 1
MSI (s) (6C:90): Note: 1: 2262 2: AppSearch 3: -2147287038
1: AppSearch 2: 1
MSI (s) (6C:90): Skipping action: CCPSearch (condition is false)
MSI (s) (6C:90): Skipping action: RMCCPSearch (condition is false)
MSI (s) (6C:90): Doing action: ValidateProductID
1: ValidateProductID 2: 1
1: ValidateProductID 2: 1
MSI (s) (6C:90): Doing action: CostInitialize
1: CostInitialize 2: 1
1: CostInitialize 2: 1
MSI (s) (6C:90): Doing action: Resolve_XXX_DIR
1: Resolve_XXX_DIR 2: 1
MSI (s) (6C:90): Creating MSIHANDLE (615) of type 790542 for thread 1680
1: f0: Function failed, the user might cancel the installation.
1: Resolve_XXX_DIR 2: 3
1: INSTALL 2: 3

Thank you very much for your help

[/B][B][B]

[Stefan Krueger]

I don't know why it's failing, but I guess this line indicates the problem:

1: Script Handler initialization failed, error = 0x0

If the InstallScript handler cannot be initialized, calling your InstallScript CA will always fail.

There was such a problem in ISWI 1.1 but it should be fixed since 1.5. Did you create your project with ISWI 2.03 or did you create it with an earlier version and upgrade it to 2.03?

[noquestion]

Hello Stefan,

thank you.

No.. I created it with ISWI 2.03. And the "funny" thing is, I did some tests and had to realize that all script actions fail if I run the setup without UI. :-( Like you mentioned.
Maybe it is because the handles to the MSI are represented by "real" WindowHandles ? But if so...that would be a general problem of ISWI, and no silent installation using installscript would ever work.
The only thing that could cause trouble on my side is, that my 2000 somehow catched the MSI 2.0, but the ISWI2.03  uses 1.5

Any ideas ?

Thank you

[Stefan Krueger]

ISWI 2.03 uses MSI 1.2.
MSI 1.5 never was released, it is just a beta version that is known to be buggy. The release version was then called MSI 2.0.
If you have MSI 1.5 on your build machine, replace it with a released version (1.1., 1.2 or 2.0). MSI 1.5 on build machines is known to cause all sorts of damages to the built packages.

[noquestion]

Sorry, you are right Stefan it uses 1.2 not 1.5...