title: WiX 3.0 throws error 217, while being executed by continuous integration
body: <p>This is the error that is thrown by our automated build suite on Windows 2008, while running <a href="http://msdn.microsoft.com/en-us/library/windows/desktop/aa369554%28v=vs.85%29.aspx" rel="noreferrer">ICEs</a> (after migrating from <a href="http://en.wikipedia.org/wiki/WiX" rel="noreferrer">WiX</a> 2.0 to WiX 3.0):</p>
  
  <blockquote>
    <p>LGHT0217: Error executing ICE action 'ICE01'. The most common cause of this kind of ICE failure is an incorrectly registered scripting engine. See <a href="http://wix.sourceforge.net/faq.html#Error217" rel="noreferrer">http://wix.sourceforge.net/faq.html#Error217</a> 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.". in light.exe(0, 0)</p>
  </blockquote>
  
  <p>Additionally, these are the errors that show up in the event log:</p>
  
  <blockquote>
    <p>MSIInstaller: Failed to connect to server. Error: 0x80070005
    Product: [ProductName] -- Error 1719. 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.</p>
  </blockquote>
  
  <p>Intuitively:</p>
  
  <ul>
  <li><a href="http://en.wikipedia.org/wiki/VBScript" rel="noreferrer">VBScript</a> and <a href="http://en.wikipedia.org/wiki/JScript" rel="noreferrer">JScript</a> were registered under admin.</li>
  <li>Integration service has permissions for the desktop interaction and all the files</li>
  <li>Builds succeed, when executed manually on the same machine by another user or even user logged in as integration account (via <a href="http://en.wikipedia.org/wiki/Remote_Desktop_Protocol" rel="noreferrer">RDP</a>)</li>
  </ul>
  
  <p>I'm out of ideas so far.</p>
  
  <p><strong>How do I solve this problem while keeping ICE validation?</strong></p>