Skip to main content

Web Deploy error - Source does not support parameter called 'IIS Web Application Name'.

At one of my customers, everything is still on premise hosted on multiple IIS web servers. To deploy web applications, we are using Web Deploy. This works quite nicely and allows us to deploy web application in an automated way.

Last week, a colleague contacted me after configuring the deployment pipeline in Azure DevOps. When the pipeline tried to deploy the application, it failed with the following error message:

"System.Exception: Error: Source does not support parameter called 'IIS Web Application Name'. Must be one of (Environment)"

Here is a more complete build log to get some extra context:

Starting deployment of IIS Web Deploy Package : \DevDrop\BOSS.Intern.Web.zip">\DevDrop\BOSS.Intern.Web.zip">\DevDrop\BOSS.Intern.Web.zip">\DevDrop\BOSS.Intern.Web.zip">\\<servername>\DevDrop\BOSS.Intern.Web.zip

Performing deployment in parallel on all the machines.

Deployment started for machine: <servername> with port 5985.

Deployment status for machine <servername>: Failed

Deployment failed on machine <servername> with following message : System.Exception: Error: Source does not support parameter called 'IIS Web Application Name'. Must be one of (Environment).Error count: 1.ScriptHalted

##[error]Deployment on one or more machines failed. System.Exception: Error: Source does not support parameter called 'IIS Web Application Name'. Must be one of (Environment).Error count: 1.ScriptHalted

For more info please refer to http://aka.ms/iisextnreadme

Finishing: Deploy package BOSS.Intern.Web to Snapp2 BOSS dev

The exception occurred while executing the following deployment step:

There seems to be nothing wrong with the deployment step above and if I compared it with other projects there wasn’t any difference.

So maybe the problem could be found in the construction of the web deploy package?

Web Deploy expect some parameters to be available that will be replaced during the deployment of the package. Maybe something went wrong there.

Here is the pipeline step that was used to build the web deploy package:

The code above will build the web application and output the build results in a specific folder. The results of this folder are zipped but that doesn’t mean that we now have a deployable web deploy package. Therefore some parameters are missing. Let’s update the pipeline to correctly create a web deploy package.

Here is the updated step:

If we now run the pipeline, we could see in the logs  that the mentioned parameter is added:

Info: Adding declared parameter 'IIS Web Application Name'.

Info: Adding declared parameter 'Environment'.

Total changes: 307 (305 added, 0 deleted, 0 updated, 2 parameters changed, 49116855 bytes copied)

Package "BOSS.Intern.Web.zip" is successfully created as single file at the following location

Fixed!

More information

Web Deploy : The Official Microsoft IIS Site

dotnet publish command - .NET CLI | Microsoft Learn

Labels:

Popular posts from this blog

.NET 8–Keyed/Named Services

A feature that a lot of IoC container libraries support but that was missing in the default DI container provided by Microsoft is the support for Keyed or Named Services. This feature allows you to register the same type multiple times using different names, allowing you to resolve a specific instance based on the circumstances. Although there is some controversy if supporting this feature is a good idea or not, it certainly can be handy. To support this feature a new interface IKeyedServiceProvider got introduced in .NET 8 providing 2 new methods on our ServiceProvider instance: object? GetKeyedService(Type serviceType, object? serviceKey); object GetRequiredKeyedService(Type serviceType, object? serviceKey); To use it, we need to register our service using one of the new extension methods: Resolving the service can be done either through the FromKeyedServices attribute: or by injecting the IKeyedServiceProvider interface and calling the GetRequiredKeyedServic...
Read more

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.
Read more

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...
Read more