it fails on a custom action, you need to open the msi to see what it does. For example, if customaction is a script requireing access to $host or other interactive environment it's gonna fail since you don't have that. Not much we can do about that I'm afraid :-(
On Thursday, June 9, 2016 at 3:42:30 PM UTC+2, Justin Dugan wrote: > > I looked at the log generated by the installer; however, it doesn't help > me at all. Maybe it will provide some incite for you? Here are the entries > from the failure: > > MSI (s) (DC:58) [14:37:35:944]: Invoking remote custom action. DLL: > C:\Windows\Installer\MSI1FB5.tmp, Entrypoint: InstallExecuteSeq > Action start 14:37:35: InstallExecuteSeq. > SFXCA: Extracting custom action to temporary directory: > C:\Windows\Installer\MSI1FB5.tmp-\ > SFXCA: Binding to CLR version v4.0.30319 > Calling custom action > CustomActions!CompanyNameWix.CustomActions.InstallExecuteSeq > CustomAction InstallExecuteSeq returned actual error code 1603 (note this > may not be 100% accurate if translation happened inside sandbox) > Action ended 14:37:36: InstallExecuteSeq. Return value 3. > Action ended 14:37:36: INSTALL. Return value 3. > > ... *** a bunch of properties listed *** ... > > MSI (s) (DC:FC) [14:37:36:911]: Note: 1: 1708 > MSI (s) (DC:FC) [14:37:36:911]: Note: 1: 2205 2: 3: Error > MSI (s) (DC:FC) [14:37:36:911]: Note: 1: 2228 2: 3: Error 4: SELECT > `Message` FROM `Error` WHERE `Error` = 1708 > MSI (s) (DC:FC) [14:37:36:911]: Note: 1: 2205 2: 3: Error > MSI (s) (DC:FC) [14:37:36:911]: Note: 1: 2228 2: 3: Error 4: SELECT > `Message` FROM `Error` WHERE `Error` = 1709 > MSI (s) (DC:FC) [14:37:36:911]: Product: <product name> -- Installation > failed. > > MSI (s) (DC:FC) [14:37:36:935]: Windows Installer installed the product. > Product Name: <product name>. Product Version: 1.10.97. Product Language: > 1033. Manufacturer: <company>. Installation success or error status: 1603. > > MSI (s) (DC:FC) [14:37:36:937]: Deferring clean up of packages/files, if > any exist > MSI (s) (DC:FC) [14:37:36:937]: MainEngineThread is returning 1603 > MSI (s) (DC:B0) [14:37:36:939]: RESTART MANAGER: Session closed. > MSI (s) (DC:B0) [14:37:36:939]: No System Restore sequence number for this > installation. > === Logging stopped: 6/8/2016 14:37:36 === > MSI (s) (DC:B0) [14:37:36:940]: User policy value 'DisableRollback' is 0 > MSI (s) (DC:B0) [14:37:36:940]: Machine policy value 'DisableRollback' is 0 > MSI (s) (DC:B0) [14:37:36:940]: Incrementing counter to disable shutdown. > Counter after increment: 0 > MSI (s) (DC:B0) [14:37:36:940]: Note: 1: 1402 2: > HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts > > 3: 2 > MSI (s) (DC:B0) [14:37:36:940]: Note: 1: 1402 2: > HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts > > 3: 2 > MSI (s) (DC:B0) [14:37:36:941]: Decrementing counter to disable shutdown. > If counter >= 0, shutdown will be denied. Counter after decrement: -1 > MSI (s) (DC:B0) [14:37:36:941]: Restoring environment variables > MSI (s) (DC:B0) [14:37:36:941]: Destroying RemoteAPI object. > MSI (s) (DC:4C) [14:37:36:941]: Custom Action Manager thread ending. > MSI (c) (14:EC) [14:37:36:942]: Decrementing counter to disable shutdown. > If counter >= 0, shutdown will be denied. Counter after decrement: -1 > MSI (c) (14:EC) [14:37:36:942]: MainEngineThread is returning 1603 > === Verbose logging stopped: 6/8/2016 14:37:36 === > > > I seem to recall when I set up the JBoss Operations Network agent to do > the install, I had to check "Allow service to interact with the desktop" in > the service properties of the agent to get it to work. This is because the > installer still pops up windows even though it's set to be an unattended > install. Is there a general cli option to explicitly tell any installer not > to use the GUI? Or is this something that has to be coded into the > installer explicitly? > -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/3f0258b8-3b80-43e2-b980-2d31298d7fff%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
