Could you send the lines from the log starting from
InstallWindowsFeaturesDeferred returning to the second mention of "rollback"
following the above line? Also, which version of MSI?

-----Original Message-----
From: Lian Jiang [mailto:lji...@microsoft.com] 
Sent: Monday, September 21, 2009 5:16 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Return='ignore' causes "ICE68: invalid custom
action type for action"

Thanks Blair for your explanation.

I tried:
<CustomAction Id="InstallWindowsFeatures"
                  Property="InstallWindowsFeaturesDeferred"
                  Value='"[WindowsFolder]Sysnative\dism.exe" /online ......'
                  Execute='immediate'/>
    <CustomAction Id="InstallWindowsFeaturesDeferred"
                  BinaryKey='WixCA'
                  DllEntry="CAQuietExec64"
                  Execute="deferred"
                  Return='ignore'
                  Impersonate="no" />


As you see, I removed "Return='ignore'" from InstallWidnowsFeatures and set
Return='ignore' in InstallWindowsFeaturesDeferred.

The compile can pass without ICE68 error but running msi failed because the
return value is not 0 (shown in the log).

Yes, I allow installation continue even this custom action failed.

Do I still miss anything?


Thanks
Lian


-----Original Message-----
From: Blair [mailto:os...@live.com] 
Sent: Monday, September 21, 2009 4:46 PM
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] Return='ignore' causes "ICE68: invalid custom
action type for action"

A so-called SetProperty "custom" action is a built-in type (it is a Type 51
custom action), and setting a session property value isn't ever expected to
fail. Why do you want to set Return='ignore'? And what would you do in your
deferred action if the immediate SetProperty ever did fail?

Because you add the msidbCustomActionTypeContinue flag to your type 51
action, Windows Installer sees a type 115, and I assume it doesn't have any
codepath that supports a Type 115, which is why you get the ICE68 (to
prevent you from attempting it) and an "unsupported type" when you attempt
it anyway.

The one you may wish to ignore (if you don't wish to depend on it returning
a 0 result code) would be your deferred InstallWindowsFeaturesDeferred
action. That is the one that actually runs your dism.exe utility.

-----Original Message-----
From: Lian Jiang [mailto:lji...@microsoft.com] 
Sent: Monday, September 21, 2009 4:27 PM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Return='ignore' causes "ICE68: invalid custom action
type for action"

Hi,

I have a custom action:

<CustomAction Id="InstallWindowsFeatures"
                  Property="InstallWindowsFeaturesDeferred"
                  Value='"[WindowsFolder]Sysnative\dism.exe" /online
/NoRestart /enable-feature /featurename:NetFx3
/featurename:Xps-Foundation-Xps-Viewer /featurename:InkSupport
/featurename:DesktopExperience /featurename:SearchEngine-Server-Package
/featurename:Indexing-Service-Package'
                  Execute='immediate'
                  Return='ignore'/>
    <CustomAction Id="InstallWindowsFeaturesDeferred"
                  BinaryKey='WixCA'
                  DllEntry="CAQuietExec64"
                  Execute="deferred"
                  Return='check'
                  Impersonate="no" />


When I compile, it failed due to ICE68 - Invalid custom action type for
action 'InstallWindowsFeatures'.

If I bypass ICE68 when linking, running the msi will fail with "Custom
action InstallWindowsFeatures specifies unsupported type".

The trick is that if I change the highlighted 'ignore'Johto 'check', then
compile will pass without bypassing ICE68.

Does anybody know why I cannot use Return='ignore'?

Appreciate very much!


Thanks
Lian




----------------------------------------------------------------------------
--
Come build with us! The BlackBerry&reg; Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9&#45;12, 2009. Register now&#33;
http://p.sf.net/sfu/devconf
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


----------------------------------------------------------------------------
--
Come build with us! The BlackBerry&reg; Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9&#45;12, 2009. Register now&#33;
http://p.sf.net/sfu/devconf
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


----------------------------------------------------------------------------
--
Come build with us! The BlackBerry&reg; Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9&#45;12, 2009. Register now&#33;
http://p.sf.net/sfu/devconf
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


------------------------------------------------------------------------------
Come build with us! The BlackBerry&reg; Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9&#45;12, 2009. Register now&#33;
http://p.sf.net/sfu/devconf
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Reply via email to