I have 2 Azure App Service Deploy steps in a Team Services build, they have the same Subscription details. The only difference is that they target different virtual applications - the one that fails contains an é character, could that be the cause? Here the step output:
2017-01-17T16:04:22.8323742Z 8570d8e4-b732-4c45-87c5-619fe9343427 exists true
2017-01-17T16:04:24.5778681Z Got connection details for Azure App Service:'foo'
2017-01-17T16:04:24.6088690Z Running command: "C:\\Program Files\\IIS\\Microsoft Web Deploy V3\\msdeploy.exe" -verb:getParameters -source:package="C:\\a\\1\\a\\Foo.zip" > "C:\\a\\1\\s\\parameter.xml"
2017-01-17T16:04:25.4027522Z Running command: @echo off
2017-01-17T16:04:25.4027522Z "C:\\Program Files\\IIS\\Microsoft Web Deploy V3\\msdeploy.exe" -verb:sync -source:package="C:\\a\\1\\a\\Foo.zip" -dest:auto,ComputerName=' https://foo.scm.azurewebsites.net:443/msdeploy.axd?site=foo ',UserName='********',Password='********',AuthType='Basic' -setParam:name='IIS Web Application Name',value='foo/bar-é' -userAgent:VSTS_foo_build_154_744 2>error.txt
2017-01-17T16:04:25.4027522Z if %errorlevel% neq 0 exit /b %errorlevel%
2017-01-17T16:04:25.4067519Z [command]C:\\Windows\\system32\\cmd.exe /CC:\\a\\1\\s\\msDeployCommand.bat
2017-01-17T16:04:25.4157662Z 'C:\\Program' is not recognized as an internal or external command,
2017-01-17T16:04:25.4167533Z operable program or batch file.
2017-01-17T16:04:25.4207534Z ##[error]Failed to deploy App Service.
2017-01-17T16:04:29.2496923Z ##[error]Error: Error: C:\\Windows\\system32\\cmd.exe failed with return code: 9009
2017-01-17T16:04:29.2576899Z ##[section]Finishing: Azure App Service Deploy: foo-dev-global
It's almost as if the Powershell command itself is broken, I'm guessing by the special character.
It maybe not the special character causes that issue. I try to deploy the virtual Application with the special characters é , following is my detail steps. Hope it is useful. We also can get moreinfo about WebDeploy error code please refer to document .
1.Create a new build definition for the project
2.Select build solution corresponding VS version.
5.New Queue build for the build definition
This is now working as expected, without me making any changes. Having informed MS of the issue, I can only conclude they've released a fix to the build task.
The technical post webpages of this site follow the CC BY-SA 4.0 protocol. If you need to reprint, please indicate the site URL or the original address.Any question please contact:yoyou2525@163.com.