Well, it probably isn't that then. Another bad stab, your Team Build doens't start inside a build environment does it? By default I believe they don't. The error message is puzzling because it seems to be saying that it just can't find msiexec. Windows Installer GP Info. http://technet2.microsoft.com/windowsserver/en/library/dd40e9f9-14e1-4f55-bd6e-eaab331b84361033.mspx?mfr=true
-- Brian Rogers "Intelligence removes complexity." - Me http://www.codeplex.com/wixml/ On Mon, Jun 30, 2008 at 9:26 AM, John Nannenga <[EMAIL PROTECTED]> wrote: > The Team Build Service account is in the administrators group of the > machine. I'm not sure how to explicitly verify that it has permissions to > run MSIs… > > > > > > *From:* Brian Rogers [mailto:[EMAIL PROTECTED] > *Sent:* Monday, June 30, 2008 11:20 AM > *To:* General discussion for Windows Installer XML toolset. > *Cc:* John Nannenga > > *Subject:* Re: [WiX-users] LGHT0217 & VSTS > > > > Hey John, > > > > Sorry to leave you hanging on Friday. I know you mentioned that UAC has > been turned off on the machine, but does the service account running the > build have Admin. rights (...stabbing in the dark here...)? Is it allowed to > run MSIs? I haven't worked with Team Build at this point so I am not sure > where else to look off the top of my head. > > > > Thanks, > > > > -- > Brian Rogers > "Intelligence removes complexity." - Me > http://www.codeplex.com/wixml/ > > On Mon, Jun 30, 2008 at 7:21 AM, John Nannenga < > [EMAIL PROTECTED]> wrote: > > Just following up...anyone have any thoughts? > > Are there other users out there that are using VSTF, Team Build, and WiX v3 > ? > > > > -----Original Message----- > From: John Nannenga > Sent: Friday, June 27, 2008 12:41 PM > To: General discussion for Windows Installer XML toolset. > > Subject: RE: [WiX-users] LGHT0217 & VSTS > > I received the following error reported on build 3.0.4214.0 (I think it is > the same issue, except this build of WiX didn't report all the individual > ICE action failures) > > Task "Light" > Command: > C:\Program Files\Windows Installer XML v3\bin\Light.exe -sw1076 -loc > ..\..\..\Strings\Common_ENG.wxl -loc Ddapi.wxl -out > "C:\Users\fgoinsbs\AppData\Local\Temp\MBS Install\Dex v11.0\Binaries\Mixed > Platforms\Release\Microsoft_Dexterity11_VC80_DDAPI_x64.msm" -pdbout > "C:\Users\fgoinsbs\AppData\Local\Temp\MBS Install\Dex v11.0\Binaries\Mixed > Platforms\Release\Microsoft_Dexterity11_VC80_DDAPI_x64.wixpdb" > obj\x64\Release\DdapiMergeModule.wixobj > > Microsoft (R) Windows Installer Xml Linker version 3.0.4214.0 > > Copyright (C) Microsoft Corporation. All rights reserved. > > light.exe : error LGHT0217: An unexpected external UI message was received: > 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. > The command exited with code 217. > > > > -----Original Message----- > From: [EMAIL PROTECTED] [mailto: > [EMAIL PROTECTED] On Behalf Of Brian Rogers > Sent: Friday, June 27, 2008 12:25 PM > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] LGHT0217 & VSTS > > Hey John, > > Out of curiosity, do you get similar errors on a previous build? I am > curious to see if this is native to the new change or this is going to fail > in the past as well. > > Thanks, > > -- > Brian Rogers > "Intelligence removes complexity." - Me > http://www.codeplex.com/wixml/ > > On Fri, Jun 27, 2008 at 10:12 AM, John Nannenga < > [EMAIL PROTECTED]> > wrote: > > > If I run a build through the VS IDE on the build machine, everything > works > > like a champ. When I run the build through Visual Studio Team Suite, > Team > > Build, I get the below errors... > > > > I followed the link and information in the URL listed in the error > message, > > everything checks out. [But I'm also not getting the error 2738 that > folks > > are referencing]. > > > > Any thoughts on how I can resolve this (aside from disabling > validations)? > > [Incidentally, the domain account used for the build service is part of > the > > administrators group on the build machine. The build machine is Windows > > 2008 Server, with UAC turned off] > > > > > > Task "Light" > > Command: > > C:\Program Files\Windows Installer XML v3\bin\Light.exe -sw1076 -loc > > ..\..\..\Strings\Common_ENG.wxl -loc Ddapi.wxl -out > > "C:\Users\fgoinsbs\AppData\Local\Temp\MBS Install\Dex > v11.0\Binaries\Mixed > > Platforms\Release\Microsoft_Dexterity11_VC80_DDAPI_x64.msm" -pdbout > > "C:\Users\fgoinsbs\AppData\Local\Temp\MBS Install\Dex > v11.0\Binaries\Mixed > > Platforms\Release\Microsoft_Dexterity11_VC80_DDAPI_x64.wixpdb" > > obj\x64\Release\DdapiMergeModule.wixobj > > Microsoft (R) Windows Installer Xml Linker version 3.0.4227.0 > > Copyright (C) Microsoft Corporation. All rights reserved. > > > > light.exe : error LGHT0217: Error executing ICE action 'ICEM01'. 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 : error LGHT0217: Error executing ICE action 'ICEM02'. 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 : error LGHT0217: Error executing ICE action 'ICEM03'. 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 : error LGHT0217: Error executing ICE action 'ICEM04'. 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 : error LGHT0217: Error executing ICE action 'ICEM05'. 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 : error LGHT0217: Error executing ICE action 'ICEM06'. 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 : error LGHT0217: Error executing ICE action 'ICEM07'. 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 : error LGHT0217: Error executing ICE action 'ICEM08'. 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 : error LGHT0217: Error executing ICE action 'ICEM09'. 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 : error LGHT0217: Error executing ICE action 'ICEM10'. 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 : error LGHT0217: Error executing ICE action 'ICEM11'. 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 : error LGHT0217: Error executing ICE action 'ICEM12'. 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 : error LGHT0217: Error executing ICE action 'ICEM13'. 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 : error LGHT0217: Error executing ICE action 'ICEM14'. 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 : 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 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 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 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 > > The command exited with code 216. > > Done executing task "Light" -- FAILED. > > > > ------------------------------------------------------------------------- > ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
