LIGHT error building project in windows service: light.exe : error LGHT0217 : Error e

[Woofster]

Issue: light.exe : error LGHT0217 : Error executing ICE action 'ICE01'.

Our project builds great in interactive windows.

But when we build from a windows service (like finalbuilder server or TFS), the build fails with the error below.

We made sure the user is an admin equiv., and we set the service to interact with the desktop.

Problem persists.

What do we do to resolve?

Linking compiled files together as 'C:\ourdir\ourproject.msi'
Microsoft (R) Windows Installer Xml Linker version 3.5.2519.0
Copyright (C) Microsoft Corporation. All rights reserved.


Updating file information.

Creating cabinet files.
There will be '4' threads used to produce CAB files.
Creating cabinet 'C:\Users\buildsystem\AppData\Local\Temp\3sx0050s\#setup.cab'.

Generating database.

Merging modules.
Validating database.
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.".

[Ulrich]

First, I would update WiX. The current release of MSI Factory uses WiX 3.9.1208, so you could use this or a newer version. If updating WiX does not solve the issue, I would check what was discussed in this thread, and see if there isn't something which could be applied in your case. Apparently there are multiple ways to get this error message, so one of the solutions suggested may work for you.

Ulrich

[Woofster]

A new build!
Cool!
Purchased new maint, and we are going to try it out!

[Woofster]

Ack, NOTE TO ALL: Newer MSI Factory is NOT the answer.

The issue is that on windows 10, the error thrown is different, so it is not masked.
On Win 7 (at least), you can disable validation in the msi factory project. (in the UI)

On Win10, to disable msi validation, you have to add -sval in the msifact file:

<LinkerOptions>-sice:99 -sval</LinkerOptions>


So.... I just paid to get latest msi factory, but did not need it. (Have not even installed it.)

Oh smell.

[Woofster]

Additional info:

The core problem is that the msi validation process cannot run from a windows service (ever... according to our research).

So you just suppress it... nothing ever built from a windows service can validate an msi... limitation of the msi universe.