There is a typo in my email. In my actually testing code, there is no extra
space around TestDeferred. Sorry for confusion.
Let me post the code segment again:
<CustomAction Id="Test"
Property="TestDeferred"
Value='"c:\windows\syswow64\WindowsPowerShell\v1.0\powershell.exe -NoLogo
-NoProfile -NonInteractive get-help"'
Execute='immediate'
Return='check'/>
<CustomAction Id="TestDeferred"
BinaryKey='WixCA'
DllEntry="CAQuietExec"
Execute="deferred"
Return="check"
Impersonate="no" />
Thanks for pointing out any error in this code.
Lian
-----Original Message-----
From: Blair [mailto:os...@live.com]
Sent: Sunday, August 23, 2009 1:17 AM
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] cannot make powershell custom action work on 64-bit
windows 2008 R2
I'm hoping that the extra spaces in the TestDeferred custom action
declaration's Id attribute are an artifact of either your or my email client
and not what you have in code.
-----Original Message-----
From: Lian Jiang [mailto:lji...@microsoft.com]
Sent: Saturday, August 22, 2009 12:23 PM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] cannot make powershell custom action work on 64-bit
windows 2008 R2
Hi,
I have a custom action where CAQuietExec calls a powershell command.
<CustomAction Id="Test"
Property="TestDeferred"
Value='"c:\windows\syswow64\WindowsPowerShell\v1.0\powershell.exe -NoLogo
-NoProfile -NonInteractive get-help"'
Execute='immediate'
Return='check'/>
<CustomAction Id=" TestDeferred "
BinaryKey='WixCA'
DllEntry="CAQuietExec"
Execute="deferred"
Return="check"
Impersonate="no" />
For testing purpose, I just hardcoded the powershell.exe path. I also tried
C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe but it gives the
same error:
MSI (s) (30:6C) [12:12:08:458]: Invoking remote custom action. DLL:
C:\Windows\Installer\MSIB570.tmp, Entrypoint: CAQuietExec
CAQuietExec: Error 0x80070002: Command failed to execute.
CAQuietExec: Error 0x80070002: CAQuietExec Failed
CustomAction InstallWindowsFeaturesDeferred returned actual error code 1603
(note this may not be 100% accurate if translation happened inside sandbox)
My system is windows 2008 R2 64bit, Wix is 3.5.0529.0 and windows installer
is 4.5. According to Rob
(http://www.mail-archive.com/wix-users@lists.sourceforge.net/msg16838.html),
this problem should have been fixed.
Am I doing anything wrong?
Thanks
Lian
----------------------------------------------------------------------------
--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus
on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
