windows installer - WiX: Mysterious and hard-to-diagnose ICE validation errors on build server build -

I am trying to integrate YX in my automated build solution using 2010 that runs on R2. Everything seemed a lot easier, and then I get this:

light.exe: Error in executing the 'ICE01' action The most common cause of this type of ice failure is an incorrectly registered scripting Is the engine. See for details and how to solve this problem. External string format was not expected by the external UI message logger: "The Windows Installer service can not be used. This can happen if the Windows Installer is not installed properly. Contact your support personnel for assistance. Please. "

This is weird. But hey! They provided a link error in LGHT 0217 ------------------------------------------ -------------------------------------------------- -------------------------------------------------- -------------------------------------------------- -------------------------------------------------- -------------------------------------------------- -------------------------------------------------- -------------------------------------------------- -------------------------------------------------- -------------------- Validation is a great way to catch common authoring errors which can cause service problems, which is why it should now be run by default Used to be. Unfortunately, ICE may be a common problem occurring on Windows Vista and Windows Server 2008. For details about the reason and how to fix it, see Heath Stewart's blog and Aaron Stanner's weblog.

Of course, these terms only describe the situation related to the script engine registration, and the conditions they describe were not present. However, I came to (2010-01-14) which indicated that if I used a domain account to run the Windows Installer service, it would work. It seemed like it was worth the shot.

"Whatever the reason (I did not test Vista, XP, 2003, 7, or 2008 R2) on Windows 2008, MSI service is only available from those logins, which have administrative Access or login that is "interactive". Those that are from service accounts, which do not have administrative privileges, can not access the MSI service and thus can not run ICE tests. "

< / Blockquote>

However, my build service accounts Areas with Windows Installer service:

Could not start the Windows Installer service on Windows Saititi -1. Error 1297: Service account configuration does not have a privilege to work properly for the service. To see service configuration and account configuration, you service Microsoft Management Console (MMC) snap-in (services.msc) and local security settings MMC can use snap-in (secondpole .msc).

Okay, windows, so you are telling me that there is some obscure permission missing in my build service account which needs to start the service. Should the administrator fix it? No, it does not work either.

So I have returned to the local system for the Windows Installer service account. At this time I created the build service to a local administrator, and see, success! This is hardly a solution, though.

My next idea was to try to isolate the set's permission that the build service would actually have to do this. This would be a good solution instead of adding more accounts to the administrator set Step 1: Go to the Local Security Policy and add the build service account to all the permissions currently assigned to the administrator. In principle, it should be allowed to succeed, and from there, I can remove the selected permissions as long as I have not separated all those permissions which should be organized to succeed.

Unfortunately, even with all the same permissions, the build will still fail until the build service account is a member of the local administrator. Why is it like this? Other than the LSP, which is dependent on the administrator group, could I change my build service account to bring the equivalence with the administrators?

Current Conclusion: To avoid ICE verification, the build service must be an administrator error.

Open question:

• Why did not allow permission for my isolation idea?
• Throwing this mysterious error 1297 domain installer service running as a domain user? I am not getting almost any document on this.

I also had to face the same problem. After some conflicts and googling, I came for the solution which would compile the project by suppressing ICE verification in the YX project.