Re: [WiX-users] Error LGHT0217 the system was unable to find the specified registry key or value
A service account that is not a local administrator seems to fail to access the
MSI service (which is also required to run validation). Thus, the problem may
not be misconfigured script engines but instead system security.
The workaround is to suppress validation in builds running non-elevated in
service accounts (non-elevated interactive accounts work fine, I haven't yet
tested non-elevated batch accounts [running the build from a scheduled task
instead of from a service]). There was also a suggestion that a too big
environment block may cause this as well.
Blair Murri
Date: Wed, 19 Jun 2013 11:00:38 +0200
From: ca.brenge...@gmail.com
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Error LGHT0217 the system was unable to find the
specified registry key or value
Hi!
Yesterday I setup a WiX project with MSBuild and everything worked fine
when I ran it locally, and I comitted the changes.
However, our nightly build failed with error LGHT0217. And I did read the
FAQ and the linked blog posts on how to fix it.
But the solution, as I understand it, is to modify the registry settings
for the user executing the build job.
And my problem is that I have no means of modifying the registry settings
for the user account that executes the build job, other than via the actual
build job.
I did try instead to execute the registry command operations inside my
build script, but the following commands all failed because the key did not
exist.
reg delete
HKCU\SOFTWARE\Classes\CLSID\{B54F3741-5B07-11CF-A4B0-00AA004A55E8} /f
reg delete
HKCU\SOFTWARE\Classes\Wow6432Node\CLSID\{B54F3741-5B07-11CF-A4B0-00AA004A55E8}
/f
reg delete
HKCU\SOFTWARE\Classes\CLSID\{F414C260-6AC0-11CF-B6D1-00AA0058} /f
reg delete
HKCU\SOFTWARE\Classes\Wow6432Node\CLSID\{F414C260-6AC0-11CF-B6D1-00AA0058}
/f
build 19-Jun-2013 09:59:15 Executing WiXErrorLGHT0217WorkAround
error 19-Jun-2013 09:59:15 ERROR: The system was unable to find the
specified registry key or value.
error 19-Jun-2013 09:59:15 ERROR: The system was unable to find the
specified registry key or value.
error 19-Jun-2013 09:59:15 ERROR: The system was unable to find the
specified registry key or value.
error 19-Jun-2013 09:59:15 ERROR: The system was unable to find the
specified registry key or value.
Or is it possible to disable the validation?
Anyone have any other ideas?
--
This SF.net email is sponsored by Windows:
Build for Windows Store.
http://p.sf.net/sfu/windows-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
This SF.net email is sponsored by Windows:
Build for Windows Store.
http://p.sf.net/sfu/windows-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Error LGHT0217
I am trying to build a very simple WiX project through our TFS 2010 build system. The project uses the default Product.wxs and contains only one component with one file. But I keep getting “error LGHT0217”. The linked WiX FAQ is of no use since I am not using any custom action and certainly not any script custom action. Here is the full error message: 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 the Windows Installer is not correctly installed. Contact your support personnel for assistance.. [C:\Builds\10\BaseI\BeamGageWiX\Sources\BaseI\CodeBase\Installations\BeamGageWiX\Install.BeamGage.Standard.x86.WiX\Install.BeamGage.Standard.x86.WiX.wixproj] I tried searching the windows installer error but none of the answers apply to my situation (windows 7 64-bit) any ideas? -- WhatsUp Gold - Download Free Network Management Software The most intuitive, comprehensive, and cost-effective network management toolset available today. Delivers lowest initial acquisition cost and overall TCO of any competing solution. http://p.sf.net/sfu/whatsupgold-sd ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Error LGHT0217
found this blog post - http://www.wintellect.com/CS/blogs/jrobbins/archive/2009/11/14/wix-projects-vs-tfs-2010-team-build.aspx whatever account is used to run the TFS Build must be a member of the local administrators group in order to the Internal Consistency Evaluators *From:* Kurt Jensen [mailto:kurt.jen...@us.ophiropt.com] *Sent:* Friday, May 06, 2011 7:19 AM *To:* 'wix-users@lists.sourceforge.net' *Subject:* Error LGHT0217 I am trying to build a very simple WiX project through our TFS 2010 build system. The project uses the default Product.wxs and contains only one component with one file. But I keep getting “error LGHT0217”. The linked WiX FAQ is of no use since I am not using any custom action and certainly not any script custom action. Here is the full error message: 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 the Windows Installer is not correctly installed. Contact your support personnel for assistance.. [C:\Builds\10\BaseI\BeamGageWiX\Sources\BaseI\CodeBase\Installations\BeamGageWiX\Install.BeamGage.Standard.x86.WiX\Install.BeamGage.Standard.x86.WiX.wixproj] I tried searching the windows installer error but none of the answers apply to my situation (windows 7 64-bit) any ideas? -- WhatsUp Gold - Download Free Network Management Software The most intuitive, comprehensive, and cost-effective network management toolset available today. Delivers lowest initial acquisition cost and overall TCO of any competing solution. http://p.sf.net/sfu/whatsupgold-sd ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] error LGHT0217 - The Windows Installer Service could not be accessed
We already had a validator extension. I added a semaphore to limit the number of simultaneous validations, and played with the number of concurrent validations we allowed. Only when I moved it to 1 (one) did the errors go away for a couple of weeks now. It appears based on observation that Windows Installer does not support concurrent validations (at least with Windows 2003). I haven't tried it on Windows 2008 to see if there is any difference (our build lab is still using 2003). -Original Message- From: Ian Elliott (Excell Data Corporation) [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 28, 2008 11:14 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] error LGHT0217 - The Windows Installer Service could not be accessed I thought as much but got no response from the Windows Installer team after inquiry. I'm curious to know, however, if any other parties on the Wix alias are experiencing the same issue. -Original Message- From: Rob Mensching [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 28, 2008 11:01 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] error LGHT0217 - The Windows Installer Service could not be accessed If there are issues they are in the Windows Installer since they provide the tool for validation. -Original Message- From: Ian Elliott (Excell Data Corporation) [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 28, 2008 08:49 To: wix-users@lists.sourceforge.net Subject: [WiX-users] error LGHT0217 - The Windows Installer Service could not be accessed Hi, We've recently seen the following error sometimes in builds. When we retry the build leg, the error disappears. We've caught the error on different build machines with different products where 3.0/2.0 wix are used. Product with 3.0 wix: 1errors in directory e:\sdaws\main\product\installer\productwebsite 1e:\sdaws\main\product\installer\productwebsite\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.. 1e:\sdaws\main\product\installer\productwebsite\urtrun.pl : error light.exe -ext WixUtilExtension -ext WixIIsExtension -nologo -wx -out e:\sdaws\main.obj.amd64fre\product\installer\productwebsite\objfre\amd64\PRODUCTWebService_x64.msi e:\sdaws\main.obj.amd64fre\product\installer\productwebsite\objfre\amd64\PRODUCTWebSiteInstaller.wixobj = light.exe failed with ExitCode=217 1NMAKE : fatal error U1077: 'e:\SDAWS\MAIN\tools\urtrun.CMD' : return code '0x1' e:\SDAWS\MAIN\tools\x86\nmake.exe /nologo BUILDMSG=Stop. /nologo /f e:\sdaws\main\tools\makefile.def BUILD_PASS=PASS2 LINKONLY=1 NOPASS0=1 MAKEDIR_RELATIVE_TO_BASEDIR=product\installer\productwebsite MAKEDIR_LOWERCASE=e:\sdaws\main\product\installer\productwebsite failed - rc = 2 Product with 2.0 wix: 5e:\panorama\main_dev_igx\product\setup\redists\lclient\internal\light.exe : error LGHT0217 : An unexpected external UI message was received: 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. Searching on web seems to have something related to ICE validation. https://forums.microsoft.com/msdn/ShowPost.aspx?PostID=3588567SiteID=1 Checking Supress ICE validation in the WiX project settings solved my issues. light.exe : error LGHT0217: An unexpected external UI message was received: 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. We're wondering if there is a potential conflict of running multiple Light.exe on multi-proc machines. Our build machines are OS 2003, 4-8 CPUs. Thanks. - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.Net email is sponsored by the Moblin Your Move Developer's
[WiX-users] error LGHT0217 - The Windows Installer Service could not be accessed
Hi, We've recently seen the following error sometimes in builds. When we retry the build leg, the error disappears. We've caught the error on different build machines with different products where 3.0/2.0 wix are used. Product with 3.0 wix: 1errors in directory e:\sdaws\main\product\installer\productwebsite 1e:\sdaws\main\product\installer\productwebsite\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.. 1e:\sdaws\main\product\installer\productwebsite\urtrun.pl : error light.exe -ext WixUtilExtension -ext WixIIsExtension -nologo -wx -out e:\sdaws\main.obj.amd64fre\product\installer\productwebsite\objfre\amd64\PRODUCTWebService_x64.msi e:\sdaws\main.obj.amd64fre\product\installer\productwebsite\objfre\amd64\PRODUCTWebSiteInstaller.wixobj = light.exe failed with ExitCode=217 1NMAKE : fatal error U1077: 'e:\SDAWS\MAIN\tools\urtrun.CMD' : return code '0x1' e:\SDAWS\MAIN\tools\x86\nmake.exe /nologo BUILDMSG=Stop. /nologo /f e:\sdaws\main\tools\makefile.def BUILD_PASS=PASS2 LINKONLY=1 NOPASS0=1 MAKEDIR_RELATIVE_TO_BASEDIR=product\installer\productwebsite MAKEDIR_LOWERCASE=e:\sdaws\main\product\installer\productwebsite failed - rc = 2 Product with 2.0 wix: 5e:\panorama\main_dev_igx\product\setup\redists\lclient\internal\light.exe : error LGHT0217 : An unexpected external UI message was received: 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. Searching on web seems to have something related to ICE validation. https://forums.microsoft.com/msdn/ShowPost.aspx?PostID=3588567SiteID=1 Checking Supress ICE validation in the WiX project settings solved my issues. light.exe : error LGHT0217: An unexpected external UI message was received: 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. We're wondering if there is a potential conflict of running multiple Light.exe on multi-proc machines. Our build machines are OS 2003, 4-8 CPUs. Thanks. - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] error LGHT0217 - The Windows Installer Service could not be accessed
If there are issues they are in the Windows Installer since they provide the tool for validation. -Original Message- From: Ian Elliott (Excell Data Corporation) [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 28, 2008 08:49 To: wix-users@lists.sourceforge.net Subject: [WiX-users] error LGHT0217 - The Windows Installer Service could not be accessed Hi, We've recently seen the following error sometimes in builds. When we retry the build leg, the error disappears. We've caught the error on different build machines with different products where 3.0/2.0 wix are used. Product with 3.0 wix: 1errors in directory e:\sdaws\main\product\installer\productwebsite 1e:\sdaws\main\product\installer\productwebsite\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.. 1e:\sdaws\main\product\installer\productwebsite\urtrun.pl : error light.exe -ext WixUtilExtension -ext WixIIsExtension -nologo -wx -out e:\sdaws\main.obj.amd64fre\product\installer\productwebsite\objfre\amd64\PRODUCTWebService_x64.msi e:\sdaws\main.obj.amd64fre\product\installer\productwebsite\objfre\amd64\PRODUCTWebSiteInstaller.wixobj = light.exe failed with ExitCode=217 1NMAKE : fatal error U1077: 'e:\SDAWS\MAIN\tools\urtrun.CMD' : return code '0x1' e:\SDAWS\MAIN\tools\x86\nmake.exe /nologo BUILDMSG=Stop. /nologo /f e:\sdaws\main\tools\makefile.def BUILD_PASS=PASS2 LINKONLY=1 NOPASS0=1 MAKEDIR_RELATIVE_TO_BASEDIR=product\installer\productwebsite MAKEDIR_LOWERCASE=e:\sdaws\main\product\installer\productwebsite failed - rc = 2 Product with 2.0 wix: 5e:\panorama\main_dev_igx\product\setup\redists\lclient\internal\light.exe : error LGHT0217 : An unexpected external UI message was received: 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. Searching on web seems to have something related to ICE validation. https://forums.microsoft.com/msdn/ShowPost.aspx?PostID=3588567SiteID=1 Checking Supress ICE validation in the WiX project settings solved my issues. light.exe : error LGHT0217: An unexpected external UI message was received: 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. We're wondering if there is a potential conflict of running multiple Light.exe on multi-proc machines. Our build machines are OS 2003, 4-8 CPUs. Thanks. - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] error LGHT0217 - The Windows Installer Service could not be accessed
I thought as much but got no response from the Windows Installer team after inquiry. I'm curious to know, however, if any other parties on the Wix alias are experiencing the same issue. -Original Message- From: Rob Mensching [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 28, 2008 11:01 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] error LGHT0217 - The Windows Installer Service could not be accessed If there are issues they are in the Windows Installer since they provide the tool for validation. -Original Message- From: Ian Elliott (Excell Data Corporation) [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 28, 2008 08:49 To: wix-users@lists.sourceforge.net Subject: [WiX-users] error LGHT0217 - The Windows Installer Service could not be accessed Hi, We've recently seen the following error sometimes in builds. When we retry the build leg, the error disappears. We've caught the error on different build machines with different products where 3.0/2.0 wix are used. Product with 3.0 wix: 1errors in directory e:\sdaws\main\product\installer\productwebsite 1e:\sdaws\main\product\installer\productwebsite\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.. 1e:\sdaws\main\product\installer\productwebsite\urtrun.pl : error light.exe -ext WixUtilExtension -ext WixIIsExtension -nologo -wx -out e:\sdaws\main.obj.amd64fre\product\installer\productwebsite\objfre\amd64\PRODUCTWebService_x64.msi e:\sdaws\main.obj.amd64fre\product\installer\productwebsite\objfre\amd64\PRODUCTWebSiteInstaller.wixobj = light.exe failed with ExitCode=217 1NMAKE : fatal error U1077: 'e:\SDAWS\MAIN\tools\urtrun.CMD' : return code '0x1' e:\SDAWS\MAIN\tools\x86\nmake.exe /nologo BUILDMSG=Stop. /nologo /f e:\sdaws\main\tools\makefile.def BUILD_PASS=PASS2 LINKONLY=1 NOPASS0=1 MAKEDIR_RELATIVE_TO_BASEDIR=product\installer\productwebsite MAKEDIR_LOWERCASE=e:\sdaws\main\product\installer\productwebsite failed - rc = 2 Product with 2.0 wix: 5e:\panorama\main_dev_igx\product\setup\redists\lclient\internal\light.exe : error LGHT0217 : An unexpected external UI message was received: 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. Searching on web seems to have something related to ICE validation. https://forums.microsoft.com/msdn/ShowPost.aspx?PostID=3588567SiteID=1 Checking Supress ICE validation in the WiX project settings solved my issues. light.exe : error LGHT0217: An unexpected external UI message was received: 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. We're wondering if there is a potential conflict of running multiple Light.exe on multi-proc machines. Our build machines are OS 2003, 4-8 CPUs. Thanks. - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url
Re: [WiX-users] error LGHT0217
I'm using Wix 3. The problem was some DCOM permissions. I have added ccnet to the DCOM local user group in windows server 2003 SP1 and it works. Thanks for your help. On 3/7/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: I assume you're using Wix 3? If not, I can at least confirm that Wix 2 can be used under CCNet (we use it). You might want to check and see if any anti-virus software is getting in your way. Regards, Richard - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] error LGHT0217
Hi, I'm trying to build an msi with wix from cruise control which run as a service I receive the following error message: error LGHT0217: An unexpected external UI message was received: The Windows Installer Service could not be accessed This occurs in the validation phase of the process. If I run light with -sval, the error disappear. The problem is I don't want to do the validation manually, I want the process to be automated with cruise control. The only clue I have been able to find (by using process monitor) is a sharing violation on the msi in the temp directory of the account ccnet which cruise control run under. If I build from the command line with the ccnet account, everything runs fine. Thanks for you help. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] error LGHT0217
I assume you're using Wix 3? If not, I can at least confirm that Wix 2 can be used under CCNet (we use it). You might want to check and see if any anti-virus software is getting in your way. Regards, Richard From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of JF Lavigne Sent: Wednesday, March 07, 2007 10:45 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] error LGHT0217 Hi, I'm trying to build an msi with wix from cruise control which run as a service I receive the following error message: error LGHT0217: An unexpected external UI message was received: The Windows Installer Service could not be accessed This occurs in the validation phase of the process. If I run light with -sval, the error disappear. The problem is I don't want to do the validation manually, I want the process to be automated with cruise control. The only clue I have been able to find (by using process monitor) is a sharing violation on the msi in the temp directory of the account ccnet which cruise control run under. If I build from the command line with the ccnet account, everything runs fine. Thanks for you help. * C O N F I D E N T I A L I T Y N O T I C E * --- The content of this e-mail is intended solely for the use of the individual or entity to whom it is addressed. If you have received this communication in error, be aware that forwarding it, copying it, or in any way disclosing its content to any other person, is strictly prohibited. Peek Traffic Corporation is neither liable for the contents, nor for the proper, complete and timely transmission of (the information contained in) this communication. If you have received this communication in error, please notify the author by replying to this e-mail immediately and delete the material from any computer. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
