TFSBuild.proj Exec BuildReleaseMsi.bat

Topics: General Questions
Jul 7, 2010 at 2:40 AM

Build, Deploy, and Build Server Deploy MSI tasks work fine from my development machine (sans WCF-OracleDB bindings, but that's another discussion!).  Now I am working on a TFS Build definition.  I started with C:\Program Files\Deployment Framework for BizTalk\5.0\Samples\TeamBuild\TFSBuild.proj + TFSBuild.rsp and have got everything working as desired except for the BuildMSI target.

Specifically, the following task is giving me fits:

<Exec Command="BuildReleaseMsi.bat" WorkingDirectory="$(WixWorkingDir)"/>

First, the cmd.exe is evidently executed with no path environment variable established which causes MSBuild.exe + cscript.exe "is not recognized as an internal or external command" errors.  So, I forcefully set the path as follows:

<Exec Command="SET Path=$(Path);$(MSBuildBinPath)&amp; BuildReleaseMsi.bat" WorkingDirectory="$(WixWorkingDir)"/>

Now I get ICE errors.  Below is the BuildLog.txt output from the relevant MSIBuild CallTarget.  I'm sure I'm mising something that should be painfully obvious.  Appreciate any constructive input.

Regards,

Vercellone


[most of omitted......]
========== Build: 5 succeeded or up-to-date, 0 failed, 0 skipped ==========
Done executing task "Exec".
Using "CallTarget" task from assembly "Microsoft.Build.Tasks.v3.5, Version=3.5.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a".
Task "CallTarget"
Target "CanonicalizePaths" skipped. Previously built successfully.
Target "BuildMSI" in file "C:\TFSDEVEL\Solutions Development\DynCorp.BizTalk.MRO Dev\BuildType\TFSBuild.proj" from project "C:\TFSDEVEL\Solutions Development\DynCorp.BizTalk.MRO Dev\BuildType\TFSBuild.proj":
Task "Message"
  Building MSI using C:\TFSDEVEL\Solutions Development\DynCorp.BizTalk.MRO Dev\BuildType\..\Sources\DynMRO\Dev\DynCorp.BizTalk.MRO\DynCorp.BizTalk.MRO.Deployment\BuildReleaseMsi.bat
Done executing task "Message".
Task "Exec"
  Command:
  SET Path=C:\Oracle\product\11.1.0\client_1;C:\Oracle\product\11.1.0\client_1\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files\Microsoft SQL Server\100\Tools\Binn\;C:\Program Files\Microsoft SQL Server\100\DTS\Binn\;C:\Program Files\Microsoft SQL Server\100\Tools\Binn\VSShell\Common7\IDE\;C:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE\PrivateAssemblies\;C:\Program Files\Microsoft BizTalk Server 2009\;C:\Program Files\Windows Imaging\;C:\Program Files\System Center Operations Manager 2007\;c:\Windows\Microsoft.NET\Framework\v3.5& BuildReleaseMsi.bat
  Microsoft (R) Build Engine Version 3.5.30729.1
  [Microsoft .NET Framework, Version 2.0.50727.4200]
  Copyright (C) Microsoft Corporation 2007. All rights reserved.
 
  Build started 7/6/2010 9:03:11 PM.
  Project "C:\TFSDEVEL\Solutions Development\DynCorp.BizTalk.MRO Dev\Sources\DynMRO\Dev\DynCorp.BizTalk.MRO\DynCorp.BizTalk.MRO.Deployment\DynCorp.BizTalk.MRO.Deployment.btdfproj" on node 0 (Installer target(s)).
    Running on Windows V60
    Detected IIS 7
  GetSoftwarePaths:
    Using .NET Framework Install Path 'C:\Windows\Microsoft.NET\Framework\v2.0.50727'.
    Using BizTalk Install Path 'C:\Program Files\Microsoft BizTalk Server 2009\'.
    Using Deployment Framework Install Path 'C:\Program Files\Deployment Framework for BizTalk\5.0\'.
    Using Deployment Framework Tools Path 'C:\Program Files\Deployment Framework for BizTalk\5.0\Framework\DeployTools'.
  InitializeAppName:
    BizTalk Application Name is DynCorp.BizTalk.MRO
  Redist:
    Directory "obj\Release\redist" doesn't exist. Skipping.
    Creating directory "obj\Release\redist".
    Creating directory "obj\Release\redist\Deployment\Framework".
    Copying file from "C:\Program Files\Deployment Framework for BizTalk\5.0\Framework\CopyDeployResults.msbuild" to "obj\Release\redist\Deployment\Framework\CopyDeployResults.msbuild".
    Copying file from "C:\Program Files\Deployment Framework for BizTalk\5.0\Framework\ServerDeploy.bat" to "obj\Release\redist\Deployment\Framework\ServerDeploy.bat".
    Copying file from "C:\Program Files\Deployment Framework for BizTalk\5.0\Framework\ServerDeployWizard.bat" to "obj\Release\redist\Deployment\Framework\ServerDeployWizard.bat".
    Copying file from "C:\Program Files\Deployment Framework for BizTalk\5.0\Framework\ServerDeployWizardMSI.bat" to "obj\Release\redist\Deployment\Framework\ServerDeployWizardMSI.bat".
    Copying file from "C:\Program Files\Deployment Framework for BizTalk\5.0\Framework\ServerRedeploy.bat" to "obj\Release\redist\Deployment\Framework\ServerRedeploy.bat".
    Copying file from "C:\Program Files\Deployment Framework for BizTalk\5.0\Framework\ServerRedeployWizard.bat" to "obj\Release\redist\Deployment\Framework\ServerRedeployWizard.bat".
    Copying file from "C:\Program Files\Deployment Framework for BizTalk\5.0\Framework\ServerUnDeploy.bat" to "obj\Release\redist\Deployment\Framework\ServerUnDeploy.bat".
    Copying file from "C:\Program Files\Deployment Framework for BizTalk\5.0\Framework\ServerUnDeployWizard.bat" to "obj\Release\redist\Deployment\Framework\ServerUnDeployWizard.bat".
    Creating directory "obj\Release\redist\Deployment\Framework\DeployTools".
    Copying file from "C:\Program Files\Deployment Framework for BizTalk\5.0\Framework\DeployTools\adapterXPaths.txt" to "obj\Release\redist\Deployment\Framework\DeployTools\adapterXPaths.txt".
    Copying file from "C:\Program Files\Deployment Framework for BizTalk\5.0\Framework\DeployTools\BounceBizTalkHost.vbs" to "obj\Release\redist\Deployment\Framework\DeployTools\BounceBizTalkHost.vbs".
    Copying file from "C:\Program Files\Deployment Framework for BizTalk\5.0\Framework\DeployTools\cscript64.exe" to "obj\Release\redist\Deployment\Framework\DeployTools\cscript64.exe".
    Copying file from "C:\Program Files\Deployment Framework for BizTalk\5.0\Framework\DeployTools\DeployBTRules.exe" to "obj\Release\redist\Deployment\Framework\DeployTools\DeployBTRules.exe".
    Copying file from "C:\Program Files\Deployment Framework for BizTalk\5.0\Framework\DeployTools\ElementTunnel.exe" to "obj\Release\redist\Deployment\Framework\DeployTools\ElementTunnel.exe".
    Copying file from "C:\Program Files\Deployment Framework for BizTalk\5.0\Framework\DeployTools\EnvironmentSettingsExporter.exe" to "obj\Release\redist\Deployment\Framework\DeployTools\EnvironmentSettingsExporter.exe".
    Copying file from "C:\Program Files\Deployment Framework for BizTalk\5.0\Framework\DeployTools\ExportBamDefinitionXml.exe" to "obj\Release\redist\Deployment\Framework\DeployTools\ExportBamDefinitionXml.exe".
    Copying file from "C:\Program Files\Deployment Framework for BizTalk\5.0\Framework\DeployTools\gacutil.exe" to "obj\Release\redist\Deployment\Framework\DeployTools\gacutil.exe".
    Copying file from "C:\Program Files\Deployment Framework for BizTalk\5.0\Framework\DeployTools\log4net.dll" to "obj\Release\redist\Deployment\Framework\DeployTools\log4net.dll".
    Copying file from "C:\Program Files\Deployment Framework for BizTalk\5.0\Framework\DeployTools\log4net.Ext.Serializable.dll" to "obj\Release\redist\Deployment\Framework\DeployTools\log4net.Ext.Serializable.dll".
    Copying file from "C:\Program Files\Deployment Framework for BizTalk\5.0\Framework\DeployTools\SetEnvUI.exe" to "obj\Release\redist\Deployment\Framework\DeployTools\SetEnvUI.exe".
    Copying file from "C:\Program Files\Deployment Framework for BizTalk\5.0\Framework\DeployTools\SetEnvUIConfig.xsd" to "obj\Release\redist\Deployment\Framework\DeployTools\SetEnvUIConfig.xsd".
    Copying file from "C:\Program Files\Deployment Framework for BizTalk\5.0\Framework\DeployTools\SetPackageIdentity.vbs" to "obj\Release\redist\Deployment\Framework\DeployTools\SetPackageIdentity.vbs".
    Copying file from "C:\Program Files\Deployment Framework for BizTalk\5.0\Framework\DeployTools\SSOSettingsFileImport.exe" to "obj\Release\redist\Deployment\Framework\DeployTools\SSOSettingsFileImport.exe".
    Copying file from "C:\Program Files\Deployment Framework for BizTalk\5.0\Framework\DeployTools\SSOSettingsFileReader.dll" to "obj\Release\redist\Deployment\Framework\DeployTools\SSOSettingsFileReader.dll".
    Copying file from "C:\Program Files\Deployment Framework for BizTalk\5.0\Framework\DeployTools\StopBizTalkHost.vbs" to "obj\Release\redist\Deployment\Framework\DeployTools\StopBizTalkHost.vbs".
    Copying file from "C:\Program Files\Deployment Framework for BizTalk\5.0\Framework\DeployTools\UacElevate.exe" to "obj\Release\redist\Deployment\Framework\DeployTools\UacElevate.exe".
    Copying file from "C:\Program Files\Deployment Framework for BizTalk\5.0\Framework\DeployTools\WriteRegValue.vbs" to "obj\Release\redist\Deployment\Framework\DeployTools\WriteRegValue.vbs".
    Copying file from "C:\Program Files\Deployment Framework for BizTalk\5.0\Framework\DeployTools\XmlPreprocess.exe" to "obj\Release\redist\Deployment\Framework\DeployTools\XmlPreprocess.exe".
    Copying file from "C:\Program Files\MSBuild\DeploymentFrameworkForBizTalk\5.0\BizTalkDeploymentFramework.targets" to "obj\Release\redist\Deployment\Framework\BizTalkDeploymentFramework.targets".
    Copying file from "C:\Program Files\MSBuild\DeploymentFrameworkForBizTalk\5.0\BizTalkDeploymentFramework.WiXSetup.targets" to "obj\Release\redist\Deployment\Framework\BizTalkDeploymentFramework.WiXSetup.targets".
    Copying file from "C:\Program Files\MSBuild\DeploymentFrameworkForBizTalk\5.0\DeploymentFramework.BuildTasks.dll" to "obj\Release\redist\Deployment\Framework\DeploymentFramework.BuildTasks.dll".
    Copying file from "C:\Program Files\MSBuild\DeploymentFrameworkForBizTalk\5.0\Microsoft.Sdc.Common.tasks" to "obj\Release\redist\Deployment\Framework\Microsoft.Sdc.Common.tasks".
    Copying file from "C:\Program Files\MSBuild\DeploymentFrameworkForBizTalk\5.0\Microsoft.Sdc.Tasks.dll" to "obj\Release\redist\Deployment\Framework\Microsoft.Sdc.Tasks.dll".
    Creating directory "obj\Release\redist\DeployResults".
    Copying file from "InstallWizard.xml" to "obj\Release\redist\Deployment\InstallWizard.xml".
    Copying file from "UninstallWizard.xml" to "obj\Release\redist\Deployment\UninstallWizard.xml".
    Copying file from "C:\TFSDEVEL\Solutions Development\DynCorp.BizTalk.MRO Dev\Sources\DynMRO\Dev\DynCorp.BizTalk.MRO\DynCorp.BizTalk.MRO.Deployment\PortBindingsMaster.xml" to "obj\Release\redist\Deployment\PortBindingsMaster.xml".
    Copying file from "DynCorp.BizTalk.MRO.Deployment.btdfproj" to "obj\Release\redist\Deployment\DynCorp.BizTalk.MRO.Deployment.btdfproj".
    Copying file from "..\..\DynCorp.BizTalk.MRO\DynCorp.BizTalk.MRO.Schemas\bin\Release\DynCorp.BizTalk.MRO.Schemas.dll" to "obj\Release\redist\DynCorp.BizTalk.MRO.Schemas.dll".
    Copying file from "..\..\DynCorp.BizTalk.MRO\DynCorp.BizTalk.MRO.Schemas\bin\Release\DynCorp.BizTalk.MRO.Schemas.pdb" to "obj\Release\redist\DynCorp.BizTalk.MRO.Schemas.pdb".
    Copying file from "..\DynCorp.BizTalk.MRO.Orchestrations\bin\Release\DynCorp.BizTalk.MRO.Orchestrations.dll" to "obj\Release\redist\DynCorp.BizTalk.MRO.Orchestrations.dll".
    Copying file from "..\DynCorp.BizTalk.MRO.Orchestrations\bin\Release\DynCorp.BizTalk.MRO.Orchestrations.pdb" to "obj\Release\redist\DynCorp.BizTalk.MRO.Orchestrations.pdb".
    Copying file from "..\DynCorp.BizTalk.MRO.Transforms\bin\Release\DynCorp.BizTalk.MRO.Transforms.dll" to "obj\Release\redist\DynCorp.BizTalk.MRO.Transforms.dll".
    Copying file from "..\DynCorp.BizTalk.MRO.Transforms\bin\Release\DynCorp.BizTalk.MRO.Transforms.pdb" to "obj\Release\redist\DynCorp.BizTalk.MRO.Transforms.pdb".
    Copying file from "..\DynCorp.BizTalk.MRO.Pipelines\bin\Release\DynCorp.BizTalk.MRO.Pipelines.dll" to "obj\Release\redist\DynCorp.BizTalk.MRO.Pipelines.dll".
    Copying file from "..\DynCorp.BizTalk.MRO.Pipelines\bin\Release\DynCorp.BizTalk.MRO.Pipelines.pdb" to "obj\Release\redist\DynCorp.BizTalk.MRO.Pipelines.pdb".
    Creating directory "obj\Release\redist\Deployment\EnvironmentSettings".
    Copying file from "C:\TFSDEVEL\Solutions Development\DynCorp.BizTalk.MRO Dev\Sources\DynMRO\Dev\DynCorp.BizTalk.MRO\DynCorp.BizTalk.MRO.Deployment\EnvironmentSettings\SettingsFileGenerator.xml" to "obj\Release\redist\Deployment\EnvironmentSettings\SettingsFileGenerator.xml".
  Installer:
    Generating obj\Release\Contents.wxi...
    Microsoft (R) Windows Installer Xml Compiler version 3.0.5308.0
    Copyright (C) Microsoft Corporation. All rights reserved.
   
    GenericBizTalkMSI.wxs
    Microsoft (R) Windows Installer Xml Linker version 3.0.5308.0
    Copyright (C) Microsoft Corporation. All rights reserved.
   
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 the Windows Installer is not correctly installed. Contact your support personnel for assistance.".
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 the Windows Installer is not correctly installed. Contact your support personnel for assistance.".
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 the Windows Installer is not correctly installed. Contact your support personnel for assistance.".
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 the Windows Installer is not correctly installed. Contact your support personnel for assistance.".
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 the Windows Installer is not correctly installed. Contact your support personnel for assistance.".
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 the Windows Installer is not correctly installed. Contact your support personnel for assistance.".
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 the Windows Installer is not correctly installed. Contact your support personnel for assistance.".
light.exe : error LGHT0216: An unexpected Win32 exception with error code 0x643 occurred: Action - 'ICE08' Fatal error during installation
C:\Program Files\MSBuild\DeploymentFrameworkForBizTalk\5.0\BizTalkDeploymentFramework.WiXSetup.targets(191,5): error MSB3073: The command ""C:\Program Files\Deployment Framework for BizTalk\5.0\Developer\WiX\light.exe" obj\Release\DynCorp.BizTalk.MRO.wixobj -out bin\Release\\DynCorp.BizTalk.MRO-1.0.0.msi -ext "C:\Program Files\Deployment Framework for BizTalk\5.0\Developer\WiX\WixUIExtension.dll" -spdb" exited with code 216.
  Done Building Project "C:\TFSDEVEL\Solutions Development\DynCorp.BizTalk.MRO Dev\Sources\DynMRO\Dev\DynCorp.BizTalk.MRO\DynCorp.BizTalk.MRO.Deployment\DynCorp.BizTalk.MRO.Deployment.btdfproj" (Installer target(s)) -- FAILED.
 
  Build FAILED.
 
  "C:\TFSDEVEL\Solutions Development\DynCorp.BizTalk.MRO Dev\Sources\DynMRO\Dev\DynCorp.BizTalk.MRO\DynCorp.BizTalk.MRO.Deployment\DynCorp.BizTalk.MRO.Deployment.btdfproj" (Installer target) (1) ->
  (Installer target) ->
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 the Windows Installer is not correctly installed. Contact your support personnel for assistance.".
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 the Windows Installer is not correctly installed. Contact your support personnel for assistance.".
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 the Windows Installer is not correctly installed. Contact your support personnel for assistance.".
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 the Windows Installer is not correctly installed. Contact your support personnel for assistance.".
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 the Windows Installer is not correctly installed. Contact your support personnel for assistance.".
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 the Windows Installer is not correctly installed. Contact your support personnel for assistance.".
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 the Windows Installer is not correctly installed. Contact your support personnel for assistance.".
light.exe : error LGHT0216: An unexpected Win32 exception with error code 0x643 occurred: Action - 'ICE08' Fatal error during installation
C:\Program Files\MSBuild\DeploymentFrameworkForBizTalk\5.0\BizTalkDeploymentFramework.WiXSetup.targets(191,5): error MSB3073: The command ""C:\Program Files\Deployment Framework for BizTalk\5.0\Developer\WiX\light.exe" obj\Release\DynCorp.BizTalk.MRO.wixobj -out bin\Release\\DynCorp.BizTalk.MRO-1.0.0.msi -ext "C:\Program Files\Deployment Framework for BizTalk\5.0\Developer\WiX\WixUIExtension.dll" -spdb" exited with code 216.
 
      0 Warning(s)
      9 Error(s)
 
  Time Elapsed 00:00:05.61
C:\TFSDEVEL\Solutions Development\DynCorp.BizTalk.MRO Dev\BuildType\TFSBuild.proj(65,7): error MSB3073: The command "SET Path=C:\Oracle\product\11.1.0\client_1;C:\Oracle\product\11.1.0\client_1\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files\Microsoft SQL Server\100\Tools\Binn\;C:\Program Files\Microsoft SQL Server\100\DTS\Binn\;C:\Program Files\Microsoft SQL Server\100\Tools\Binn\VSShell\Common7\IDE\;C:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE\PrivateAssemblies\;C:\Program Files\Microsoft BizTalk Server 2009\;C:\Program Files\Windows Imaging\;C:\Program Files\System Center Operations Manager 2007\;c:\Windows\Microsoft.NET\Framework\v3.5& BuildReleaseMsi.bat" exited with code 1.
Done executing task "Exec" -- FAILED.
Done building target "BuildMSI" in project "TFSBuild.proj" -- FAILED.
Done executing task "CallTarget" -- FAILED.
Done building target "AfterCompile" in project "TFSBuild.proj" -- FAILED.
Done Building Project "C:\TFSDEVEL\Solutions Development\DynCorp.BizTalk.MRO Dev\BuildType\TFSBuild.proj" (EndToEndIteration target(s)) -- FAILED.

Build FAILED.

"C:\TFSDEVEL\Solutions Development\DynCorp.BizTalk.MRO Dev\BuildType\TFSBuild.proj" (EndToEndIteration target) (1) ->
(AfterCompile target) ->
  C:\TFSDEVEL\Solutions Development\DynCorp.BizTalk.MRO Dev\Sources\DynMRO\Dev\DynCorp.BizTalk.MRO\DynCorp.BizTalk.MRO.Schemas\PurchaseOrder.xsd : warning BEC1007: Node "<Schema>" - Target namespace is empty.
  C:\TFSDEVEL\Solutions Development\DynCorp.BizTalk.MRO Dev\Sources\DynMRO\Dev\DynCorp.BizTalk.MRO\DynCorp.BizTalk.MRO.Schemas\Receipt.xsd : warning BEC1007: Node "<Schema>" - Target namespace is empty.
  C:\TFSDEVEL\Solutions Development\DynCorp.BizTalk.MRO Dev\Sources\DynMRO\Dev\DynCorp.BizTalk.MRO\DynCorp.BizTalk.MRO.Schemas\Shipment.xsd : warning BEC1007: Node "<Schema>" - Target namespace is empty.


"C:\TFSDEVEL\Solutions Development\DynCorp.BizTalk.MRO Dev\BuildType\TFSBuild.proj" (EndToEndIteration target) (1) ->
(BuildMSI target) ->
  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 the Windows Installer is not correctly installed. Contact your support personnel for assistance.".
  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 the Windows Installer is not correctly installed. Contact your support personnel for assistance.".
  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 the Windows Installer is not correctly installed. Contact your support personnel for assistance.".
  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 the Windows Installer is not correctly installed. Contact your support personnel for assistance.".
  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 the Windows Installer is not correctly installed. Contact your support personnel for assistance.".
  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 the Windows Installer is not correctly installed. Contact your support personnel for assistance.".
  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 the Windows Installer is not correctly installed. Contact your support personnel for assistance.".
  light.exe : error LGHT0216: An unexpected Win32 exception with error code 0x643 occurred: Action - 'ICE08' Fatal error during installation
  C:\Program Files\MSBuild\DeploymentFrameworkForBizTalk\5.0\BizTalkDeploymentFramework.WiXSetup.targets(191,5): error MSB3073: The command ""C:\Program Files\Deployment Framework for BizTalk\5.0\Developer\WiX\light.exe" obj\Release\DynCorp.BizTalk.MRO.wixobj -out bin\Release\\DynCorp.BizTalk.MRO-1.0.0.msi -ext "C:\Program Files\Deployment Framework for BizTalk\5.0\Developer\WiX\WixUIExtension.dll" -spdb" exited with code 216.
  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 the Windows Installer is not correctly installed. Contact your support personnel for assistance.".
  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 the Windows Installer is not correctly installed. Contact your support personnel for assistance.".
  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 the Windows Installer is not correctly installed. Contact your support personnel for assistance.".
  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 the Windows Installer is not correctly installed. Contact your support personnel for assistance.".
  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 the Windows Installer is not correctly installed. Contact your support personnel for assistance.".
  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 the Windows Installer is not correctly installed. Contact your support personnel for assistance.".
  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 the Windows Installer is not correctly installed. Contact your support personnel for assistance.".
  light.exe : error LGHT0216: An unexpected Win32 exception with error code 0x643 occurred: Action - 'ICE08' Fatal error during installation
  C:\Program Files\MSBuild\DeploymentFrameworkForBizTalk\5.0\BizTalkDeploymentFramework.WiXSetup.targets(191,5): error MSB3073: The command ""C:\Program Files\Deployment Framework for BizTalk\5.0\Developer\WiX\light.exe" obj\Release\DynCorp.BizTalk.MRO.wixobj -out bin\Release\\DynCorp.BizTalk.MRO-1.0.0.msi -ext "C:\Program Files\Deployment Framework for BizTalk\5.0\Developer\WiX\WixUIExtension.dll" -spdb" exited with code 216.
  C:\TFSDEVEL\Solutions Development\DynCorp.BizTalk.MRO Dev\BuildType\TFSBuild.proj(65,7): error MSB3073: The command "SET Path=C:\Oracle\product\11.1.0\client_1;C:\Oracle\product\11.1.0\client_1\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files\Microsoft SQL Server\100\Tools\Binn\;C:\Program Files\Microsoft SQL Server\100\DTS\Binn\;C:\Program Files\Microsoft SQL Server\100\Tools\Binn\VSShell\Common7\IDE\;C:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE\PrivateAssemblies\;C:\Program Files\Microsoft BizTalk Server 2009\;C:\Program Files\Windows Imaging\;C:\Program Files\System Center Operations Manager 2007\;c:\Windows\Microsoft.NET\Framework\v3.5& BuildReleaseMsi.bat" exited with code 1.

    3 Warning(s)
    19 Error(s)

Time Elapsed 00:00:29.75

Coordinator
Jul 7, 2010 at 3:32 PM

Hi Vercellone,

First on the Exec of BuildReleaseMsi.bat: I recommend that instead of calling the BAT file, copy the MSBuild command out of the BAT file and use it in your Exec task since it's just a simple MSBuild command line (you could also use the MSBuild task).

As for the ICE error -- I've never seen or heard of it before, but it appears to be common enough that Microsoft has several KB's on it.  I suspect that it is not a Deployment Framework-related issue.  Perhaps you could check the permissions of the TFS Build service account.  Otherwise, have you seen this KB?  http://support.microsoft.com/kb/315346

Thanks,
Tom

Jul 7, 2010 at 8:45 PM

Tom,

I changed the task to: 

 

<MSBuild Properties="Configuration=$(BuildFlavor)" Targets="Installer" Projects="$(WixWorkingDir)\$(SolutionName).Deployment.btdfproj" />

 

Quite a bit more output was generated prior to the problematic light.exe execution, but I still get ICE errors.  And, it seems to give up after the first fatal light.exe error this time around. (errors from log are pasted below).  It should be noted that I can execute BuildReleaseMsi.bat on either machine and an msi file is successfully written to bin\Release\DynCorp.BizTalk.MRO-1.0.0.msi.  So, the articles I have found don't seem to apply.  What do you think?


[...omitted above...]
Using "Exec" task from assembly "Microsoft.Build.Tasks, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a".
Task "Exec"
  Command:
  "cscript.exe" /nologo "C:\Program Files\Deployment Framework for BizTalk\5.0\Developer\generate-install-script.js" obj\Release\redist obj\Release\Contents.wxi false false "DynCorp.BizTalk.MRO"
  Generating obj\Release\Contents.wxi...
Done executing task "Exec".
Task "Exec"
  Command:
  "C:\Program Files\Deployment Framework for BizTalk\5.0\Developer\WiX\candle.exe" "-dredist_folder=obj\Release\redist" "-dProductUpgradeCode=1c40136d-99ac-4dc1-a086-2f27a0d74fb1" "-dProductName=DynCorp.BizTalk.MRO" "-dProductId=64c59860-ba2d-4080-94ef-fcc6937dca47" "-dProductVersion=1.0.0" "-dProjectVersion=2.0" "-dManufacturer=DynCorp International" "-dPackageDescription=DynCorp.BizTalk.MRO" "-dPackageComments=DynCorp.BizTalk.MRO" "-dDeploymentTest=" "-dContentsIncludePath=C:\TFSDEVEL\Solutions Development\DynCorp.BizTalk.MRO Dev\Sources\DynMRO\Dev\DynCorp.BizTalk.MRO\DynCorp.BizTalk.MRO.Deployment\obj\Release\Contents.wxi" "-dProjectFilename=DynCorp.BizTalk.MRO.Deployment.btdfproj" -out "obj\Release\DynCorp.BizTalk.MRO.wixobj" "C:\Program Files\Deployment Framework for BizTalk\5.0\Developer\GenericBizTalkMSI.wxs"
  Microsoft (R) Windows Installer Xml Compiler version 3.0.5308.0
  Copyright (C) Microsoft Corporation. All rights reserved.
 
  GenericBizTalkMSI.wxs
Done executing task "Exec".
Task "Exec"
  Command:
  "C:\Program Files\Deployment Framework for BizTalk\5.0\Developer\WiX\light.exe" obj\Release\DynCorp.BizTalk.MRO.wixobj -out bin\Release\\DynCorp.BizTalk.MRO-1.0.0.msi -ext "C:\Program Files\Deployment Framework for BizTalk\5.0\Developer\WiX\WixUIExtension.dll" -spdb
  Microsoft (R) Windows Installer Xml Linker version 3.0.5308.0
  Copyright (C) Microsoft Corporation. All rights reserved.
 
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 the Windows Installer is not correctly installed. Contact your support personnel for assistance.".
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 the Windows Installer is not correctly installed. Contact your support personnel for assistance.".
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 the Windows Installer is not correctly installed. Contact your support personnel for assistance.".
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 the Windows Installer is not correctly installed. Contact your support personnel for assistance.".
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 the Windows Installer is not correctly installed. Contact your support personnel for assistance.".
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 the Windows Installer is not correctly installed. Contact your support personnel for assistance.".
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 the Windows Installer is not correctly installed. Contact your support personnel for assistance.".
light.exe : error LGHT0216: An unexpected Win32 exception with error code 0x643 occurred: Action - 'ICE08' Fatal error during installation
C:\Program Files\MSBuild\DeploymentFrameworkForBizTalk\5.0\BizTalkDeploymentFramework.WiXSetup.targets(191,5): error MSB3073: The command ""C:\Program Files\Deployment Framework for BizTalk\5.0\Developer\WiX\light.exe" obj\Release\DynCorp.BizTalk.MRO.wixobj -out bin\Release\\DynCorp.BizTalk.MRO-1.0.0.msi -ext "C:\Program Files\Deployment Framework for BizTalk\5.0\Developer\WiX\WixUIExtension.dll" -spdb" exited with code 216.
Done executing task "Exec" -- FAILED.
Done building target "Installer" in project "DynCorp.BizTalk.MRO.Deployment.btdfproj" -- FAILED.
Done Building Project "C:\TFSDEVEL\Solutions Development\DynCorp.BizTalk.MRO Dev\Sources\DynMRO\Dev\DynCorp.BizTalk.MRO\DynCorp.BizTalk.MRO.Deployment\DynCorp.BizTalk.MRO.Deployment.btdfproj" (Installer target(s)) -- FAILED.
Done executing task "MSBuild" -- FAILED.
Done building target "BuildMSI" in project "TFSBuild.proj" -- FAILED.
Done executing task "CallTarget" -- FAILED.
Done building target "AfterCompile" in project "TFSBuild.proj" -- FAILED.
Done Building Project "C:\TFSDEVEL\Solutions Development\DynCorp.BizTalk.MRO Dev\BuildType\TFSBuild.proj" (EndToEndIteration target(s)) -- FAILED.

Build FAILED.

"C:\TFSDEVEL\Solutions Development\DynCorp.BizTalk.MRO Dev\BuildType\TFSBuild.proj" (EndToEndIteration target) (1) ->
(AfterCompile target) ->
  C:\TFSDEVEL\Solutions Development\DynCorp.BizTalk.MRO Dev\Sources\DynMRO\Dev\DynCorp.BizTalk.MRO\DynCorp.BizTalk.MRO.Schemas\PurchaseOrder.xsd : warning BEC1007: Node "<Schema>" - Target namespace is empty.
  C:\TFSDEVEL\Solutions Development\DynCorp.BizTalk.MRO Dev\Sources\DynMRO\Dev\DynCorp.BizTalk.MRO\DynCorp.BizTalk.MRO.Schemas\Receipt.xsd : warning BEC1007: Node "<Schema>" - Target namespace is empty.
  C:\TFSDEVEL\Solutions Development\DynCorp.BizTalk.MRO Dev\Sources\DynMRO\Dev\DynCorp.BizTalk.MRO\DynCorp.BizTalk.MRO.Schemas\Shipment.xsd : warning BEC1007: Node "<Schema>" - Target namespace is empty.


"C:\TFSDEVEL\Solutions Development\DynCorp.BizTalk.MRO Dev\BuildType\TFSBuild.proj" (EndToEndIteration target) (1) ->
"C:\TFSDEVEL\Solutions Development\DynCorp.BizTalk.MRO Dev\Sources\DynMRO\Dev\DynCorp.BizTalk.MRO\DynCorp.BizTalk.MRO.Deployment\DynCorp.BizTalk.MRO.Deployment.btdfproj" (Installer target) (2) ->
(Installer target) ->
  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 the Windows Installer is not correctly installed. Contact your support personnel for assistance.".
  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 the Windows Installer is not correctly installed. Contact your support personnel for assistance.".
  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 the Windows Installer is not correctly installed. Contact your support personnel for assistance.".
  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 the Windows Installer is not correctly installed. Contact your support personnel for assistance.".
  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 the Windows Installer is not correctly installed. Contact your support personnel for assistance.".
  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 the Windows Installer is not correctly installed. Contact your support personnel for assistance.".
  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 the Windows Installer is not correctly installed. Contact your support personnel for assistance.".
  light.exe : error LGHT0216: An unexpected Win32 exception with error code 0x643 occurred: Action - 'ICE08' Fatal error during installation
  C:\Program Files\MSBuild\DeploymentFrameworkForBizTalk\5.0\BizTalkDeploymentFramework.WiXSetup.targets(191,5): error MSB3073: The command ""C:\Program Files\Deployment Framework for BizTalk\5.0\Developer\WiX\light.exe" obj\Release\DynCorp.BizTalk.MRO.wixobj -out bin\Release\\DynCorp.BizTalk.MRO-1.0.0.msi -ext "C:\Program Files\Deployment Framework for BizTalk\5.0\Developer\WiX\WixUIExtension.dll" -spdb" exited with code 216.

    3 Warning(s)
    9 Error(s)

 

Coordinator
Jul 7, 2010 at 9:06 PM
Edited Jul 7, 2010 at 9:08 PM

I found your exact problem in a two-year-old mail thread: http://www.mail-archive.com/wix-users@lists.sourceforge.net/msg18888.html. They don't seem to have found much of a resolution other than messing with group membership and permissions on the account used by Team Build. Are you saying that the MSI build works without error on the build machine when you log in and run it yourself?

You can always disable light.exe's MSI validation since the MSI is most likely being generated correctly. Unfortunately that will require changing BizTalkDeploymentFramework.WiXSetup.targets in \Program Files\MSBuild\DeploymentFrameworkForBizTalk\5.0. I believe (but am not 100% sure) that the additional command line switch that you would need is -sval.

Thanks, Tom

Jul 7, 2010 at 10:43 PM

Excellent!  That was exactly my problem!  I removed the tfsbuild domain account from the IIS_IUSRS group and all is well!  THANK YOU!!

Coordinator
Jul 7, 2010 at 11:03 PM

Wow, that sounded too far out there to be a solution but I'm glad it did the trick!  It would appear then that Windows Installer has a specific Deny permission set for the IIS_IUSRS group.  If the TFS build service account can be in Administrators and still not have permissions, then an explicit Deny is about the only thing that could override admin rights.

Tom