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

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME ...

Cache stampede: when our cache turned against us

While investigating some performance issues, we ran into an ASP.NET Core API that cached a fairly expensive aggregation query for 60 seconds. Under normal load, that was fine: one request rebuilds the cache, everyone else reads from it. Under peak load, dozens of requests would arrive in that same expiry window, all see a cache miss, and all fire the same expensive query in parallel. The database didn't like that. That was the moment when our caching layer stopped helping and started hurting. A burst of requests comes in at the same time, all miss the cache, and all go hammer the database or the downstream API at once. That's a cache stampede . The cache was supposed to protect our backend, and for a few hundred milliseconds it did the opposite. Why this happens IMemoryCache.GetOrCreate (and its async sibling) looks like it protects you, but it doesn't add any locking on its own. Look at the naive version: public async Task<Report> GetReportAsync(string key) ...

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.

The art of simplicity

Search This Blog