I get the following from msiexec with verbose logging. What fails to contact the server? Is it light or MSIExec?
=== Verbose logging started: 2/10/2009 10:47:07 Build type: SHIP UNICODE 4.05.6001.00 Calling process: c:\hudson\jobs\CAB Settings\workspace\.repository\com\microsoft\wix\wix\3.0.4318.0\unpacked \light.exe === MSI (c) (44:30) [10:47:07:092]: Engine created on writable database - enabling validation mode. MSI (c) (44:30) [10:47:07:092]: SOFTWARE RESTRICTION POLICY: Verifying package --> 'C:\Documents and Settings\hudson\Local Settings\Temp\gw2mk_vi\settings-1.0.1-SNAPSHOT.msi' against software restriction policy MSI (c) (44:30) [10:47:07:092]: Note: 1: 2262 2: DigitalSignature 3: -2147287038 MSI (c) (44:30) [10:47:07:092]: SOFTWARE RESTRICTION POLICY: C:\Documents and Settings\hudson\Local Settings\Temp\gw2mk_vi\settings-1.0.1-SNAPSHOT.msi is not digitally signed MSI (c) (44:30) [10:47:07:092]: SOFTWARE RESTRICTION POLICY: C:\Documents and Settings\hudson\Local Settings\Temp\gw2mk_vi\settings-1.0.1-SNAPSHOT.msi is permitted to run at the 'unrestricted' authorization level. MSI (c) (44:30) [10:47:07:155]: Failed to connect to server. Error: 0x80070005 > -----Original Message----- > From: Nord, James [mailto:jn...@nds.com] > Sent: 09 February 2009 18:29 > To: us...@hudson.dev.java.net > Cc: wix-users@lists.sourceforge.net > Subject: RE: Re: ICE Errors in CI environment > > When running hudson directly from the command prompt the > build succeeds. > > I then added the user to the Administrators group and > re-tried the build using the service and the build suceeded. > I removed the Administrators group and the build then failed. > > Obviously from the run with least privilledges does anyone > know what privs the user needs? > "Enable Interaction with Desktop" is only available when the > service is running under the System account. > > Regards, > > /James > > > -----Original Message----- > > From: Bob Arnson [mailto:b...@joyofsetup.com] > > Sent: 09 February 2009 17:58 > > To: General discussion for Windows Installer XML toolset. > > Subject: Re: [WiX-users] ICE Errors in CI environment > > > > Later versions of WiX have an explicit warning message for > this case. > > As I recall, service accounts need to have the "Allow Service to > > Interact With Desktop" setting turned on. > > > > From: Kohsuke Kawaguchi [mailto:kohsuke.kawagu...@sun.com] > > Sent: 09 February 2009 18:00 > > To: us...@hudson.dev.java.net > > Cc: wix-users@lists.sourceforge.net > > Subject: Re: ICE Errors in CI environment > > > > > > I'd first use Process Explorer or something to really double-check > > what user account Hudson is running. If it's really the > same user and > > you can do this from a GUI login, I'd then suspect perhaps > the ability > > to interact with the desktop might have something to do with this. > > > > To verify that hypothesis, you can temporarily run Hudson > from within > > your interactive login session. > > > > > > Nord, James wrote: > > > Hi all, > > > > > > (Wix 3.0.4318.0, CI is Hudson 1.279 running in Apache > > Tomcat 6.0.16 on > > > Java 1.6.0 update6) > > > > > > I'm having an issue that I can't work out. > > > > > > I get the following errors from the WIX toolset when > > running in the CI > > > environment: > > > Microsoft (R) Windows Installer Xml Linker version 3.0.4318.0 > > > Copyright (C) Microsoft Corporation. All rights reserved. > > > light.exe : error LGHT0217 : Error executing ICE action > 'ICE01'. The > > > most common cause of this kind of ICE failure is an incorrectly > > > registered scripting engine. See > > > http://wix.sourceforge.net/faq.html#Error217 for details > and how to > > > solve this problem. The following string format was not > > expected by the > > > external UI message logger: "The Windows Installer Service > > could not be > > > accessed. This can occur if you are running Windows in safe > > mode, or if > > > the Windows Installer is not correctly installed. Contact > > your support > > > personnel for assistance.". > > > light.exe : error LGHT0217 : Error executing ICE action > 'ICE02'. The > > > most common cause of this kind of ICE failure is an incorrectly > > > registered scripting engine. See > > > http://wix.sourceforge.net/faq.html#Error217 for details > and how to > > > solve this problem. The following string format was not > > expected by the > > > external UI message logger: "The Windows Installer Service > > could not be > > > accessed. This can occur if you are running Windows in safe > > mode, or if > > > the Windows Installer is not correctly installed. Contact > > your support > > > personnel for assistance.". > > > light.exe : error LGHT0217 : Error executing ICE action > 'ICE03'. The > > > most common cause of this kind of ICE failure is an incorrectly > > > registered scripting engine. See > > > http://wix.sourceforge.net/faq.html#Error217 for details > and how to > > > solve this problem. The following string format was not > > expected by the > > > external UI message logger: "The Windows Installer Service > > could not be > > > accessed. This can occur if you are running Windows in safe > > mode, or if > > > the Windows Installer is not correctly installed. Contact > > your support > > > personnel for assistance.". > > > light.exe : error LGHT0217 : Error executing ICE action > 'ICE04'. The > > > most common cause of this kind of ICE failure is an incorrectly > > > registered scripting engine. See > > > http://wix.sourceforge.net/faq.html#Error217 for details > and how to > > > solve this problem. The following string format was not > > expected by the > > > external UI message logger: "The Windows Installer Service > > could not be > > > accessed. This can occur if you are running Windows in safe > > mode, or if > > > the Windows Installer is not correctly installed. Contact > > your support > > > personnel for assistance.". > > > light.exe : error LGHT0217 : Error executing ICE action > 'ICE05'. The > > > most common cause of this kind of ICE failure is an incorrectly > > > registered scripting engine. See > > > http://wix.sourceforge.net/faq.html#Error217 for details > and how to > > > solve this problem. The following string format was not > > expected by the > > > external UI message logger: "The Windows Installer Service > > could not be > > > accessed. This can occur if you are running Windows in safe > > mode, or if > > > the Windows Installer is not correctly installed. Contact > > your support > > > personnel for assistance.". > > > light.exe : error LGHT0217 : Error executing ICE action > 'ICE06'. The > > > most common cause of this kind of ICE failure is an incorrectly > > > registered scripting engine. See > > > http://wix.sourceforge.net/faq.html#Error217 for details > and how to > > > solve this problem. The following string format was not > > expected by the > > > external UI message logger: "The Windows Installer Service > > could not be > > > accessed. This can occur if you are running Windows in safe > > mode, or if > > > the Windows Installer is not correctly installed. Contact > > your support > > > personnel for assistance.". > > > light.exe : error LGHT0217 : Error executing ICE action > 'ICE07'. The > > > most common cause of this kind of ICE failure is an incorrectly > > > registered scripting engine. See > > > http://wix.sourceforge.net/faq.html#Error217 for details > and how to > > > solve this problem. The following string format was not > > expected by the > > > external UI message logger: "The Windows Installer Service > > could not be > > > accessed. This can occur if you are running Windows in safe > > mode, or if > > > the Windows Installer is not correctly installed. Contact > > your support > > > personnel for assistance.". > > > light.exe : error LGHT0216 : An unexpected Win32 exception > > with error > > > code 0x643 occurred: Action - 'ICE08' Fatal error during > > installation > > > > > > If I login to the box (XP) as the same user that the CI > > service is set > > > to run as and run exactly the same command then everything > > is ok -the > > > build completes with no errors. > > > I've checked HKCU for any scripting keys but I couldn't see > > any - and it > > > wouldn't explain why it works from the command line and > not the CI > > > environment. > > > Anyone any ideas? > > > /James > > > > > > > > > > > > > > > > > > -- > > Kohsuke Kawaguchi > > Sun Microsystems > > http://weblogs.java.net/blog/kohsuke/ > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@hudson.dev.java.net > For additional commands, e-mail: users-h...@hudson.dev.java.net > > ************************************************************************************** This e-mail is confidential, the property of NDS Ltd and intended for the addressee only. Any dissemination, copying or distribution of this message or any attachments by anyone other than the intended recipient is strictly prohibited. If you have received this message in error, please immediately notify the postmas...@nds.com and destroy the original message. Messages sent to and from NDS may be monitored. NDS cannot guarantee any message delivery method is secure or error-free. Information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. We do not accept responsibility for any errors or omissions in this message and/or attachment that arise as a result of transmission. You should carry out your own virus checks before opening any attachment. Any views or opinions presented are solely those of the author and do not necessarily represent those of NDS. To protect the environment please do not print this e-mail unless necessary. NDS Limited Registered office: One Heathrow Boulevard, 286 Bath Road, West Drayton, Middlesex, UB7 0DQ, United Kingdom. A company registered in England and Wales Registered no. 3080780 VAT no. GB 603 8808 40-00 ************************************************************************************** ------------------------------------------------------------------------------ Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM) software. With Adobe AIR, Ajax developers can use existing skills and code to build responsive, highly engaging applications that combine the power of local resources and data with the reach of the web. Download the Adobe AIR SDK and Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
