Unable to deploy IIS Web Site from offline package drop


I’ve just started evaluating Octopus Deploy and ran straight into a major speed bump. Not all of our customers will support online deployments using Tentacle and therefore the most interesting feature of OD for us to evaluate was the offline package drops.

So, I created a simple single-page web application (nothing more than the ASP.NET template) and added the Octopack nuget package (to generate the nuget package).

The installation process only contains one step (Deploy NuGet package) which includes the IIS Web Site/IIS Application Pool features.

After the release is created and deployed, I simply run the cmd in the package drop and I get the following error:

Comparing existing IIS bindings with configured bindings…
Found configured binding which is not assigned: http *:7575:
Existing IIS bindings do not match configured bindings.
Clearing IIS bindings
Assigning binding: http *:7575:
New-ItemProperty : Objektreferensen har inte angetts till en instans av ett objekt. (TRANSLATION: The object reference has not been set to an instance of an object)
At C:\OctopusApplications\My Local\OctopusDeployTestApp\\Octopus.Features.IISWebSite_BeforePostDeploy.ps1:373

  •         New-ItemProperty $sitePath -name bindings -value ($wsbind ...
  •         ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    • CategoryInfo : NotSpecified: (:slight_smile: [New-ItemProperty], NullReferenceException
    • FullyQualifiedErrorId : System.NullReferenceException,Microsoft.PowerShell.Commands.NewItemPropertyCommand

I can’t find any information on how to extract more detailed logs for you to scavenge (for an offline package drop).

Also, OD doesn’t seem to clean up the failing install. Some files remains in the destination folder as well as the created IIS App Pool and IIS Web Site (however, weirdly configured).

I’m struggling to find anyone with a similar issue using my best friend Google. Perhaps you can help?

Best regards,
Niklas Källander

I just found the cause of this issue. I checked my bindings and found that I’ve left “IP address” and “Host name” blank. As the description of “Host name” clearly states that it’s OK to leave it blank but the description of “IP address” don’t, I changed the value of “IP address” to “*” and tested deployment once more. This time it worked without a glitch! (:

(Perhaps make “IP address” a required field?)

/Niklas Källander

Hi Niklas,

Thanks for reaching out. Glad to hear you found a workaround. I’ve created a github issue for the inconsistent behavior when using offline deployments https://github.com/OctopusDeploy/Issues/issues/2203