[wix-users] Wix setup can´t start custom action

John Cooper JoCooper at jackhenry.com
Thu Mar 17 06:45:33 PDT 2016

A 1603 is a fatal error exit.  This usually means you are throwing an exception.

John Merryweather Cooper
Senior Software Engineer | Integration Development Group | Enterprise Notification Service
Jack Henry & Associates, Inc.® | Lenexa, KS  66214 | Ext:  431050 |JoCooper at jackhenry.com

-----Original Message-----
From: wix-users [mailto:wix-users-bounces at lists.wixtoolset.org] On Behalf Of Andreas Buchner
Sent: Thursday, March 17, 2016 8:33 AM
To: WiX Toolset Users Mailing List <wix-users at lists.wixtoolset.org>
Subject: [wix-users] Wix setup can´t start custom action

The e-mail below is from an external source.  Please do not open attachments or click links from an unknown or suspicious origin.

Hello everyone,

I have one customer who faces the following issue on only one of his clients:

Our setup is executing a custom action before InstallFinalize which is defined like the following:
      Return="check" />

The setup fails while it tries to execute the custom action. In the MSI-Log we see the following:

MSI (s) (50:78) [11:08:54:135]: Generating random cookie.
MSI (s) (50:78) [11:08:54:140]: Created Custom Action Server with PID 5500 (0x157C).
MSI (s) (50:1C) [11:08:54:196]: Running as a service.
MSI (s) (50:1C) [11:08:54:198]: Hello, I'm your 32bit Impersonated custom action server.
SFXCA: Failed to create new CA process via RUNDLL32. Error code: 216 CustomAction CreateNativeImages returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox) Action ended 11:08:54: InstallFinalize. Return value 3.
MSI (s) (50:54) [11:08:54:528]: User policy value 'DisableRollback' is 0 MSI (s) (50:54) [11:08:54:528]: Machine policy value 'DisableRollback' is 0

Currently we´re using WiX The operating system is Win7 x64 and the setup is compiled in x86.
We already created a test setup which only installs one file and tries to start a custom action which only calls a messagebox and we´re running into the same issue.

Has anyone an idea/suggestion what can cause this?
Thanks in advance!

Andreas Buchner

WiX Toolset Users Mailing List provided by FireGiant http://www.firegiant.com/

NOTICE: This electronic mail message and any files transmitted with it are intended
exclusively for the individual or entity to which it is addressed. The message, 
together with any attachment, may contain confidential and/or privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure or distribution 
is strictly prohibited. If you have received this message in error, please 
immediately advise the sender by reply email and delete all copies.

More information about the wix-users mailing list