Looks like your custom action is no longer returning ERROR_SUCCESS.
CustomAction UpdateConfig returned actual error code -2146232576
That or maybe the custom action is crashing and Windows Installer is just
letting you know. You might try MsiBreak to debug.
On Fri, May 25, 2012 at 11:57 AM, Justin Kabonick <kabonick...@gmail.com>wrote:
> Last year I wrote an installer to install a Windows service. Part of that
> install includes a custom action which calls the executable which is
> installed and passes in some command line parameters so that a
> configuration file is updated.
>
> However, the custom action started failing. I get the following in the log.
>
> MSI (s) (F0:80) [14:44:08:231]: Executing op:
> ActionStart(Name=UpdateConfig,,)
> MSI (s) (F0:80) [14:44:08:231]: Executing op:
>
> CustomActionSchedule(Action=UpdateConfig,ActionType=1042,Source=C:\FolderPath\MyService.exe,Target=/updateconfig
> C:\FolderPath,)
> CustomAction UpdateConfig returned actual error code -2146232576 (note
> this
> may not be 100% accurate if translation happened inside sandbox)
> MSI (s) (F0:80) [14:44:08:262]: Note: 1: 1722 2: UpdateConfig 3: C:\
> FolderPath\MyService.exe 4: /updateconfig C:\FolderPath
> MSI (c) (F4:50) [14:44:08:262]: Font created. Charset: Req=0, Ret=0, Font:
> Req=MS Shell Dlg, Ret=MS Shell Dlg
>
> Error 1722. There is a problem with this Windows Installer package. A
> program run as part of the setup did not finish as expected. Contact your
> support personnel or package vendor. Action UpdateConfig, location:
> C:\FolderPath\MyService.exe, command: /updateconfig C:\FolderPath
> MSI (s) (F0:80) [14:44:09:338]: Product: My Windows Service -- Error 1722.
> There is a problem with this Windows Installer package. A program run as
> part of the setup did not finish as expected. Contact your support
> personnel or package vendor. Action UpdateConfig, location:
> C:\FoldePath\MyService.exe, command: /updateconfig C:\FoldePath
>
>
> That error code doesn't seem to mean anything and it appears to be a
> garbage value. But I can't seem to find any reason for the action to fail.
> It works fine if I run it outside of the installer. I know that the
> executable uses some .Net reflection to find the configuration file and
> there was an earlier issue because the current working directory was
> C:\System32 since it was started by msiexec. However that was fixed.
>
> Is there any way to track down why this action would start failing
> suddenly?
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
--
virtually, Rob Mensching - http://RobMensching.com LLC
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
