Azure App Service deploy started failing with Unrecognized argument 'Files\IIS\Microsoft'. All arguments must begin with "-"

[noellelc]

Note

Issues in this repo are for tracking bugs, feature requests and questions for the tasks in this repo

For a list:
https://github.com/Microsoft/azure-pipelines-tasks/tree/master/Tasks

If you have an issue or request for the Azure Pipelines service, use developer community instead:

https://developercommunity.visualstudio.com/spaces/21/index.html )

Required Information

Entering this information will route you directly to the right team and expedite traction.

Question, Bug, or Feature?
Type: bug

Enter Task Name: Azure App Service deploy

list here (V# not needed): 4.216.2 https://github.com/Microsoft/azure-pipelines-tasks/tree/master/Tasks

Environment

• Server - Azure Pipelines or TFS on-premises?

  • If using TFS on-premises, provide the version:

  • If using Azure Pipelines, provide the account name, team project name, build definition name/build number: account name: DevDiv, Project name: DevDiv, Release id: 103259

• Agent - Hosted or Private:

  • If using Hosted agent, provide agent queue name: private

  • If using private agent, provide the OS of the machine running the agent and the agent version:

Issue Description

We are running this task in a release pipeline in Azure DevOps. Last successful run was yesterday on version 4.214.0. It looks like this task just recently started failing, with version 4.216.2. Error message: Unrecognized argument 'Files\IIS\Microsoft'. All arguments must begin with "-".

The argument in question is the command itself: "C:\Program Files\IIS\Microsoft Web Deploy V3\msdeploy.exe"; it looks like it's not honoring the quotations and is parsing this string as individual arguments, hence the callout of "Files\IIS\Microsoft"

Task logs

[Enable debug logging and please provide the zip file containing all the logs for a speedy resolution]

Troubleshooting

Checkout how to troubleshoot failures and collect debug logs: https://docs.microsoft.com/en-us/vsts/build-release/actions/troubleshooting

Error logs

[Insert error from the logs here for a quick overview]

[fernandofig]

The workaround has also worked for us too, although I am wondering why this is still an issue if it has supposedly rolled back? Is it due to us already having the latest version of the task installed already?

This is a good point.

I tried deleting all the folders and files within _work\_tasks\IISWebAppDeploymentOnMachineGroup*, restarted the Azure Agent service, and ran the stage again. As I expected, the task is redownloaded, but the task that's downloaded is still 0.216. So what gives? Wasn't it supposed to be 0.215?

[khuramshahzad]

Thank your for quick fix, i have uninstall the web deploy from machine (Web Deploy) - Windows Server 2019, and my CI-CD pipeline is working fine

[frjimenezcorpcab]

in my case, im new with azure pipelines and release, in my first try, i found this error, but when uninstall web deploy, release ocurrs without any error, but not deploy in the machine, after try the command directly in power shell, seems like the error is the same that with web deploy "C:\azagent\A5_work_tasks\IISWebAppDeploymentOnMachineGroup_1b467810-6725-4b6d-accd-886174c09bba\0.216.0\node_modules\azure-pipelines-tasks-webdeployment-common\MSDeploy3.6\MSDeploy3.6\msdeploy.exe" -verb:sync -source:package='C:\azagent\A5_work\r1\a\temp_web_package_6798924466245622.zip' -dest:auto -setParam:name='IIS Web Application Name',value='RH' -enableRule:DoNotDeleteRule

[engern]

Having to remove another software for this to work is not a satisfactory solution for me. I've tried to contact @Pranshu-Negi , hopefully he can provide a better solution.

[Pranshu-Negi]

The PR that created the issue has been reverted now.

[selangley-wa]

What they need to do is push out a newer version, e.g., 0.217.0, that works correctly. It could just be 0.215.0 under a new name.

[edgariscoding]

I agree. As it is, clients with 0.216.0 will stay on that version unless a newer version is released.

[frjimenezcorpcab]

The PR that created the issue has been reverted now.

i tried deleting the content of C:\azagent\A5_work_tasks, and continue downloading versión 0.216.0 with same error

[Pranshu-Negi]

The PR has been reverted but the fix will take few days to be deployed to production. Please be reassured that we are working to fix this issue as soon as possible.

[DarkChocoholicDev]

What happened, though? I thought that reversion was done several weeks ago.

[frjimenezcorpcab]

its any way to download 0.215.0 while release to production

[DarkChocoholicDev]

If nothing gets tailored to the installation when it's downloaded, in theory someone could ZIP it up and make it available on a share. I'm scoping it out now. 14.7 MB of files. (I guess efficiency doesn't much come into play here. :-))

Can anyone confirm that nothing in it is installation specific?

[VIJAYASHANKAR]

We too facing this issue :(

[MarkusPopp]

today i saw Task version 0.217.0 in the azagent work folder, which is actually 0.215.0, so the fix seems to be deployed into prod.

[jrummell]

As of an hour ago, this is now working for me

[engern]

Can confirm this also works for me, even with web deploy 4.0 installed. It downloaded a folder with version 0.217.0 before starting.

Still not impressed with how long it took to revert a bug that potentially stops CI/CD for thousands of applications...

[EjazAtIces]

I am getting same error when I use Azure Devops Release pipeline to deploy to on-premises web server . This is IIS(asp.net core mvc) application.

Just to add more info: Deployment works if environment variable is set (ASPNETCORE_ENVIRONMENT) If environment variable is deleted on the server then getting this error.

any help? any other page reference?