I have seen the following article and have added the user into the DCOM group, but there is no change.
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/error-LGHT0217-tp698664p698664.html ------------------------------------------------------- Peter Solomon On Fri, Feb 18, 2011 at 10:57 AM, Peter Solomon <pe...@nextsteps.co.za> wrote: > Hi There, > > I'm wondering if someone else has also experienced the same problem > when using Cruise Control to build there project - see error below > > Everything build fine in VS 2008. > > I've got Wix 3.5.2519.0 installed on Windows Server 2008 R2. > > Would someone be able to point me in the correct direction? > > > light.exe (0,0): > > errorLGHT0217: 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 the Windows Installer > is not correctly installed. Contact your support personnel for > assistance.". > light.exe (0,0): > > errorLGHT0217: 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 the Windows Installer > is not correctly installed. Contact your support personnel for > assistance.". > light.exe (0,0): > > errorLGHT0217: 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 the Windows Installer > is not correctly installed. Contact your support personnel for > assistance.". > light.exe (0,0): > > errorLGHT0217: 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 the Windows Installer > is not correctly installed. Contact your support personnel for > assistance.". > light.exe (0,0): > > errorLGHT0217: 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 the Windows Installer > is not correctly installed. Contact your support personnel for > assistance.". > light.exe (0,0): > > errorLGHT0217: 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 the Windows Installer > is not correctly installed. Contact your support personnel for > assistance.". > light.exe (0,0): > > errorLGHT0217: 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 the Windows Installer > is not correctly installed. Contact your support personnel for > assistance.". > light.exe (0,0): > > errorLGHT0216: An unexpected Win32 exception with > error code 0x643 > occurred: Action - 'ICE08' Fatal error during installation > > ------------------------------------------------------- > Peter Solomon > ------------------------------------------------------------------------------ The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
