Re: [WiX-users] Why do I get ICE failures building from a serviceaccount?

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 454-5900

Thanks for the responses.  I'm not comfortable with giving the build service
account admin privileges.  Maybe if the whole build thing was in a VM I
could do that.  Something to look into.
--
Andrew Arnott
"I [may] not agree with what you have to say, but I'll defend to the death
your right to say it." - S. G. Tallentyre


On Thu, Jan 14, 2010 at 8:41 AM, Blair <os...@li...> wrote:

> For whatever reason on Windows 2008 (I didn't test Vista, XP, 2003, 7, or
> 2008 R2) the MSI Service is only available from logins that either have
> administrative access or are logins that are "interactive". Logins that are
> from service accounts that to not have administrative privileges cannot
> access the msi service and thus cannot run ICE tests.
>
> I had opened an inquiry inside of MSFT last year about this issue but it
> was
> never resolved (I got a lot of "I would have thought, however). I never got
> any other workarounds either.
>
> -----Original Message-----
> From: Pally Sandher [mailto:pal...@ie...]
> Sent: Thursday, January 14, 2010 6:21 AM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Why do I get ICE failures building from a
> serviceaccount?
>
> 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.".
>
> msiexec service needs to be running for ICE's to be evaluated.
>
> Palbinder Sandher
> Software Deployment & IT Administrator
> T: +44 (0) 141 945 8500
> F: +44 (0) 141 945 8501
>
> http://www.iesve.com
> **Design, Simulate + Innovate with the <Virtual Environment>**
> Integrated Environmental Solutions Limited. Registered in Scotland No.
> SC151456
> Registered Office - Helix Building, West Of Scotland Science Park,
> Glasgow G20 0SP
> Email Disclaimer
>
>
> -----Original Message-----
> From: Andrew Arnott [mailto:and...@gm...]
> Sent: 14 January 2010 00:06
> To: wix-users
> Cc: David Christiansen
> Subject: Re: [WiX-users] Why do I get ICE failures building from a
> serviceaccount?
>
>  When I build my WIX project, it succeeds under user account A when I
> log in as that person and build it myself from my Windows desktop.  But
> when that same user account is used from a Windows Service (think
> automated build
> machine) the same build fails with the below errors.
>  I've checked the jscript and vbscript engines, and they are registered
> under HKLM and not HKCU for that user account.  I don't know what else
> to try.  Any ideas?
>
>  Thanks.
>
>
> http://teamcity.dotnetopenauth.net:82/viewLog.html?buildId=892&tab=build
> ResultsDiv&buildTypeId=bt45
>
>  [07:16:41]: Project "build.proj.teamcity.patch.tcprojx" (MSI
> target(s)):
> (11m:19s)
>  [07:27:47]: [Project "build.proj.teamcity.patch.tcprojx" (MSI
> target(s)):] Project "DotNetOpenAuth.Installer.wixproj" (default
> targets): (14s)
>  [07:28:01]: [Project "DotNetOpenAuth.Installer.wixproj" (default
> targets):] 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.".
>  [07:28:01]: [Project "DotNetOpenAuth.Installer.wixproj" (default
> targets):] 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.".
>  [07:28:01]: [Project "DotNetOpenAuth.Installer.wixproj" (default
> targets):] 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.".
>  [07:28:01]: [Project "DotNetOpenAuth.Installer.wixproj" (default
> targets):] 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.".
>  [07:28:01]: [Project "DotNetOpenAuth.Installer.wixproj" (default
> targets):] 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.".
>  [07:28:01]: [Project "DotNetOpenAuth.Installer.wixproj" (default
> targets):] 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.".
>  [07:28:01]: [Project "DotNetOpenAuth.Installer.wixproj" (default
> targets):] 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.".
>  [07:28:01]: [Project "DotNetOpenAuth.Installer.wixproj" (default
> targets):] light.exe error LGHT0216: An unexpected Win32 exception with
> error code
> 0x643 occurred: Action - 'ICE08' Fatal error during installation
>
>  --
>  Andrew Arnott
>  "I [may] not agree with what you have to say, but I'll defend to the
> death your right to say it." - S. G. Tallentyre
> ------------------------------------------------------------------------
> ------
> Throughout its 18-year history, RSA Conference consistently attracts the
> world's best and brightest in the field, creating opportunities for
> Conference attendees to learn about information security's most
> important issues through interactions with peers, luminaries and
> emerging and established companies.
> http://p.sf.net/sfu/rsaconf-dev2dev
> _______________________________________________
> WiX-users mailing list
> WiX...@li...
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
>
>
>
> ----------------------------------------------------------------------------
> --
> Throughout its 18-year history, RSA Conference consistently attracts the
> world's best and brightest in the field, creating opportunities for
> Conference
> attendees to learn about information security's most important issues
> through
> interactions with peers, luminaries and emerging and established companies.
> http://p.sf.net/sfu/rsaconf-dev2dev
> _______________________________________________
> WiX-users mailing list
> WiX...@li...
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
>
>
> ------------------------------------------------------------------------------
> Throughout its 18-year history, RSA Conference consistently attracts the
> world's best and brightest in the field, creating opportunities for
> Conference
> attendees to learn about information security's most important issues
> through
> interactions with peers, luminaries and emerging and established companies.
> http://p.sf.net/sfu/rsaconf-dev2dev
> _______________________________________________
> WiX-users mailing list
> WiX...@li...
> https://lists.sourceforge.net/lists/listinfo/wix-users
>