Build server without admin rights fails with light.exe

[wixbot]

My corporate infrastructure does not allow admin rights on service accounts. So creating build scripts for WIX projects on our build servers always fail. Is there any plan to update WIX to allow builds to work on non-elevated privilege service accounts on build servers?

This is example of some errors I get:

light.exe: 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: 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 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.".

Originally opened by jasonmohyla

[wixbot]

This is a limitation of the ICE validators. You can turn off validation for CI builds and use the Smoke.exe tool manually.

Resolution set to external
Status changed from Untriaged to Resolved

[degasus]

What do you think about reopen this issue. We've spend a full day figuring out this bug. Yes, it is a bug in an external code, but we can work around it.

Suggestions:

• Detect if the ICE validation is accessable and raise a warning instead.
• Create a warning that this is likely a Windows Installer issue and why it is failing: "elevated privilege or UI required", maybe even a link to this page.