The Deployment Framework for BizTalk is the most powerful and customizable, yet easy-to-use toolkit for deploying and configuring your BizTalk solutions.
MIT License
53
stars
24
forks
source link
Automated deployment script does not seem to work with beta 6.0 #369
It is not a BTDF issue afterall. Apologies. After racking my brains a bit, I figured it might be another MicroSoft Win 2012 security issue. Even though I ran the scripts as administrator, msiexec was still not running behind the scenes. Adding 'start' at the beginning of my script fixed it.
Again, thanks for all your wonderful work on this product.
Hi,
Let me start by saying thanks for the great job you're doing on the BTDF. It is fantastic. I apologize in advance for taking up some of your time.
We use BTDF for all our automated deployments, and it works absolutely well with our BizTalk 2009 system. We are now upgrading to BTS 2013 R2, and I chose to use Beta 6.0 (s I wrongly or rightly assumed that is the version I have to use with 2103 R2?). The issue is, our batch files, which run fine on BTS 2009, now fail at the MSI installation stage. Not sure what I am missing. The deployment attempt always fails with the error below: The actual script is pasted further below. Thanks in advance
__C:\Windows\system32>"C:\Program Files (x86)\TestApplicationOne\1.0\Deployment\Framework\De
ployTools\EnvironmentSettingsExporter.exe" "C:\Program Files (x86)\TestApplicationOne\1.0\
Deployment\EnvironmentSettings\SettingsFileGenerator.xml" "C:\Program Files (x86
)\TestApplicationOne\1.0\Deployment\EnvironmentSettings"
The system cannot find the path specified.
MSBUILD : error MSB1009: Project file does not exist.
Switch: C:\Program Files (x86)\TestApplicationOne\1.0\Deployment\TestApplicationOne.Deployment.btdfproj
UPDATE...
It is not a BTDF issue afterall. Apologies. After racking my brains a bit, I figured it might be another MicroSoft Win 2012 security issue. Even though I ran the scripts as administrator, msiexec was still not running behind the scenes. Adding 'start' at the beginning of my script fixed it. Again, thanks for all your wonderful work on this product. Hi,
Let me start by saying thanks for the great job you're doing on the BTDF. It is fantastic. I apologize in advance for taking up some of your time.
We use BTDF for all our automated deployments, and it works absolutely well with our BizTalk 2009 system. We are now upgrading to BTS 2013 R2, and I chose to use Beta 6.0 (s I wrongly or rightly assumed that is the version I have to use with 2103 R2?). The issue is, our batch files, which run fine on BTS 2009, now fail at the MSI installation stage. Not sure what I am missing. The deployment attempt always fails with the error below: The actual script is pasted further below. Thanks in advance
__C:\Windows\system32>"C:\Program Files (x86)\TestApplicationOne\1.0\Deployment\Framework\De ployTools\EnvironmentSettingsExporter.exe" "C:\Program Files (x86)\TestApplicationOne\1.0\ Deployment\EnvironmentSettings\SettingsFileGenerator.xml" "C:\Program Files (x86 )\TestApplicationOne\1.0\Deployment\EnvironmentSettings" The system cannot find the path specified.
MSBUILD : error MSB1009: Project file does not exist. Switch: C:\Program Files (x86)\TestApplicationOne\1.0\Deployment\TestApplicationOne.Deployment.btdfproj
THE SCRIPT SET Environment="Dev" msiexec.exe /i TestApplicationOne-1.0.0.0.msi /passive /log TestApplicationOne.log INSTALLDIR="C:\Program Files (x86)\TestApplicationOne\1.0" "C:\Program Files (x86)\TestApplicationOne\1.0\Deployment\Framework\DeployTools\EnvironmentSettingsExporter.exe" "C:\Program Files (x86)\TestApplicationOne\1.0\Deployment\EnvironmentSettings\SettingsFileGenerator.xml" "C:\Program Files (x86)\TestApplicationOne\1.0\Deployment\EnvironmentSettings" "C:\Windows\Microsoft.NET\Framework\v4.0.30319\MSBuild.exe" /p:DeployBizTalkMgmtDB=false;Configuration=Server;SkipUndeploy=true /target:Deploy /l:FileLogger,Microsoft.Build.Engine;logfile="DeployResults.txt" "C:\Program Files (x86)\TestApplicationOne\1.0\Deployment\TestApplicationOne.Deployment.btdfproj" /p:ENVSETTINGS="C:\Program Files (x86)\TestApplicationOne\1.0\Deployment\EnvironmentSettings\Exported%Environment%Settings.xml" pause
This work item was migrated from CodePlex
CodePlex work item ID: '10884' Vote count: '1'